Tulunk Village

Kimbles wrote:Since we're getting a bit far into the game, here are some save states for different towns to help with testing: Kurinon, Iris, Freesia
You load them in VBA with the "Load..." option. *nod* The first one's from an old patched version but should work fine, and the other two are originally from an unpatched Speed (hence the Fungus). Let me know if it doesn't work. ^^;

Mind posting battery saves (.sav) instead?

Battery save files ensure that the data in ram is current. Plus VBA save states won't work with other emulators such as BGB.

I don't think VBA lets you use .savs with different names though, which makes them much more annoying to switch between. *shrug* You can always save the game and reload it, I mainly posted the saves to help with checking text which shouldn't be affected anyway. XD

kmeisthax wrote:Okay, so I had an idea today, which I think is going to really help the patch and future Team Tulunk (do we even have a name?) projects. One thing I've been calling for a while is better tooling; we currently have just a text inserter and everything else is done by opening up a hex editor and manually assembling all of our code patches. Well, I just wrote (er, almost done writing) a script which parses xLink map files and overlays the relevant sections onto a base ROM. What this means is that now we can just write our patched code in RGB/ASMotor and have the assembler/linker machinery build our code patches for us. And, as time goes forward and we have more stuff in this new patch tooling system we can accomplish bugfixes by just altering our asm files and producing a new patched ROM.

The goal over time is that the target that our ROM hackers have for achieving modifications is the patch source, rather than in progress testing patches. And instead of having two ROM hackers continuously releasing patches that force the other guy to reimplement their work, they just push nice git commits around on the patch source files and stuff just works.

I plan to use this system to produce my next patch, as a proof-of-concept. Then I want to port all the hacking we've done so far over to Speed Version, but in the new system. So then we'll have a patch source for the entire project. And then having the patch build Power or Speed will be a simple matter of swapping out some include file somewhere which makes a bunch of variables that hold the relevant patch locations change. So basically what I need is a semi-comprehensive list of the things we changed, so that when I go and find those functions and port the patches over I don't make stupid mistakes.

This would be very cool. In fact, I do something similar with my Pokémon Red disassembly: ASM code and data are stored in a Mercurial repository and assembled on-the-fly with RGBDS (a modified version that has the ability to include chunks of a binary file, namely the parts of the ROM that haven't yet been disassembled; other versions of RGBDS do not support patching a ROM).

This has many advantages, especially when working with text: repointing is trivial, and is sometimes not even necessary because certain data can be expanded in place. Assembly files can have comments and variables. Keeping stuff in Mercurial or Git provides many great features like history, bisecting, and an easy way for other people to contribute (I have received several contributions to my project simply because the source is available).

Please, I need help. I used patch v90 on japan pokemon power, and the thing is, everything is good but everytime a denjuu calls, it say something like 08564<578 and it says that when you press A button, and then it goes away eventually. And everytime I talk to people and denjuu, it says the same thing. It not in words when you talk to anyone, its in numbers binary codes that appears. So Please, is there a better patch or no?

Hey, no need to post it twice. Also I don't think we have a patch for "japan pokemon power". XD

Sorry though, that's all you're going to get, because most of the text in the game is still untranslated (as it says in the first post of this topic). It replaces the untranslated text with placeholders to help the people working on it, since the alternative is just having garbled text everywhere (since we removed the japanese font).

The patch is still being worked on, so you can try coming back in a few months and it might be more finished. Sorry there's no better alternative at the moment. :/

IIMarckus It looks like your system hacks incbin to allow including byte ranges from other files. I'm actually doing it the exact opposite fashion: codemodule takes an optional parameter --baserom which tells it where a baserom is. This creates an implicit link-time incbin to every part of the ROM that doesn't have a section overlayed on top of it. Of course, this also means that in baserom mode all the nice section fixing code doesn't matter because right now there's no way to tell the linker what regions of the baserom are free without hacking the assembler. Sooooo... yeah.

EDIT: Actually, I'm going to test the feasibility of patch-rgbds first. Now that I think of it, I can just incbin most of the ROM and progressively overlay more patches until I get a fully documented patch, right?

EDIT 2: Actually, nevermind. I actually got codemodule completed to the point where I can declare patches and they get linked and overlayed over the base ROM. I have no clue if symbol resolution works yet, but I'm going to continue discussion of this in another thread. The plan is to start patching over v90 and progressively move that version back by implementing more code in the new system until we can build the project from the original Japanese cartridge.

Proof: http://i.imgur.com/2dPFy.png

I currently have a little makefile which depends on having a recent version of asmotor compiled. This may be a bit technical to actually install on other romhackers' machines - most Windows machines don't have make and cygwin is a pain to use properly.

shay-shay "Japan pokemon power"? WTF, are you running the chinese pirates? I guess not, because the <<0xaddr>> syntax is our own placeholder for untranslated text. Whenever you see that, just imagine a bunch of translator elves in your Gameboy furiously decoding kana. And wait for the next patch.

Making another post to let everybody know that my little patch-building system is going swimmingly. I switched assemblers from asmotor to the particular variant of rgbds that iimarkus uses, so we get partial INCBINs as well as automatic ROM overlaying. So now I have a little makefile which assembles all the patches (eventually twice when I start working on speed, since it has separate folders for version-specific patches) and spits out a nice ROM.

The current strategy is to build on top of the last hand-built patch and slowly port code over until I can build the whole ROM from the Japanese base. This would eventually require moving text and graphics insertion into codemodule and perhaps some changes to the assembler to better handle automatic allocation of known free space blocks. But for right now I'm just going to worry about the asm.

There's also a bit of an issue of logistics - After some internal doubt and IRC discussion I'm probably just going to put the ASM sources on github unless I can convince wikifang's site host to run a git server (which isn't easy to do). I'm still worried about tightening enforcement of copyright policies in the wake of the MegaUpload bust. On a related note, can anyone give me a solid word that all of our patch history is backed up somewhere? 90% of the links on the patch history page on Wikifang are mediafire links. A few of them are hosted directly on Wikifang, which indicates that we have some sort of file-hosting ability.

