• Welcome to Final Fantasy Hacktics. Please login or sign up.
 
June 16, 2025, 04:30:30 pm

News:

Please use .png instead of .bmp when uploading unfinished sprites to the forum!


Custom class and spell trouble

Started by Jennifer Darknight, April 24, 2013, 01:18:25 pm

Jennifer Darknight

April 24, 2013, 01:18:25 pm Last Edit: April 24, 2013, 01:42:13 pm by Jennifer Darknight
Okay, so I'm having a bit of trouble.

I created a custom class for Teta utilizing FFTacText and FFTPatcher, and on the appearance, everything is fine. The class name shows up in the menu, and I can even use the abilities in battle (Since I'm simply testing her class to see how she plays so I can tweak accordingly, I threw her in the Gariland battle), but when I click on her job status in battle, it shows her main class as "Delita's Sis" (instead of my created class, Acolyte, which takes the place of Bishop rather than the Delita's Sis class), and has the class mastered.

And yet when I use skills...it's got a selection of spells that I used for my custom class (Short of three, but I'll get to those) already mastered.

And on those three spells...they're custom spells that I'd created in FFTPatcher, used on the template of Deathspell 2, Wish, and MBarrier (and edited accordingly). I messed around with the values, and on the patcher everything looks fine (the spells are renamed, they're lined up okay, and the values are fine), and yet when I play the game, my custom spells aren't there. Instead I have vanilla MBarrier, Deathspell 2, and Wish, with the flavor text and everything.

Clearly I'm goofing up somewhere, and I'm not exactly sure...where it is.

Edit:
I played around with some of the things in ENTD, and Teta at least doesn't know every skill that her skillset has to offer, but when I go into the menu, I still get the Delita's Sis class option, and my spells are still wonky. : | I'll try fiddling around with a few more things.

Choto

I seem to remember some type of hardcoding for Teta's class... you may want to try putting her in another job slot/skillset. I forget what is involved with doing all of that though.

RavenOfRazgriz

The thing I keep telling everyone ever is wrong here.

Your Job ID MUST match Sprite ID.  This has nothing to do with hardcoding.  For the Job to correctly work in battle, since you're using Sprite 1C Teta, you MUST use the Job 1C Delita's Sis slot.  If you want to use a different slot, you need to move Teta's sprite into the matching Sprite location.  (Note that ShiShi has the Sprite IDs labeled incorrectly, using base-0 instead of base-1, so in ShiShi it will be 1B Teta, etc., but this is actually 1C Teta.)  This is why units like Gafgarion and Rafa actually have two different Sprites on the ISO - each Job needs its own Sprite to function correctly.

Glain

"Sprite Set" in the ENTD is also the unit's base class (I really thought that value was labelled "Sprite Set / Base Class" instead of just "Sprite Set"), so the only available classes for any given unit will be the base class (the job with the same ID as the Sprite Set, or Squire for generics) plus the generic jobs. 

You can force a unit's current job to be anything, via the Job dropdown in the ENTD, but that doesn't actually make it an available job for the unit.  That's how you can be in a job without it appearing anywhere on your job list... a rather interesting situation.
  • Modding version: Other/Unknown

RavenOfRazgriz

This is also why, if you're familiar with the older versions of 1.3, Miluda at Thieves' Fort could come in with the Bomb skillset randomly, causing hilarious chaos and fun for the whole family when she Self-Destructed on your face and killed your entire party.

Jennifer Darknight

Okay! Wow, that does make things a hell of a lot easier. I fixed it to where the sprite, job, etc match up, and everything works fine. Even my custom spells are working, and acting as...well, themselves and not something else entirely.

Strange thing, though. For some reason, the description on one of my spells is doing this:




RavenOfRazgriz

Shorten your description so the pixel length is less than 200.  That's what happens when you break the pixel width, but not enough to make the game crash just yet.

The actual legal width is closer to 210 I think but a good rule of thumb is to keep it to 200 pixels and 4 lines of text.