TheUntoldLyric

From just the few hours I worked with it, I figured most of that out myself. Regardless, thanks for the verification, that way I know what I thought was the right idea anyway. I didn't notice we had a complete document for cutscenes though, everyone I saw talking about made it seem like we didn't have the knowledge to make them. I suppose I should've looked into our documents a bit more for it before I posted..Oops. Thank you, regardless.

Has anyone documented the saved 'cutscenes' you can make with the Debug Camera? See: http://tcrf.net/Proto:The_Legend_of_Zelda:_Ocarina_of_Time_Master_Quest Specifically: "The Demo Control allows you to save your newly created movie to the Memory Pak plugged into the third controller." Aside from what it says, I've found nothing else about it. Has anyone even tried to ever take the 'movie' out of the save and import it into the rom itself? I'm going to try tinkering with it shortly, myself. I figured I might post about it as well, just in case.

I've been around since ZSO, though under a different name. Since I've lurked, I've gathered many different documents and stuff I thought would be useful when I actually 'did' ever make a hack. Although I'm not always active in Z64 hacking, I try to keep updated with news, tools and documents people post or update. Once a year, roughly, I dig around and see what new information I can save to maybe use 'someday'. Sadly, most of my stuff did actually end up getting wiped a couple years ago. So I 'did' lose some smaller, less important documents. A few days ago I decided to do my yearly information raid. I also decided perhaps others might benefit from my hoarding. The Z64 hacking community has a horrible habit I've noticed over the years. Keeping their information sprawled all over the place. Since ZSO and the smaller sites after it imploded on themselves, the community spread to several smaller information outposts. Glitchkill, GCN and Maco are a few of these outposts, not including the many wikis. Because of how many different sites there are, information tends to get cluttered about even worse, then someone from one site finds something valuable, yet the other sites arn't aware of it. I hope that this .rar and the documents within can be of some help. Even if all the documents are old news to you specifically, I hope it'll at least serve as a offline database of sorted documents. -From the Readme -- That said, this .rar contains nearly everything but the kitchen sink. Tools, some Patches, Tutorials and alot of other documents. All 'mostly' sorted out and named in a (hopefully, mostly) orderly fashion. Keep in mind, (also said in the readme), because of my previous HD failure, I did lose alot of misc little documents. So if alot of stuff in here seems new, it's probably because it is. Don't get the wrong idea though, theres plenty of older documents and archived posts in here. All that said, It's nice to see the community still around. Keep up the good work, every time I come by to do my raids, I'm always impressed with progress. I hope this archive can be useful, even if it's all known to you. www.mediafire.com/download/w2cgipqwj5in6jb/SortedNotes.rar Also, I wasn't entirely sure where to post this. Hopefully this is the right subforum.

I would like to change the 'collision' size of a held item. Say, a Broken Giants Knife. How would I go about doing this? I already tried to disassemble when a enemy was hit and try to follow the code back to the weapon damage to see if it was around there. I also tried a few other misc breakpoint disassembly stuff, some of which was with the Infinite Sword Glitch enabled. I also tried to use Cheat Engine and searching for changed values when I switch to a different weapon/slash with a different weapon, though this idea might be initially flawed because the collision isn't just one changing object, I don't think. I'm not actually 'too' familiar with assembly. I've done some smaller, simple assembly hacks for some SNES games, yet it seems alot more difficult to do anything on the N64. Maybe because of how much more data it is, or the UI of the debugger, or I simply don't have my mind fully around assembly yet. Regardless, I've had no luck these last few days. Can anyone with a little more experience than me give me suggestions on what to look for, or better yet, lend a hand in looking? Thanks in advance for any help.