[PSX/PC] General editor - Hades Workshop (0.50b)

[anxietymafia]

Is it possible to make Garnet use her short hair model on the field?

 

[Tirlititi]

Unfortunatly, this is mainly hard-coded. You can change it using the tool dnSpy but not Hades Workshop only.
In dnSpy, open the Assembly-CSharp.dll, search for the following classes and methods and edit a few lines:

1) In the class "ModelFactory" and its method "CreateModel", there's this block:
Code: [Select]

 if (ModelFactory.garnetShortHairTable.Contains(text)) {  ushort num = BitConverter.ToUInt16(FF9StateSystem.EventState.gEventGlobal, 0);  bool flag = num >= 10300;  if (flag)  {   // etc... Disable "long_hair" components  }  else  {   // etc... Disable "short_hair" components  } }

Replace the "if (flag)" line by "if (flag && isBattle)".

2) In the class "EventEngine" and its method "DoEventCode" (that's a very long one), there is a "case EBin.event_code_binary.MODEL":
Code: [Select]

 case EBin.event_code_binary.MODEL: {  posObj.model = (ushort)this.getv2();  Obj expr_1EA4 = this.gExec;  expr_1EA4.flags |= 1;  posObj.eye = (short)(-4 * this.getv1());  if (this.gMode == 1)  {   string text = FF9BattleDB.GEO[(int)posObj.model];   posObj.go = ModelFactory.CreateModel(text, false);   GeoTexAnim.addTexAnim(posObj.go, text);   if (ModelFactory.garnetShortHairTable.Contains(text))   {    posObj.garnet = true;    ushort num7 = BitConverter.ToUInt16(FF9StateSystem.EventState.gEventGlobal, 0);    posObj.shortHair = (num7 >= 10300);   } // etc...

Change the line "posObj.shortHair = (num7 >= 10300);" to "posObj.shortHair = false;".

There might be a third method to change, the method "addTexAnim" of the class "GeoTexAnim", but I am not sure if it is important or if it would mess up with the battle model.
And there would be a 4th one, "ff9play::FF9Play_GetSerialID", if you wanted to change her model in battles as well.

 

[anxietymafia]

Thanks so much for the reply,

Is this also possible for the psx version?

 

[Tirlititi]

No, sorry.

 

[Clem Fandango]

I've been working with the tool for a while now and I'm trying to find a way around how Phoenix Downs interact with undead monsters.

Specifically I'm trying to find a way to make the item no longer bring the HP of undead targets down to critical HP levels. My initial thought was to have the item use the Life formula, but that doesn't appear to work since there's no hit rate section for items (unless I'm totally blind) and Phoenix Downs using the formula don't seem to work on dead allies either.

Part of the problem is that I still want to have undead targets take damage from restorative sources since I have at least one spell in the mod based around doing that, so taking away the undead type from enemies isn't something I want to do. I've also noticed that granting enemies Easy Kill status doesn't seem to make them immune to the effect either (which is wild to think about, honestly), so I'm not sure if there's something I'm missing to make this happen.

Worst case scenario I can just make Phoenix Downs really expensive so just chucking them at zombies and such isn't economically feasible, I mean if it's good enough for FF5 it's good enough for me, but I wanted to ask and see if there's something I'm missing.

Also, apologies if this has been asked before, I did a brief and possibly bad search and couldn't find anything.

 

[Tirlititi]

Hello Clem Fandango. Sorry I didn't see your message before.

It is not possible to do that without modding the battle engine. It can be done either with Albeoris's Memoria tool or with dnSpy, but not directly with HW (or only with added difficulties for no reason). In both case, it's a bit of C# coding.

Using Memoria, you need to change the script of Phoenix Downs (inside "Scripts/Sources/Battle/0072_ItemPhoenixScript.cs"):
Code: [Select]

public void Perform(){ if (!_v.Target.CanBeRevived())  return;  if (_v.Target.IsZombie) {  _v.Context.Flags |= BattleCalcFlags.Miss; // Add this line  return; // Add this line//  if ((_v.Target.CurrentHp = (UInt16)(GameRandom.Next8() % 10)) == 0) // Remove this line//   _v.Target.Kill(); // Remove this line } else if (_v.Target.CheckIsPlayer()) {  if (_v.Target.IsUnderStatus(BattleStatus.Death))   _v.Target.CurrentHp = (UInt16)(1 + GameRandom.Next8() % 10);  _v.TargetCommand.TryRemoveItemStatuses(); }}

Using dnSpy, you need to change the method "btl_calc::CalcMain" and more specifically the "case 72":
Code: [Select]

if (Status.checkCurStat(target, 64u) || btl_util.CheckEnemyCategory(target, ENEMY.ENEMY_CATEGORY_UNDEAD)){calc_VAR.flags |= 1; // Add this line// Remove the following lines, "if ((target.cur.hp = (ushort)(Comn.random8() % 10)) == 0)" and "SetEnforceHP0"}else if (btl_calc.CheckNotPlayerMiss(calc_VAR))// etc... no change there

 

[Clem Fandango]

Hypothetically, were I to enact the change using dnSpy, would the HWS files used by Hades pick up that change? In other words, if I wanted to distribute a mod as an HWS file, would folks playing the mod still need to make the same changes in order for the Phoenix Down change to be in effect? I'm just trying to figure out which way I should go about this while making it as seamless as possible should I choose to release a mod.

 

[Tirlititi]

No, the .hws wouldn't hold that change.
That's a real problem for me as well as I would largely prefer to have only 1 file for the mod, but the nature of the change is just not embeddable in a .hws... so I decided that I would distribute the C# code as well (generating the mod then requires Memoria or dnSpy in addition to HW).
Using Memoria, it's simply a .cs file to share in addition to the .hws (and then I think that you need to run Memoria's script compiler, but that's easy).

In any case, the default way to share a mod is not to share the .hws (+ maybe C# code) but to share the generated Steam files (p0data, DLL...).
Even if it creates mod compatibility problems, that's the easiest way to do it, both for the modder and the user.

 

[Clem Fandango]

Thanks for the reply, I was afraid this might make things kind of complicated. I think for the moment I might keep working on other stuff and leave this towards latter parts of this whole process. It's generally not a showstopper for what I'm working with, but I'll definitely need to consider it further if I ever end up releasing anything.

 

[Clem Fandango]

I've got a question regarding spell sequencing that I didn't see mentioned anywhere in the FAQ.

Is it possible to take a spell that normally has animations set to one target to affect multiple targets instead?

For a specific example (not to mention exactly what I'm trying to change) is something like Shell. The Shell animation in the game only hits one target. What I'm hoping is possible is set the spell sequencing so that the Shell animation hits every target in the party in sequence, similar to how something like Mighty Guard works. I'm not even entirely sure if this is possible due to engine limitations and my experiments in making it do this through editing spell sequencing has generally resulted in crashes. I'm under the impression that this isn't doable, but I wanted to check in this thread first.

It's not a huge issue and if it's not possible I'll probably just opt for the Mighty Guard animation instead or something similar. I've just found through play testing that there's never really any ideal situation to cast just Shell or Protect; both effects don't last very long even in ideal circumstances and while the bonus they have is nice, it's not super necessary in vanilla and I wouldn't want to wind up making it mandatory either. It's fairly weak for a single target buff.

 

[Tirlititi]

It's not possible to make it look nice, unfortunatly :/
The spell animations are the biggest black box of the game now because it's delegated to an external DLL in the Steam version and I can't access its source code, either to see how it works or to modify them (all the possibilities and informations for that section were obtained the old way: guessing and testing).

You may however make Shell's animation hit all the targets in effectivity. For that, you simply need to change the line "Effect Point: 1st target" to "Effect Point: all targets" in its Spell Animation sequence. It will only display the effect on the 1st character though... so I guess that Mighty Guard's animation is still a better choice anyway.

 

[Clem Fandango]

Ah, okay. Thanks, I appreciate the detailed description.

Also I realized there was an easy workaround for the whole Phoenix Down undead thing I mentioned a couple weeks back: I can just change the targeting so that enemies cannot be targeted with Phoenix Downs, it seems so obvious in retrospect.

 

[Clem Fandango]

I've got another question that I haven't been able to find an answer for, either here or on the Steam page.

I've learned how to change the content of Chocograph contents, which is great. I'm wondering if it's possible to restrict when certain Chocographs can be obtained. Specifically I was hoping to be able to push the choocgraph that grants the Ocean movement to being only obtainable after Gulug and the final piece of the flight chocograph to be obtained only after Ipsen's castle, or possibly even into Disc 4. I've looked through various scripts, but the truth is that I don't really know where I should be looking or what it is I'm looking for. Is this even doable in the first place?

 

[Tirlititi]

At some point, I wanted to register the local variables of the Hot & Cold scripts but it is quite a big system and that work went on standby...
The main function (the one deciding the reward at least) is "Barrel_41" in the Chocobo Forest, "Barrel_38" in the Lagoon and "Barrel_46" in Air Garden. It's always the same. Here is that function with most of variables given a name.

The part you're interested in is close to the top of the function:
Code: [Select]

            switch 3 ( Chocobo_ChocoColor ) from 1 {            case +0:                if ( Hot&ColdField == 1 ) {                    set ChocographAvailableList |= 8 // 4th Chocograph (Yellow to Light Blue)                    set ChocographLastAvailableFlag = 1                }                break            case +1:                if ( ( Hot&ColdField == 2 ) && ( Global_ScenarioCounter >= 9400 ) ) {                    set ChocographAvailableList |= 2048 // 12th Chocograph (Light Blue to Red)                    set ChocographLastAvailableFlag = 1                }                break            case +2:                if ( ( Hot&ColdField == 1 ) && ( Global_ScenarioCounter >= 9400 ) ) {                    set ChocographAvailableList |= 8192 // 14th Chocograph (Red to Deep Blue)                    set ChocographLastAvailableFlag = 1                }                break            default:                set ChocographLastAvailableFlag = 0                break            }

Without renamed variables (as it appears in Hades Workshop), it's this part:
Code: [Select]

            switch 3 ( Chocobo_ChocoColor ) from 1 {            case +0:                if ( Chocobo_CurrentField == 1 ) {                    set VAR_GenInt24_172 |= 8                    set VAR_LocUInt8_8 = 1                }                break            case +1:                if ( ( Chocobo_CurrentField == 2 ) && ( General_ScenarioCounter >= 9400 ) ) {                    set VAR_GenInt24_172 |= 2048                    set VAR_LocUInt8_8 = 1                }                break            case +2:                if ( ( Chocobo_CurrentField == 1 ) && ( General_ScenarioCounter >= 9400 ) ) {                    set VAR_GenInt24_172 |= 8192                    set VAR_LocUInt8_8 = 1                }                break            default:                set VAR_LocUInt8_8 = 0                break            }

So you see, you only need to increase the scenario counter lower bound for this special chocograph availability. Here are a few key scenario counter values (the first ones are named in the game's source code and I'm not always sure of the meaning, the last ones are values I searched myself in different field scripts):
Code: [Select]

SC_COUNTER_ARMOR_BLANK_START = 1500SC_COUNTER_ARMOR_BLANK_END = 1600SC_COUNTER_WMTITLE_BUNMEI_ON = 2400SC_COUNTER_SGATE_DESTROYED = 2990SC_COUNTER_CLAY_DESTROYED = 4990SC_COUNTER_LIND_DESTROYED = 5598SC_COUNTER_FOG_END = 5990SC_COUNTER_KUROMA_APPEAR = 6200SC_COUNTER_DAGGER_AWAKE = 6875SC_COUNTER_SGATE_RECOVER = 6990SC_COUNTER_ALEX_DESTROYED = 8800SC_COUNTER_SUNA_MAKYU_ON = 9450SC_COUNTER_WMTITLE_NEW_ON = 9600SC_COUNTER_SUNA_MAKYU_OFF = 9890SC_COUNTER_CUT_HAIR = 10300SC_COUNTER_GET_HILDA3 = 10400SC_COUNTER_HOKORA_START = 10600SC_COUNTER_HOKORA_END = 10700SC_COUNTER_LAST_WORLD = 11090Hilda Garde obtained = 10400Ipsen Castle entered = 10500Ipsen Castle done = 10600Eiko+Dagger gone to Shrine = 10620Amarant+Freya gone to Shrine = 10640Steiner+Vivi gone to Shrine = 10660Shrines done = 10700Disc 4 = 11100

 

[Clem Fandango]

Well how about that! This is great, I look forward to playing around with this. Thanks for the quick reply!

 

[Tirlititi]

Update to v0.41c:
- Added script file batch importing: you can now write script functions with your favorite text editor and import it back when you're done,
- Fixed bugs with text and UI text batch importation; also, the text IDs now start from 0 instead of 1 in the exported batches (so they match with the text ID inside scripts),
- Added more unused/dummied datas (for enemies mainly) that can be recycled when modifying the game's source code; also added enemy attack targetting informations (they are mostly unused, except for deciding if Cover triggers if I'm not mistaken),
- Listed more script functions and general variables in the script editor,
- Fixed a bug with Qu's Marsh's dialogs (it was actually caused by a "mobile" version of the dialogs; I think it's unused),
- In the Randomizer, the Prison Cages' "Absorb" spell is not randomized anymore,
- Fixed another bug with spell animation sequencing.

I am retiring from FF9 modding (presumably definitively). I don't think that I'll update this tool any further. The code is on Github though and I'll still answer questions, so here you go.

 

[gledson999]

Update to v0.41c:
- Added script file batch importing: you can now write script functions with your favorite text editor and import it back when you're done,
- Fixed bugs with text and UI text batch importation; also, the text IDs now start from 0 instead of 1 in the exported batches (so they match with the text ID inside scripts),
- Added more unused/dummied datas (for enemies mainly) that can be recycled when modifying the game's source code; also added enemy attack targetting informations (they are mostly unused, except for deciding if Cover triggers if I'm not mistaken),
- Listed more script functions and general variables in the script editor,
- Fixed a bug with Qu's Marsh's dialogs (it was actually caused by a "mobile" version of the dialogs; I think it's unused),
- In the Randomizer, the Prison Cages' "Absorb" spell is not randomized anymore,
- Fixed another bug with spell animation sequencing.

I am retiring from FF9 modding (presumably definitively). I don't think that I'll update this tool any further. The code is on Github though and I'll still answer questions, so here you go.

All I can tell you with this is, thanks for what you did for Final Fantasy IX!!!

About the menu's UI size, you can try to edit the C# source code of the menu and use something like that:
Code: [Select]

Could you see this issue of Menu's UI size? I don't know anything about programming. But you told this months ago

Code: [Select]

this.SubMenuPanel.transform.localScale = new Vector3(1.2f, 1.0f, 1.0f);

This would go in the method "MainMenuUI::Awake" (at the beginning, that's fine). I am not sure if it will work though, as UI modding is not something I know a lot about (and some informations are stored in GameObject and Transform files in the archives level1 and level2). Try to play with the figures here if you see that it has an effect.

 

[Tirlititi]

So? Have you tried doing that?
But it can't be done for the PSX version. It's a modification of the game's engine, so it's for PC.

 

[Clem Fandango]

I've got a few questions, one regarding the frog catching minigame, the second for setting a kind of AI behavior in an enemy and the last pertains to Chocograph pieces.

First, is there any way to change the amount of frogs required to be captured to make Quale appear? Specifically I'd like to drop down the last total that results in the Quale boss fight, mostly because I don't use the frog count for any damage calculations in any skills (wound up dumping Frog Drop pretty early) and I feel like the road to 99 frogs is way more of a grind than it ought to be. My hope is to drop down to a much nicer number, like 69 frogs. Seems a bit more reasonable.

Second, and I imagine there might be an example already existing in the game that I'm overlooking, but is there a way to force the AI to only use certain attacks when targets have a specific status? So for example, would it be possible for an enemy to only use Full Life on a party member when that party member is under the effects of Zombie? I was considering looking at the AI scripts from enemies in the game that do this, but like I said, I can't seem to think of any examples of it actually happening.

The last thing I wanted to ask about is similar to what I was asking about a while back with regards to changing the availability of Chocographs. I used your method and it's worked perfectly, so no problems there. Is there a way to limit the number of Chocograph Pieces (the six that turn into the Sky upgrade) that you can acquire until specific times? It's not really a huge deal if not, but it'd be cool if it's possible. I've currently got it set so that the Ocean change is only available after Gulug and am hoping to make Sky only available after Ipsen's Castle. Frankly it's not a particularly huge difference though so not a big deal. EDIT: Nevermind all of this actually, like minutes after I wrote it I checked your linked chocograph script with changed variables and was able to sort it out. Pretty obvious in retrospect, not sure how I missed it.

That aside, I'll be sure to update to the latest version of the tool, thanks for continuing to answer questions!

 

[gledson999]

So? Have you tried doing that?
But it can't be done for the PSX version. It's a modification of the game's engine, so it's for PC.

I understood, so the PSX version is impossible  :-( anyway thanks for reply and thanks for you impressive tool