I want to hack LoZ OoT in LemAsm - N64 Rom editor. Help please.

[Guardian]

I'm new at this sort of thing. I havent gotten down on how to use that editor. I have the rom. Just having trouble using the editor. What exactly do I need to do first hand?

My goal to hack this rom is only the design from Majoras Mask of Oni Link and place it over Adult Link and replace the Biggorons sword with the Fierce Deity blade as well. Thats what I want to do. And I know that would be really awsome. I also have the MM rom as well.

Can anyone lend me a hand to get started. Please?:down:

 

[cooliscool]

Umm.. that's not really possible, especially with a tool such as LemASM. It's designed for hex viewing/editing to help troubleshoot issues.

 

[Guardian]

cooliscool, would you or anyone else know of any N64 polygon editor out there on the net that would allow me to make this possible?

 

[Jesterhead]

I dont think that this would be very easy, maybe you look better for a cheat or something, if you cant find a cheat for changing Link, then you can expect that this is not very easy

 

[matarina71]

cooliscool, would you or anyone else know of any N64 polygon editor out there on the net that would allow me to make this possible?

Wouldn't Blender do the job? It's multi-platform and free.

 

[blanky64]

I think I remember Lemmy's graphics plugin can perform VRML-exports of the world, although there's (currently) no way to import it back in again...

And, as far as I know, you can't feed Blender N64 ROMs

 

[spoondiddly]

There are only two model inport/export programs I know of at the moment, and both are in development. The formats really aren't that bad, but the mapping can be a bite if they use a lot of crazy effects. Then again, you don't really need to edit the models it seems, but just swap them about. That's hex editor stuff, and shouldn't be too much trouble.

If you only wanted to swap models, both games share the same encryption, so you might (emphasis on *might*) be able to replace the compressed binaries. That's probably a lost cause, though, unless you know where all the image tables are; you can shift around any rom address tables used to access the objects, assuming they don't fit in the space allotted; and if you get very very lucky and there isn't some unforseen problem that causes it to crash.