Jason777

Nice -- it's pretty convenient that you won't have to be making significant changes to damage tables either.

Cool stuff. What trainer did you use to find these things?

To expand upon that post, I had documented a bit of that myself when helping out HeavyZ with his mod. You can find some notes that also contain information on counter highlighting (i.e. when you have max ammo, the ammo count is green). http://www.cs.utexas.edu/~jason777/OoT_Rebirth/Arrow_Rupee_Decrement/ Old video of the hack that builds upon that documentation:

Porting to MM is something that has always been trouble. It probably has to do with how MM makes much use of animated textures and sets up RAM segments -- a lot of things were probably simplified from a programmer's standpoint for MM and so these things are probably achieved in a subtley different way.

The Market is made up of multiple JFIF backgrounds. You can see this clearly in the documentation you linked.

With PJ64 you would have to reinput all the ROM settings.

I recommend talking to xDaniel because he apparently got the patch working. He probably has the correct ROM to use.

From what I understand, the BPS patch is what actually patches game code to implement the hack. The Python script is just for inserting modified tables that are to be used with the hack. If you need help patching your ROM, I would recommend asking xDaniel. Also, check your private messages.

I am sure you already tried this, but have you applied the BPS patch? Also, it may be a typo but you should be using ZELOOTMA.Z64

What errors are you getting exactly? I've never used the actual hack but you must be referring the python script for inserting updated tables. The actual hack itself was written in C and compiled with Galatea's branch of GCC (which targets the MIPS architecture).

You've given us plenty of updates and screenies to keep us happy I'm liking the model you have for Link's replacement. You just need to group limbs in order to make the replacements via Hylian Toolbox. Knowing that these are beta pics makes me all the more excited to see "new" models!

Sounds like an awesome course. I bet it's pretty expensive considering they give you an Alienware

http://www.cs.utexas.edu/~jason777/Izou_Zelda/Misc/Misc_NOTES.txt Contains relevant information.

That looks flipping sweet. Great job with all the maps I've seen far and your texture mapping is quite precise.

I made that exact same hack about 2 years ago when teaching Sanguinetti how to reassemble actor files and called them "Deku Bombs" haha.

Columns are awesome. Needs more columns.

Unfortunate to hear, xdaniel. Your tools have made modding so much easier in the recent years. I also want to thank you for leaving your source code behind as there is much I can learn from it.

Spinout developed something similar awhile back (mips2c.py) when he was hosting the TBT forums but there was a problem with looping, I think. Anyway, nice find!

Hiya! I wasn't a part of ZSO but I'm sure I've seen your username around

https://www.the-gcn.com/topic/2352-how-to-create-custom-sound-effects-for-oot/?do=findComment&comment=37032 That should teach you what you need to know.

Sweet. I love it when things like this get posted. I'm pretty sure I've downloaded every data archive pertaining to OoT that was uploaded publically since late 2009.

CloudMax, if I could have that information I could find the collision relatively easy!

Collision is still largely unknown but I have few ideas on how to crack it. Think about what an actor (enemy instance) does when getting struck... It might turn red If it was killed, it'll flash white It might play a sound It loses some health It may produce sparks if wearing armor (i.e. Iron Knuckle) So, keeping this in mind, it would make sense to place BPX on one of the function responsible for doing this. Unfortunately, the function responsible for playing SFX is used all throughout the game so you'll have a lot of noise when trying to uncover what you're looking for. You can combat this by silencing all other sounds in the game that interfere (trace back function calls by looking at register $ra). It might be easier to place BPX (breakpoint execute) on the functions that handle health reduction, turning red, hit sparks, or death flashes mainly cause they're specifically related to weapon collision. Anyways, here are function addresses for OoT Debug: 0x8002F828 = extern void playSound(RAMActor* a, u16 sfx_id); 0x80035628 = extern u8 decrementHealth(RAMActor* a); And these are for OoT 1.0... Although it shouldn't be any trouble to find them in OoT Debug: 0x80025B4C = extern void deathFlash(void* gameBase, RAMActor* target); 0x80027090 = extern void highlightActor(RAMActor* target, u32 colour, u32 duration, u32 unk1, u32 unk2); 0x8001D7A8 = extern void hitSpark(void* gameBase, u8 sparkType, CoordU* loc);

If you look at the source code for the hack, you can see that he wrote collision detection for damage. He surrounded an NPC instance with a collision sphere, cylinder, or box and wrote code to see whether or not something came within or touched the box. I don't think he fully managed to understand collision of actors so he wrote it himself.

Copy the display list and do search in the ROM to see if comes up anywhere else. I feel like I've seen the spikes somewhere...