mzxrules

Addition/subtraction in computers is designed in such a way that only addition is required (ex. 10 - 10 = 000A + FFF6 = 1 0000, where the 1 is dropped/recorded via overflow flag). You are not subtracting 000A from FFFF, you are subtracting it from 1 0000. If you're using Windows, you can make the calculation easier by going into the Programmer mode in Calculator and setting the value size on the bottom left. From there you can simply do 0000 - 000A to get FFF6, or similar.

According to my math... 11A5D0 (v1.0's 15E660 equivalent) + 0130 = A700, which if you have my Game File Bit Mappings table still, you'd see that the word is used for the room clear flags for the Forest Temple. 0138 should be used instead. Chest Switches Clear Triggers Perm Collectables Nothing Visited Rooms Visited Rooms

Speedrunnin's by Cosmo.

How does it work?

That doesn't look like a $0 budget game at all. Also, the platforming bit at 1:24 looks like it came out of Sunshine rather than SM64.

http://wiki.spinout182.com/w/Ocarina_of_Time:_Save_Format The first 0x10 bytes affect the entrance table lookup. 15E660 is the base entrance index. 15E668 is what I call the cutscene entrance offset, default is 0000. If set to FFF0-FFFF, it will play whatever cutscene is being pointed to by the cutscene pointer. If set to those values while the scene is loading, it will cause a cutscene defined by the 0x17 command to play. 15E66C is game world time. Somewhere near 15E6C8 should be the child and adult buttons. Also, after 15E6C8 is C item slots, which determine item highlighting and what inventory slot should be written to when a bottle item's contents updates.

I don't get how you can say you admitted that it was a terrible idea, when it's obvious that you tried to defend your position. There is no standard algorithm for randomizing the items in MM, and in the post I responded to you did not describe any sort of algorithm, so regardless of your "Freudian slip" your notation was completely nonsensical. I'm not sure how your POC accomplishes that. As written, your POC program will have to reshuffle the array more than a million times on average, which doesn't support your earlier claim that "Each randomization should take a small fraction of a second with a set as small as MM's" Actually, that's not entirely true. There are three variable elements to the algorithm: The elements that can be randomized without restriction, the elements that must exist within the first part of the array, and the cut-off point (the under 100 value). As the cut-off value gets closer to the total number of items to randomize, the average number of rerolls becomes less until you hit O(n).

No, it is you who does not understand the pitfalls with the solution you proposed. Or in other words, randomizing then checking to see if the game guessed correctly. To start, your math is quite wrong, for a simple reason... It does not accurately model the problem, which is either [*]The number of shuffles required to put all required items in the places they're accessible, or [*]The number of shuffles required to place a single item such that no duplicates/exclusions occur, yet all items remain accessible. For one, the set of items that must be in a single location does not exist in the set of items are to be randomized, and thus should not be part of the equation. The other, is that it is impossible to know how many randomization attempts it will take without actually having an algorithm to check the validity of the solution of each randomized attempt. To prove my point, lets say you were to implement it like this: You have a pool of potential items, and you randomly choose one out of the pool. You run some sort of check and if the check passes you get that item and it is removed from the pool; else you randomly choose another. Obviously the more complex the check algorithm becomes, the more the reroll count moves from 0, potentially to infinity if you make a mistake along the way.

The trouble with that is that you'd have to save your randomized item list, otherwise one could constantly reload an owl statue until they obtained the item they needed. A terrible idea. If you know what places certain items won't be accessible, write the generation algorithm so that they aren't put there. Otherwise, you risk running into a situation where randomization takes 2, 3, 1000, never attempts.

Teach me how to hover to Inverted Stone Tower! Because that's kind of a big problem with randomized chest contents. If you have purely randomized contents, you risk making it impossible to obtain certain items. If you don't randomize the key/boss item locations in dungeons, you'll end up with a sort of 100% run with a broken flow to it.

fixed. Anyway, the thing that is a bit disappointing is that the presentation of the video and "gameplay" shown looks like an early alpha, and that we won't see anything playable for at least 2 years. Well that, and the "Now in Development" logo.

Not really. It was one of the last things I added into the game, and at that point there isn't anything really worth getting at that point either. Bottle/Heart Pieces aren't useful if you know what you're doing, and Biggoron's Sword is not incredibly useful since Ganon/dorf is weak to the Master Sword.

Ice Cavern has been moved before Forest Temple The normal entrance to Tower Climb has been changed to take you to Twinrova's Room, to prevent becoming unable to warp. Prelude can now be obtained instead of Light Medallion. It serves as a way to warp back to Tower Climb. A dialog Pop-up was removed. The patcher program now switches the language byte to E so that you can experience quick text if you use a J rom as a base

Updated with Version 2 patcher link.

You did. It's hidden in a pretty goofy place in the Bottom of the Well.

There is no game ending bug in the Water Temple. You can read about it here.

Version 2 The concept is simple. It's a mod where every dungeon in the game has been strung together one after another, with minimal tweaks to make the dungeons flow faster / make things more interesting, while still being essentially v1.0. Starting equipment consists of the Kokiri Sword, Deku Shield, Ocarina of Time, Bottled Fish, Din's Fire, Zelda's Lullaby and Song of Time. Except for Din's Fire, all other items are automatically equipped from the start. Once you complete a major dungeon, you will be unable to return to it so make sure you have all the items you require to progress further. However, there is a bit of an exception to this. There are a few non-dungeon areas that can be accessed within the mod. Savewarping at one of these locations will either take you to the Temple of Time as a Child, or the Fire Temple as an adult. One major feature to the mod is that aside from the Deku Tree's Navi pop-ups, all navi pop-ups or generic pop-up dialogs like the ones in Gerudo Training Grounds have been removed or no longer instantly pop up. Also, aside from the Navi Pop-ups in the Deku Tree, all dialog is quick text, and can be quick-skipped by mashing B. Dungeon Rush is unique in that it's a v1.0 mod rather than the Debug Rom that is typically used. The reason for this is for the mod to be playable on the Wii. I've written a custom program to allow you to patch the v1.0 Rom. I think it requires at minimum Windows XP to run. Simply click the create button to find v1.0, open it, and hopefully it instantly creates the mod. To fix pause lag on Project 64 (tested with v1.6, but I think v1.7 is the same) you'll need to update Project64.rdb On XP you can find it in the Project 64 folder, but on Windows Vista, Windows 7 you have to look for a hidden folder named "AppData" in the username directory. From there go into the folder named "local", then inside another called VirtualStore, to find Programs x86 -> Project 64 folders. Add the following somewhere after // ---- END OF HEADER, START OF ROM ENTRIES -------------------------- To fix the pause lag on Mupen 64 Plus. When launching the game, you must suffix --cheats 0 in the launch options.

I'm sick of working on this thing... Which is a good because it means I'm done. Injected the rom into this wad here, dunno if it works, will release if I find out it does. Bit afraid to test since I lost bootmii due to my SD card achieving it's solid state and me cut-pasting instead of copy paste, and the site's down. Edit: just because

Why would anyone want Pacman in smash? Pacman hasn't been relevant to gaming for years now.

The odd white pixel on the L was a test to see why the L was so jagged, and isn't on the final image.

Can someone figure out what the first word in a cutscene does? I have a feeling that it does something very similar to the 3E8 command, and changing it's value has some strange side effects. For reference, the 3E8 command contains an index which references a pointer value located in code.asm, that points directly to code.asm in ram.Also for reference, the cutscene pointer is located at 80213D88 in ram in the debug version.

And I would like to be able to enter a discussion without my comments being removed without explanation just because I happen to dislike a game the op likes.That's the problem with wanting only positive discussion about a topic (even more-so when you expect us to do so without mentioning it). It comes off as being rather selfish and controlling because the fact is of course that we are individuals and have our own tastes in everything (including what we believe is a positive and negative aspect of life), and is only exacerbated by the rule that allows the op to dictate what is or isn't fair game, when the moderators should be the ones to do that.

I read about this on Zelda Universe. The only thing that I thought gave it any credibility was that Flotonic was an admin on the forums. As for URA, we need to turn it into a joke... call all Zelda mods URA, as in URA Zelda Mod!

Why would a dungeon rush not have bosses... Anywho, created the first compressed "build" of Dungeon Rush and gave it a full start to finish playthrough. Found a few minor things that need to be taken care of (really just removing dialog) so it'll be ready most likely this weekend.

The text seems a little small (save for ZELDA of course)