Final Fantasy Hacktics

Now now, I know what you'll say: "There's nothing wrong with IRC!" And you'd be correct!

But IRC is for old people. So, for all the youngsters that refuse to get off my goddamn lawn, I decided to create a Discord server. I won't be necessarily very active myself on it myself, but I will receive and look at my @mentions and check from time to time. All of the admin team (Team XENA) will be available on IRC, and most of us should be on Discord too.

Why did it take so long?
It took this long for Discord to get its shit together when it comes to notifications. It looks like I can finally get @mentions on there for what really matters without having to mute everything

I use pSX's r3000 debugger to view code live and edit the memory directly, but otherwise to compile your own code in MIPS there's MassHexASM or my FFT Hack Template Spreadsheet

ori r2, r2, 0x8001
The PSX memory/registers being little-endian, that means that it will OR 0x01 on 0x004B's value and OR 0x80 on 0x004C's value, which is what we want and why it works.

I can explain more if you're still confused

Quote from: nitwit on March 30, 2020, 05:42:14 pmIt's more tedious than difficult

My ASM dyslexia says otherwise lol.

That's a really cool project though, I approve! I've always been super thankful for the wiki documentation and the more there is, the better. 🙂
I wish I could help (hell I wish I could've when I was healthy), but I'm going to leave it up to you and others!

Good luck! Great project.

Wow I can't believe you had me manually enter hex in my emulator's memory just so I could know what the code was. :v
I wouldn't have done it if I didn't still have it open at the right spot... just give me the code the next time lol.

You're using lh/sh on a non-aligned address. This is not a good idea and I can't say what sort of issues it could cause, but it will probably vary from emulator to emulator and with the live console.

i.e.
lb/sb can be used with memory addresses ending with 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F
lh/sh can be used with memory addresses ending with 0,2,4,6,8,A,C,E
lw/sw can be used with memory addresses ending with 0,4,8,C

Using your code above with 01 80 42 34 (ori r2, r2, 0x8001) instead of 01 00 42 34 (ori r2, r2, 0x0001), will accomplish what you want, and you can use it for your own personal mods, but you should never release code like this to the public.

I think your issue is that you're loading from 4B and 4C, but only storing in 4B.

It's not really supposed to change anything else on the settings page.
Your ID is 1, so in FFTPatcher, type 1 in the box that I labeled as 169. That's it. The option between 169/16B is just in case someone has a conflicting hack using the unknown/unused 169 box, but I doubt anyone have ever made a hack that uses either of those besides me.

And I decided to update the spreadsheet to fix that bug just in case: Special Snowflakes v1.02.xlsm

What's your code like?

From looking at the code you should be using ori 0x0001 on unit stats 0x004B and ori 0x0080 on unit stats 0x004C.
It sounds like you're using 0x0001 on 0x004C which is the flag for armor.

Decided, against my better judgment, to make the FFT Style the default one... Enjoy?

Yes, it's still fairly incomplete, but I figured it would be better than waiting many more months stuck with the default SMF theme.

Updated the rules! Fewer of them, made them way shorter, less bloated, and more comprehensive. 🙂

They're not text; they're images.

You can find them in Shishi, or more precisely, under the Other Images tab:
- WLDTEX.TM2\3 - WLDTEX (3)
- Pre-Battle Location Text Images\*
- Chapter Titles\*

Quote from: RetroTypes on March 26, 2020, 05:26:00 pmAlso Xif I have no idea how your Snowflake spreadsheet works lmao I'll keep playing with it but any pointers would be great.  :p

Modify a row how you want your unit to be (like 150% PA will generate the unit with 150% PA), then take the ID on the leftmost side of the row and set that in FFTPatcher as shown under the Settings tab, either the 169 or 16B box.

@evisceratus
Thank you.
I updated php.ini to set all of those values to true + Strict.
For SMF, I suppose we'll have to wait for an update. I made the cookie HTTPS, but there's no option for SameSite yet.
I also updated the links you mentioned.

As in closing the program and re-opening it

No, I meant loading from a savestate then loading a hard save could cause the issue to happen. You might even have to restart the emulator, I'm not 100% sure.

Quote from: Punkioinapit713 on March 13, 2020, 07:11:23 pmWhile sorry, what I mean is that I can change everything using the editor yet none of it saves I'll go in the game and it plays as it was before I tried to edit it.

You say you're using pSX... are you loading a savestate before trying to load a hard save? pSX doesn't update the memory card data on the fly; it keeps it in memory. You have to re-launch the game entirely.

If that's not it, it could also be forgetting to change back to mcr, updating the wrong memory card, etc.

I guess the better question if none of this worked: If you reload the file you edited in Tastic, are your changes there or not?

@FickleLemon
What I'm getting is that for you, this bug is probably normal behaviour.

For us, eventers of expertise, we have no clue what you could possibly be talking about, so you'll really have to walk us step by step through what you did, and describe us precisely what you're trying to accomplish if you want a proper answer in a reasonable time frame.

We can't even begin to guess what you've done to cause this issue.

Help us help you!

In war we served by keeping seagull out of our land!

It's just dummy text. It's only present in the US PSX version. You can use Raven's edited scripts which removes it out if it bothers you... it comes in a folder alongside EVSP.

@Squaresoft
IIRC it identifies which set will be used. So, in the screenshot above, 0-5 would use the 1st set, 6-9 the 2nd, A-D the 3rd, and otherwise the 4th. Yes, there are used to determine when random battles can take place, with 0x006F Shop Progression as the default.

I'm the one who discovered and analyzed this data, but it's been a few years since I last played with it.