- Apr 14, 2019
- 1,187
- 3,389
- 499
There's quite a lot of coding for FFFox, and while the early versions were mainly call-and-answer events to prevent touching the main code too much, I've changed focus since to changing the code wherever needed, and just manually adding in the updates Inusuku brings, rather than porting from version to version. However, once the Kitsune update comes out, it shouldn't be too hard for one to do a simple image replacement, outside of a couple images, if one wanted to port a kitsune only version.I have to admit that my delusions were running away with me when I said I still have hope that FFFox mod might get ported to mobile.
After thinking about it some more, it probably is possible, but I honestly don't want anyone to go through with it considering how much time and effort it would entail, and I especially don't want BlueFireNick to do it, because I want them to spend as much of their free time as they healthily can making FFFox mod as good as they want it to be.
I'm not a complete beginner in terminal, so I plan on making some scripts to automate changing all the images from a standard decensor and base PC version into their counterparts for the mobile version. That way it won't matter which colour version comes after that, I can just overwrite the source files and use the scripts to convert them again.
Thanks for the warning on changed images and image combinations though, honestly until yesterday I didn't notice the (I swear I know the proper word for the 400x100 images back from when I used faststone viewer on windows) because there were so few of them in the directory. (maybe horizontal collage, either way I know how to stitch images together so that's not a problem)
I have a feeling it might be more of a pain in the ass then I first anticipated to check for any smaller changes, though.
I'll probably end up using transparency layers in gimp to make sure everything lines up before automating it.
I'll spend a while learning the process on daseson's monochrome colour version, when I've got it right I'll upload it to the monochrome page so everyone there can have it.
What I am a complete noob at is bugfixing rpg maker errors, no way I could have fixed all the stuff you've got listed in the readme for monochrome, so I think I'll completely give up on the translation for anything other than the internal names readable by Joiplay.
what else was I thinking as my abstract minded self.
right, the readme.
I'm copying the format of your readme and I've edited the Joiplay cheatmenu tutorial with some more tips for the later versions, like changing the default gamepad to have F5 and F12 on the second cycle, using the on screen keyboard to interact with the cheat menu, and the tabs that you'll generally want to use: items, variable and switches.
I've got placeholders throughout my ~Fantasy~ readme for the version names and stuff anyone might want to keep in mind, and reminders for my self.
I'll probably upload a version for proof reading and other stuff to include later in case anyone is curious.
Also contains a shameless request for someone to upload the mobile version when they get get it next month.
Also absent mindedly I realized that fox eared imouto is coming to the FFFox mod sometime so I added that to my TDL to repack as much of it as possible in another directory.
The FFFox and daseson color mod updates are my most looked forward to things next month. Making the mobile fantasy version take 5th place.
Also, I know at least some of Inusuku's files are already multi-frame images, such as the hscene folder, the eyebrow, eye, and mouth files, etc, and is possibly a technique Inusuku learned from them porting the last game (Inusuku's code has obvious improvements from the base game to this latest update). So that part depends on just how much they change it to fit the new engine. Good luck with your project.