So, the difference of the encounter rate between the PSX version and Steam version seems to rely on this:
"_encountTimer" should be initialized to 0f to match with the PSX version. There, the 1st encounter check of the field is delayed. Instead of increasing that timer from 0f to 960f (which takes about 0.5 second running), the 1st check waits for an increase of 2400f (which takes about 1.25 second running), effectively giving ~0.75 seconds to the player without random encounter check increase for free, which is good enough when you go straight to the exit.

Does that sounds right to you?
Because both the 960f limit and the "encratio" set by the field scripts seems to match with the PSX version as described by SoftReset[gamefaqs.gamespot.com].

That's the factor used for the speed up booster. It's 5 by default (even without Memoria).
Indeed, that's not relevent if the boosters are all disabled: you need to set "Enabled=1" in the "[cheats]" section for it to work.

Originally posted by Albeoris:

There is good news - during working on OpenVIII, I wrote a cool formatter for JSM scripts that describe all the events at the locations and some scripted fights. It is easy (but long -_-) can be rewritten for IX and, finally, get a handy tool for creating NPCs and your own quests.
http://forums.qhimm.com/index.php?topic=18923.0

I did that already, a long time ago.
https://imgur.com/a/cFYryS3

Using "GetDialogChoice" allows to retrieve the (last shown) dialog's picked choice.
Typically:
Note that an "else if" sequence like this is equivalent to a "switch" block:

Hello Liossenel,

Those can be done through Field script editing. In HW, go to the panel "Environment -> Fields", find the field you want to change and "Edit Script". I guess you got it that far already.

In order to change a cutscene, you need to write lines of script code. Inside a script function, the lines are executed sequencially (except when you have control flow lines, like loops "while ..." or "RunScriptSync", etc...). So you'd want to spot the lines of code telling the game to make Zidane speak, for instance.
In the first field, "Prima Vista/Cargo Room", Zidane's two first lines are in the function "Zidane_Loop". In practice, the code for cutscenes are very often either in a function of the characters or in the function "Main_Loop". There it is at the beginning of "Zidane_Loop" so you shouldn't search for it for too long.

Take a look at these lines:
You can see the two dialog bubbles, it's the lines "WindowSync" (click on the line inside HW to have more informations about it). "Sync" means that the code will wait until the dialog is closed before resuming, so the "Walk( 25, -664 )" line won't run until the player close the bubble (in contrast with "WindowAsync"). These lines are typically what you can find for doing a cutscene with only one character: the character speaks, runs some animations and walks around.

Simply adding a "WindowSync" line somewhere there with the correct parameters will make Zidane speak an additional line of dialog.

If you want an example of a cutscene with several intertwining character actions, go to the cases "+4", "+6", ..., "+11" of the same "Zidane_Loop" function. For instance, in the "case +6", you have these lines:
The variable "VAR_GlobUInt8_26" is used there as a counter for waiting all the characters to finish their job. It is setup to 4 first, then Zidane does his stuff, and is decremented by 1 in the line "set VAR_GlobUInt8_26--".
If you go to "Blank_Loop" or "Cinna_Loop" or "MarcusA_Loop", you will also see that they decrement this variable with lines "set VAR_GlobUInt8_26--" when they are done with speaking/moving/whatever.

Note that the function "Code3_Loop" basically controls the cutscene's flow here: it updates the cutscene's counter "VAR_GlobUInt8_24" (that you'll find in the other functions I mentionned) when required to the next value.

In general, "Loop" functions are executed every frame, waiting for something, because there are the two lines "Wait(1)" and "loop" at the end.

Click on the "Function List" button to have access to all the possible codes usable in the scripts. For instance,
- for starting a fight, it's "Battle" or "BattleEx",
- for changing the field, it's "Field" (or "WorldMap" when leaving the the world map); it is often preceeded by a line "set General_FieldEntrance = VALUE" to say where the character comes from in the script of the destination field,
- for playing a music, it's "RunSoundCode( 0, MusicID )",
- for changing a character's 3D model, it's "SetModel" and you need to setup the character's default animations (when standing, walking, turning...) with codes like "SetStandAnimation". I'm not exactly sure if swapping the 3D model of a character like that is bug-free but I think I remember some script doing that (maybe while the model is hidden though).

You should scroll the "HELP AND TIPS" section in the Qhimm forum's topic as there are other examples of how to use scripts (as you will see, it's the same system for the AI of the enemies so it has really broad purposes).

It is possible using dnSpy (or modding the engine source with Memoria).
The easiest way would be to add a case to the method "UIKeyTrigger::Update".

To check if a controller button is currently pressed, use "UnityXInput.Input.GetButton(KEYCODE)".
To check if a controller button is pressed (exactly for 1 frame), use "UnityXInput.Input.GetButtonDown(KEYCODE)".
To check if a controller button is released (exactly for 1 frame), use "UnityXInput.Input.GetButtonUp(KEYCODE)".

Among the key codes, you have "JoystickButton4", "JoystickButton5", "LeftTrigger", "RightTrigger" and "JoystickButton7" for L1, R1, L2, R2 and Select respectively.

So in the end, it would look like this:

No, that's not it, sorry for not being clear.

Step 4: do NOT move the created Assembly-CSharp.dll out of the game's folder.
Step 5/6: you're not forced to do another installation with Memoria, just use the one you currently have.

Also, between step 1 and 2, copy/paste the "resources.assets" of your current installation with Memoria into the clean install (if you don't have any installation with Memoria or didn't mod anything with it yet, you can skip it of course).
That's because the "resources.assets" contains, among other things, the names of both the party's abilities (modified by Memoria, I guess) and the enemies' abilities (modified by HW) so you need to keep the modified file along during all the modding steps.

Your last line is correct: that's the possibility I was describing.

The incompatibility between Hades Workshop and Memoria are about the Assembly-CSharp.dll only. You can modify the stats and abilities of the enemies with HW and then use Memoria because these stats are not in the DLL:

1) Prepare a copy of the game: it should be the vanilla game, without any mod and without Memoria (so HW can open it) but take the "resources.assets" from your Memoria-modded game and replace it in the copy.
2) On that Memoria-less copy of the game, do the modifications you want in the "Enemies" panel of HW (there are only two restrictions: you should not click on "Edit Status Set" of the status-dealing abilities or change the battle scenes, these changes are in the DLL),
3) Save Steam Mod: it will create a Assembly-CSharp.dll, a p0data2.bin, a resources.assets and possibly a p0data7.bin (if you modified the AI script),
4) Replace the files "p0data2.bin", "p0data7.bin" and "resources.assets" of the game modded with Memoria ; you can still mod with Memoria afterwards or update those p0data files whenever you want.

Nice job, thank you :)

Did you get one of these two tools?
Hades Workshop: http://forums.qhimm.com/index.php?topic=14315.0
Memoria: https://steamhost.cn/steamcommunity_com/groups/ff-modding/discussions/13/357284131804133221/

You can't do anything without one of them.