No, I'm planning two different patches with somewhat different scripts and graphics to account for both versions of the TV show (Japanese and the US redub). I meant the code being usable with two different scripts, that's all.

And uh, I can't do any sort of ASM work. I'm not a programmer. This is why I asked for help. Crap. :|

You sent me stuff? I didn't find anything in my emails. I think this was around the time you took your sabbatical from the internet. And yes, I had to change a LOT of stuff in the script around, I had to change lots of parts in the script and rewrite half the damn thing to account for the changes in squishy tiles.

And I have to do it again soon because of the second patch.

Sorry.

Not necessarily.

The header just determines whether or not the WRAM present (if any) has a battery.  You can still use RAM without it being battery backed, it just won't save when you quit the emu.

Also, some mappers aren't set up to have WRAM at all, and many of those that do need to have it explicitly enabled via a register write (as is the case here, since this is MMC3).  So you might have to add some additional code to the startup in the program.
 
To enable WRAM/SRAM on MMC3, you need to make sure $80 is written to $A001 (probably some time at startup).  The game might already be doing this -- you can check by putting write breakpoints on $A001.  Hopefully the game isn't writing to it a million times.

You'll have to sqeeze in some extra initialization code, then, if you want RAM at $6000-7FFF

Slip this in somewhere at program startup.... like in the routine jumped to by the Reset vector.  It doesn't matter where, as long the code is executed before any reads/writes to $6000-7FFF

Blech.  If I had a NES debugger handy I might walk you through it, but alas.

Anyway if you can't add two instructions to startup code, I doubt you'll be able to modify the text loading routine, so even if I showed you how step by step it wouldn't do you any good (having RAM to use does nothing if you don't know how to use it).

I'm not trying to sound like a jerk (which I realize I kind of do!  sorry!)  I tried to word this as nicely as I could.  I'm just explaining why I'm not giving a more useful response.  =(

You really might be surprised how easy it is if you sit down, skim the docs, and just dink around.  It can be a lot of work and it takes a lot of stick-to-it-ive-ness, but it's not really that complicated.

I personally don't find it to be that hard and I have no programming experience. It took me a while to get the hang of things, but I'm fairly comfortable now. As long as you know how to properly utilize the tools available to you, you can do a lot of things easily.