Ty for the reply.
Do you know if its possible to do with spreadsheets? At least for Ramza.
I think it's important to mention my design intentions: The "one trick pony" thing doesn't really concern me too much. Cid in vanilla, for instance, surely was a OTP but that didn't stop him from being one of the best characters in the game. I want the players to have to choose between more of the classes and actually use more strategy in their formations and character builds rather than deathballing or 1-shotting everything. Having Ramza be a specific, and limited, character would force players to use their generics to fill in the gaps in his ability rather than just replacing characters to make the same build on a separate one with better scaling.
I was doing a run of KO and got to that point. Why keep my first 6 generics when Rad, Alicia, and Lavian are better in every conceivable way and have 70/70 brave/faith? I want uniques to feel unique, but I also don't want this to be the difference of 1-3 skills (vanilla Ramza, any holy swordsman, etc).
I guess you could think of it like Darkest Dungeon, if you've played it. All of those characters serve one specific function, with a variety of in-class skills, but are still powerful and useful in their own rights, especially when customized with items. MOBAs work the same way actually. The comp and builds make all the difference to the point where you can play thousands of games with different builds/comps. That is far more strategy to me than stack speed on your strongest character and have him one shot everything. That would actually be fine if the comp wasn't 5 "strongest" characters, since there is only so much I can do with the AI especially without having to change the layout of every single battle to make them more strategic.
It may be a stretch to do this with generics, but I certainly wouldn't mind it for Ramza and also for "special" characters. With that being said, since this is FFT and not DD, I would want these characters to still have secondary jobs or at least 1 full job tree.
Do you know if its possible to do with spreadsheets? At least for Ramza.
I think it's important to mention my design intentions: The "one trick pony" thing doesn't really concern me too much. Cid in vanilla, for instance, surely was a OTP but that didn't stop him from being one of the best characters in the game. I want the players to have to choose between more of the classes and actually use more strategy in their formations and character builds rather than deathballing or 1-shotting everything. Having Ramza be a specific, and limited, character would force players to use their generics to fill in the gaps in his ability rather than just replacing characters to make the same build on a separate one with better scaling.
I was doing a run of KO and got to that point. Why keep my first 6 generics when Rad, Alicia, and Lavian are better in every conceivable way and have 70/70 brave/faith? I want uniques to feel unique, but I also don't want this to be the difference of 1-3 skills (vanilla Ramza, any holy swordsman, etc).
I guess you could think of it like Darkest Dungeon, if you've played it. All of those characters serve one specific function, with a variety of in-class skills, but are still powerful and useful in their own rights, especially when customized with items. MOBAs work the same way actually. The comp and builds make all the difference to the point where you can play thousands of games with different builds/comps. That is far more strategy to me than stack speed on your strongest character and have him one shot everything. That would actually be fine if the comp wasn't 5 "strongest" characters, since there is only so much I can do with the AI especially without having to change the layout of every single battle to make them more strategic.
It may be a stretch to do this with generics, but I certainly wouldn't mind it for Ramza and also for "special" characters. With that being said, since this is FFT and not DD, I would want these characters to still have secondary jobs or at least 1 full job tree.