DeathBasket

You can get an mp3 in the video description. That was fun to do and I think it came out well, let me know your opinions.

He's a Time Lord - his tunic is a TARDIS and it's bigger on the inside.

o i c wut u did thar I found what it says but I don't understand what it means.

I don't think they will seeing as Dominic has already composed warp songs based on the default notes the ocarina uses.

This.

also and Yes so I've been looking at cutscene data a little (pointed to be the 0x17 command in the scene header) and here's what I know: nothing Text: 00000013 0000xxxx xxxx = number of entries text entries (follows one of two formats): FFFF xxxx yyyy FFFF FFFF FFFF x = start frame y = end frame (no text displayed) or zzzz xxxx yyyy 0000 0000 0000 z = message number x = start frame y = end frame (waits for text to finish before continuing cutscene) Camera Positions: 00000001wwwwxxxxyyyyzzzz w = ? x = start frame? y = end frame? z = ? following that: ww00 [????] [????????] [xxxxyyyyzzzz] [????] ww = ? FF on last entry xxxx = x position yyyy = y position zzzz = z position Camera Focus: 00000002wwwwxxxxyyyyzzzz ww = ? xxxx = start frame? yyyy = end frame? zzzz = ? following that: ww00 [????] [????????] [xxxxyyyyzzzz] [????] ww = ? FF on last entry xxxx = x position yyyy = y position zzzz = z position The camera will look towards the coordinates specified. There's still a load of unknowns (and other data I haven't even started looking at) so if anybody wants to contribute anything, go ahead.

It appears a three dimensional so you can view it from different angles. It works by combinations of interference and diffraction and physics-y stuff, I did it in one of my modules this year.

That's the idea, but you could also use the leftover space from things that are no longer run to write your own code.

Most people like to mod the MQ debug ROM so here's a few useful things you can do: Make file 1 into a 'normal' file 1. go to B20434 in ROM and write 00000000 over the four bytes there. 2. go to BDF648 and change 15C0001B to 1000001B. 3. go to B20488 and write 10000002 (cutscene fix) Disable noclip (when you press L+dpad-right) go to C1EC04 and change 11E00080 to 10000080. Disable map select go to B96A00 and change the next 0x1C bytes to something. (I haven't been able to remove it without a crash but it can be replaced by the title screen or file select screen...) go to B3D954 and write 10000009 Disable debug camera 1. go to AD0AA0 and change 3B2E0001 to 00007021 (fixes controls). 2. go to AD0AEC and change 11200022 to 10000022. Disable item debug (pressing L at start menu) go to BEEC20 and change 24190001 to 24190000. Fix the ending scene go to B33FF8 and change 1521 to 1000. If anyone has anything else or any improvements on what I've posted then please post them.

The code is much longer than it really needs to be (lazy) so I'll put it in this spoiler tag: For best results, set Navi's initial colour to something like FF007F in ROM. See this page.

Yes, that's what I meant but it seems I said it in the wrong way (or not at all ).

I'm presuming you know the actor data format. In XVI32 select the first byte of the actor data and then do Edit>Block mark. Do the same thing on the last byte and then it should be highlighted in red. Now go to File>Write block... and save it as anything. When you want to put it back into the map go to File>Insert... and choose the file you saved it to. Be careful with that though because it will insert your data but not overwrite anything, so you'll either have to place it somewhere it won't affect anything else or just correct any pointers to other data after it that has moved.

Depending on what hex editor you're using there should be a function to write selected data to a file. That way you can store the actor data in another file and paste it back into your map file after you're redone it.

I haven't really used it properly at the moment but it's looking good. Is saving implemented in the release? I opened the same object after saving and none of the changes I made was there any more. Other than that, would rotation editing be possible using the mouse? It's not necessary but it'd be nice.

I'm pretty sure you can use C code with any C++ development tools, but then again I don't program with C.

Couldn't you use Visual C++? My advice would be to think a little more about the program before you rush into writing it. You should learn how and when to use things like loops and functions too because I'm pretty sure that'd save many lines of code here. I'm not saying you're a bad programmer because you've probably only just started but you should try out some more examples to learn more about the language you use because that will improve anything you program in the future.

omgwtf Well anyway, nice program but I'd recommend being able to choose a ROM without it having to have a specific filename and adding a main loop for the program so you don't have to keep reopening it to use different features; you should try rewriting this as a gui program rather than cli, it'd work so much better.

That's too dangerous! What if it's corrupted and drives you to insanity and eventual suicide? I'm going to brush my teeth.

I just lost the game. I'm not a fan of dubstep but this isn't bad, made me laugh at the end.

punk7890 got me into hacking back in late-ish 2008, I learned a lot about codes and level editing from him and then started learning about porting maps, objects, etc. Most of the things I did from then were just small map/object/music modifications. I didn't do any real hacking until I started looking into assembly hacking some time about a year ago, but I don't have a huge interest in hacking so I don't get much done.

Pokémon Black (DS) GoldenEye (Wii) Donkey Kong Country Returns (Wii) Wii Party (Wii) FIFA 10 (XBOX 360) That's since December. I plan on buying Ocarina of Time 3D and Star Fox 3D as soon as I convince myself that the 3DS is worth spending £200 on just for remakes of good Nintendo 64 games.

Sorry if I'm hijacking this thread but this program may come in more useful: Download It's something I started ages ago but never got close to finishing (as in I've only done about 5% of what I planned). I saw this thread so I decided to dig out my terrible program and compile it. Credit to the people who found information I used (or was using) - namely sakura, Flotonic and myself.

Fun fact: What you see in the video was an assembly hack since at the time I couldn't be bothered to go back and find where the values were actually set. Here are the addresses, values are one byte each: RAM: 800ED55F - A button 800ED5A3 - Bottom C 800ED5DF - Right C 800ED61B - Left C 800ED65B - Top C ROM: B646FF - A button B64743 - Bottom C B6477F - Right C B647BB - Left C B647FB - Top C The notes start from C (00). The default values are 02 (D), 05 (F), 09 (A), 0B (, 0E (D). Have fun with custom ocarina songs now that you can use any notes you like!

This. Back when OoT came out I didn't know anyone who didn't have a gold cartridge; to this day I still only know one person who has a grey one. I'm pretty sure the gold one is the most common over here though and it won't be worth anywhere near as much as the gold US cartridge.