No problem.  I found out that the reason the one event wasn't working, was that I was going straight up from the dungeon entrance, and for some reason that makes a big deal reguarding certain events.  As for the regional headers, just do a search for 2D CC and check and see all the stuff that is dependant on which region you are currently on.

Aah. Very odd, but that's a load off my shoulders. Also, I searched 2D CC but there are several results even in the first bank. Anything specific you meant?

When you put it that way, that makes a lot of sense, but really the binary way I explained it is really just a more complication explanation of that that just so happens to work. And yes, by down I meant tile 78, since the spikes were on the bottom. Also, 10-13 being one way doors; isn't that kind of useless? If you have a shutting door and nothing that opens it then it technically is a one way door and that's a waste of 4 bytes.

Personally I like explaining it the bit way since it's good practice (I'm going to imagine that a lot of people hacking these games are like people using Advance Map and other Pokemon tools) and makes a lot more sense, because notice how all of your numbers depended on the first 2 bits being the direction and other bits as "flags".

Hmm... Are you sure it's not? I've tested and the 3rd bit (*xx) controls if the doors open from a trigger, block being pushed, or something else. The first two bits then control the direction again. The 4th bit (*xxx) should control enemies needed to be killed... I haven't actually looked at the code, but this is more from trial-and-error. I've tried other values that would resemble the door directions in the tileset, like using the boss key doors, but then I noticed it's two-bit-based (Or seems to be bit based. If you don't have the 4th bit set and kill all the enemies, the door won't open. If the 3rd bit is set, and you push a trigger, the direction from the two bits will open).

I've figured out a lot of other events, such as the key falling down method (Like re-created the LA Tail Cave room to the left of the entrance. That was a piece of cake to make the enemies, the key fall, and the door open). The key falling's ID was 1201. The door facing right's ID was 1E0B. 0B in binary translates to 1011, which is the all-enemies-killed bit set, and the 11 which is the right door. Another test I performed was creating a trigger with ID 900 (Aren't all triggers 900?), and set the door-opening interaction ID to 1E07. 07 in binary is 111, which is a trigger pushed and some other stuff and the right-direction door, and when pushed, the door facing right opened.

Sorry, I'm just blabbing on, but 08 should be down opening up when all enemies are defeated (Which it is. Check room 25 of Level 1). And in binary that translates to 1000, which is the all-enemies-killed flag and the two bits represent the down-direction door, which is used.

Who knows, maybe it's all a coincidence, but it makes sense.

(I'm on my phone, so excuse typos)

You did? I wish I would have known that before-hand. This probably means I'll have to add something to remove regional header-based events too.

I thought about interaction scripts, but it's so pointless. There's space at the end of the bank and a lot of interactions to delete. It's kind of a waste of time and asm space. Not much is left in the first bank for the hacker's content so I try to avoid adding scripts as much as possible. I'm on my phone now so I'll explain more later.

Okay, I'm pretty sure I've found the cause (Or atleast this explains the Past Maku Gate staying shut). Around 10F85 in the ROM (Aftually that should be 17. ZOLE changes it to 40) a bunch of the bytes are changed up, and I'm not sure why. But hopefully if I get that all sorted out they'll be fixed.

Edit: Dang... Found out why. Basically the game checks the region headers (What I call them) there and uses them for events, and since a lot of the data is changed for repointing, they won't work. This means I have to make new ASM scripts and a new header system with keeping the old one... Great...

[Opening Doors when All Enemies are Killed]

This is a tutorial on creating the most common dungeon events, such as opening doors when enemies are killed, creating a chest when a trigger is pushed, etc... The list will be updated from time to time.

Opening Doors when All Enemies are Killed

Step 1: Create a Type 2 Interaction.

Step 2: Set the X position to 0. The Y position is the YX location of the door. For example, 5E; 5 being the Y and E being the X.

Step 3: Assign the first 2 digits of the ID to 1E (Always 1E when dealing with doors).

Step 4: Open a calculator that can convert binary to hexadecimal (I recommend Windows Calculator in Scientific Mode). In binary mode, make the code '10', which results in decimal 2. The next 2 bits are the direction of the door to open. 00 is Down, 01 is Left, 10 is Up, 11 is Right (Note these are the directions of the doors, so 00 would end up being placed on the North wall, 01 on the East wall, etc...). So if we wanted our interaction to open up the right door at 5E, the right 2 digits of the ID would be 09 (The binary code we made would be 1001). The final ID of our interaction would be 1E09.

~Lin

ZOLE 4 has been released. The most up-to-date version is 1.26.1. Download it here: http://zeldahacking.ulmb.com/ZOLE%204.zip.

In the future, you may or may not see it at the following locations:

This Forum
RHDN
ZOLE's Blog

This means all other released are frauds or rip-offs. Only download it from the sites listed above, and on RHDN, my name is Lin.

~Lin