Final Fantasy Hacktics

@Jumza
Well, I've never tried map editing so I went to download it (I believe you were referring to Ganesha, I didn't find anything else) to explore it a little. There seems to be a whole lot of stuff for me to figure out but I would manage. I didn't want the atmosphere (the field's color) to change right from the start, but if that's the closest I can get for a colored field to remain during a battle, I'll learn all there is to know from Ganesha. I'll keep that as my last resort because when an idea comes to mind, I want it done right.

Quote from: Xifanie on February 05, 2013, 01:52:45 am
The only alternative to ColorField() is changing the state of the map using the ATTACK.OUT editor. Normally you have a Day, and a Night state, but depending of the map, the latter might not exist. There are actually many map states per map, but we still have no idea how to access them, the game originally only allows to select between 1 or 2 of them.

Can the ATTACK.OUT editor already edit everything there is from ATTACK.OUT? If that's not the case, do you assume I could find those states through hex editing? I'm asking this because I know nothing about hex (or else I wouldn't have asked, I'd already be trying right now). But if there's a possibility for me to do this through hex editing, I will learn how to do it in order to have those hidden and (possibly) unused states be edited to change the field and/or units' color and/or the background's color and have them appear (and remain there) after certain effects take place.

Hello there, I'm a long time lurker and finally decided to post something. I was wondering, is there any way to keep the ColorField command after an event has ended? What I would like to do is have a battle where the background stays in a different color throughout a battle. This would give a particular atmosphere to the battle and I'd love to know how to do this if it can be done. I've tried a few things with EVSP but the field just reverts to normal as soon as the event ends.

I had issues with that, too. What I did to fix it is to save my event in the Custom event directory (it chooses that by default when you save), name it in a way you'll remember what it was. Once it saves, it writes down your event in the event.txt as well.

event.txt (not PSXevents.txt) is the source of the compiler. If event.txt is empty, nothing will change, no matter how many times you compile the event. I believe you can just copy & paste your event in there as well, but I haven't tried it. I just save the event and let it paste itself to event.txt. You will know it worked if it says "Event compiled successfully to offset x00004000" rather than "Event compiled successfully to offset x00002000" which is what it kept doing to me. Mind you, there might be another way around it, but this is what fixed it for me.