NINJA 2.0.0.0 Final Delayed

This weekend I’ve been feeling pretty sick, and any time I do have is going into our code crunch for Monday’s eForms alpha at work (eForms is the half of our company’s accounting software that I am in charge of). As of now, I’m still behind schedule and chances for a mostly functioning alpha look bleak. I would pull an all-nighter and make it happen, but that would leave me dead on Monday night, and that’s not an option since Monday is 七夕.

I can promise you whatever delay there is will be worth it. NINJA is currently halted while I restructure libPirate to be a class-based library. NINJA will basically become an interface to accessing libPirate’s functions. In fact, if you look at the current version, most of its code is mirrored in libPirate. This means users can upgrade NINJA just by dropping in the latest libPirate stable release.

I’ve also rewritten the GUI to access NINJA as an asynchronous process so NINJA will no longer freeze when you apply or create a patch. I also plan to make the console output more verbose to give better indication NINJA is still running.

NINJA 2.0 beta test

For those who have been following on the ROMHacking dot net forums, you may know I’ve been actively developing the NINJA 2.0 format for the last month. There have been several beta tests on the forums, and I think it’s finally ready for a front-page notice.

Link removed: http://ninja.cinnamonpirate.com/

Read the rest of this entry »

Sidebar

I just noticed Evil Peer released his teaser for Temporal Flux in NINJA format. Kick ass

Wow, another NINJA

Thanks to MadMalkav for sending me this one.

Someone named Nemesis has released a new patcher that has partial support for the NINJA file format. It’s called Ouinja. I haven’t tried it yet, but according to the author it’s very fast.

Read the rest of this entry »

Urgent update

Please upgrade to NINJA 1.01 if you previously downloaded it. There’s an error with the support for binary patching–a value of 0 for the CRC32/MD5/SHA1 is supposed to tell it to ignore the check, but it wasn’t accepting 0.

This shouldn’t affect any patches made with version 1.0, it could only be a problem for if someone made a derivative work that wrote 0 for one of these values–NINJA 1.0 writes true values for all 3.

Just an extra alert to anyone who might be making a derivative work: “unk” is the value textual patches to ignore a check. 0 is the value in binary patches. To be more precise, the entire range being ignored should be 0. So if you’re ignoring the SHA1, you’d replace that field with 20 bytes of 0×0.

Frisbee eating fun

It’s finally done! I’ve devoted the last two and a half days to non-stop programming of it, and it’s done. Thank god …

I wrote a new series of patching formats designed to be a bit more powerful/flexible than IPS and PPF, and with a mind for them to be able to continually expand as systems and file sizes grow. The format will support 2040-bit addressing, which means a file 2^2040 bytes long. Why do I write in exponents you ask? Because that longer than a googolplex^600 — in other words, I should be an old man with gray hair before this format ever hits the wall with addressing.

Read the rest of this entry »