That's all for now. I have to go to bed, it's like 3am now...

@kmeisthax

lol, my bad! I don't remember anything that I said back in December 21, 2011.
I had no IDEA of anything that you just said, but all I know that it take a long time to translate the untranslated stuff in the game. But now, you made it easier for me to understand how hard the syntax gotta be replaced with translated words by showing that you have proof on what you are working on.

I will wait patiently for patch v91 to come out.


--------------------------------------------------------------------------------------------------
Edit:

Looks like I couldn't sit and just wait for someone to translate the game!
Well, I decided to answer your question for.

I have backed up every Patches.
I know that wasn't suppose to be my job, but it's good to have it just in case

Heres what I backed up:
1) 90% Patches
2) Changelog
3) Made a list of missing patches that needs to be fixed and added.
--------------------------------------------------------------------------------------------------
Proof:

Main Root - http://i.imgur.com/mOUww.jpg
Patches 2-69 - http://i.imgur.com/YnDVp.png
Patches 69-90 - http://i.imgur.com/31sB1.png
Missing Patches - http://i.imgur.com/E2Egx.png
Change logs - http://i.imgur.com/Mc4NF.png
Change logs extended - http://i.imgur.com/6OOiy.png
--------------------------------------------------------------------------------------------------

1) Do you want me to backup anything else that is important?
2) Anybody have ANY of the missing patches?

--------------------------------------------------------------------------------------------------

Hi guys, I've owned the bootlegged Telefang since i was a small kid when I went on a trip to the Philippines. I had no idea there was a dedicated following for it until now!
Anyway can someone explain to me how to use the patch and ROM?
I'm very new to emulation.

Sorry if this was most likely answered somewhere else, if it was, I couldn't find it.
Thanks so much c:

Obscurimity wrote:Hi guys, I've owned the bootlegged Telefang since i was a small kid when I went on a trip to the Philippines. I had no idea there was a dedicated following for it until now!
Anyway can someone explain to me how to use the patch and ROM?
I'm very new to emulation.

Sorry if this was most likely answered somewhere else, if it was, I couldn't find it.
Thanks so much c:

All you need to do is install Lunar IPS, open your patch file by double-clicking (it will end in .ips extension) and it will ask which ROM to apply it to (we can't provide the ROM or tell you where to get that.) It needs to be applied to the Japanese Power version. Another way to use patches that I think a lot of emulators support (VBA I know of) is naming the patch and ROM the same thing (eg, telefangpatch.ips and telefangpatch.gbc) and it should automatically apply the changes when you load the ROM, without actually editing the file.