1
FF9 Tools / Re: [PSX/PC] General editor - Hades Workshop (0.50b)
« on: 2025-07-12 20:33:04 »
@iamthehorker: Hello. That's the link now. Dropbox indeed changed its URL format several years ago.
The Collector
The Collector
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
FF9 Gameplay Releases / Re: [PSX/PC] Alternate Fantasy (v3.2 & v6.8)
« on: 2025-06-03 12:33:21 »
It might be related to the SFXRework mode.
Alternate Fantasy is not fully compatible with the option "SFXRework = 0" since a long time, but these incompatibilities only get more and more important with each version. You need to have "SFXRework = 1" in your Memoria.ini for that kind of things.
Alternate Fantasy is not fully compatible with the option "SFXRework = 0" since a long time, but these incompatibilities only get more and more important with each version. You need to have "SFXRework = 1" in your Memoria.ini for that kind of things.
3
FF9 Gameplay Releases / Re: [PSX/PC] Alternate Fantasy (v3.2 & v6.0)
« on: 2025-05-20 09:19:38 »
Hello.
Yes, there has been problems with Alternate Fantasy for the past few days, since the latest release of Memoria. That version of Memoria (v2025.05.12) broke compatibility with a few mods, including Alternate Fantasy, and we had to update them.
So now, Alternate Fantasy should be compatible again, but you need to have everything updated: Memoria v2025.05.12 and Alternate Fantasy v6.8.
Alternatively, you should have no problem if you kept Alternate Fantasy v6.6 and Memoria v2024.12.04, but rather update everything.
Yes, there has been problems with Alternate Fantasy for the past few days, since the latest release of Memoria. That version of Memoria (v2025.05.12) broke compatibility with a few mods, including Alternate Fantasy, and we had to update them.
So now, Alternate Fantasy should be compatible again, but you need to have everything updated: Memoria v2025.05.12 and Alternate Fantasy v6.8.
Alternatively, you should have no problem if you kept Alternate Fantasy v6.6 and Memoria v2024.12.04, but rather update everything.
4
FF9 Gameplay Releases / Re: [PSX] Comprehensive ATB Enhancement
« on: 2025-04-16 13:16:48 »
From my experience, there is no module compression by default in FF9, but it may be that some ISO are shared with a patch that add such compression (decades ago, there was a "Paradox patch" of the french ISO that used RNC to compress a part of the menu modules).
5
FF9 Gameplay Releases / Re: Moguri mod messed up and won't let me access Memoria Launcher.
« on: 2025-04-02 14:34:14 »
Duplicate the file "FF9_Launcher.bak" in your game's folder and rename the duplicate as "FF9_Launcher.fix".
If you don't find "FF9_Launcher.bak", then duplicate "FF9_Launcher.exe" instead (and still rename it "FF9_Launcher.fix").
That is most likely because you uninstalled the game without disabling the "Fix Steam Overlay" option.
If you don't find "FF9_Launcher.bak", then duplicate "FF9_Launcher.exe" instead (and still rename it "FF9_Launcher.fix").
That is most likely because you uninstalled the game without disabling the "Fix Steam Overlay" option.
6
FF9 Tools / Re: [PSX/PC] General editor - Hades Workshop (0.50b)
« on: 2025-03-13 11:13:20 »
Hi.
I'm afraid so, yes. As said, you really need to save on a different file everytime.
It might be that your .hws are not corrupted and the datas can be technically retrieved, but for that I need to dig into what's the problem and I'm not on it yet.
I'm afraid so, yes. As said, you really need to save on a different file everytime.
It might be that your .hws are not corrupted and the datas can be technically retrieved, but for that I need to dig into what's the problem and I'm not on it yet.
7
FF9 Tools / Re: [PSX/PC] General editor - Hades Workshop (0.50b)
« on: 2025-03-02 20:37:34 »
Hello.
That looks very complicated. I don't know how you should proceed.
I know why it bugs though: the coordinates in functions "Zidane_Init" are the XZY coordinates on the field. They are of type "Int16" so 65477 must indeed be interpreted as -59, there's no problem there. The problem is that the coordinates used by "MoveCamera" are XY coordinates on the screen. The conversion from field coordinates to screen coordinates is all but straightforward. Maybe you can search for other ways to manipulate the camera there (can you add an offset to the camera that follows the player character? I don't remember).
That looks very complicated. I don't know how you should proceed.
I know why it bugs though: the coordinates in functions "Zidane_Init" are the XZY coordinates on the field. They are of type "Int16" so 65477 must indeed be interpreted as -59, there's no problem there. The problem is that the coordinates used by "MoveCamera" are XY coordinates on the screen. The conversion from field coordinates to screen coordinates is all but straightforward. Maybe you can search for other ways to manipulate the camera there (can you add an offset to the camera that follows the player character? I don't remember).
8
FF9 Tools / Re: [PSX/PC] General editor - Hades Workshop (0.50b)
« on: 2025-02-11 09:34:25 »
Hello Yerek.
That would be very great. I should be working again on Hades Workshop in a foreseeable future (maybe a month or so), so it can be part of the version after that.
You can contact me on discord (Tirlititi) if that's OK with you. Another possibility is to create a "Pull Request" on github directly.
That would be very great. I should be working again on Hades Workshop in a foreseeable future (maybe a month or so), so it can be part of the version after that.
You can contact me on discord (Tirlititi) if that's OK with you. Another possibility is to create a "Pull Request" on github directly.
9
FF9 Tools / Re: [PSX/PC] General editor - Hades Workshop (0.50b)
« on: 2025-02-02 14:31:54 »
Hi charlie_38.
The entry names are not very trustful in that regard. Entries are named "Region" as soon as they are initialized (most likely in the function "Main_Init") with "InitRegion", while object entries are named according to the "SetModel" line found in their own functions. You need to compile, close and re-open the script editor to have updated entry names.
I guess your problem is only the "InitRegion", as the rest seems correct. An example of region in the vanilla script using the same method as yours is:
The entry names are not very trustful in that regard. Entries are named "Region" as soon as they are initialized (most likely in the function "Main_Init") with "InitRegion", while object entries are named according to the "SetModel" line found in their own functions. You need to compile, close and re-open the script editor to have updated entry names.
I guess your problem is only the "InitRegion", as the rest seems correct. An example of region in the vanilla script using the same method as yours is:
Code: [Select]
Function Region8_Init
SetRegion( ( -44, 1481 ), ( -159, 1237 ), ( 31, 1169 ), ( 88, 1329 ) )
return
Function Region8_Range
ifnot ( IsMovementEnabled ) {
return
}
Bubble( 1 )
return
Function Region8_SpeakBTN
ifnot ( IsMovementEnabled ) {
return
}
// Whatever happens when interacting while inside the region
return
10
FF9 Tools / Re: [PSX/PC] General editor - Hades Workshop (0.50b)
« on: 2025-02-01 12:35:15 »
Hello.
Glad you found the problem, charlie_38. The indexings of statuses are indeed confusing, because of a mistake we did early on that lead to shift the indexing by 1 in some places. Sorry about that.
@Kapten Teo: Thanks. Unfortunatly, there is no easy way to do that. The main problem is that there are enemies with a 10,000 extra HP that should not be taken into account but are there for scripting purposes. For example, Plant Brain's HP, internally, are 11,431 HP instead of 1,431 HP, and then its AI script manages the way it dies. If you raised its HP by 50%, it would go up to 17,146 HP and require 7,146 damage to be killed, way more than the expected 50% bonus.
And there are plenty of enemies like that, and there are also enemies with a slightly different system, which makes things more complicated.
So, except for checking the option "Edit similar enemies", I don't see a way to ease the task for you (and you'll still need to take into account these extra 10,000 HP when they are present).
The HWS are found here ("AF & PCP source files").
However, it's been a while since I didn't update these source files (althoug the Beatrix Mod's HWS is up-to-date because I didn't update the mod since a long time), partly because I need to update Hades Workshop and partly because I think people tend to import the .hws files for compatibility reasons for situations in which compatibility should be handled by the Memoria engine instead. There are situations that prevent compatibility unless "compiling a mix of both mods", but most of the time it's rather a matter of file conciseness and priority choices.
Well, for the Beatrix Mod, I should be the one improving the file conciseness. But there, you have the HWS.
Sorry, I really need to update my mods at some point. I focus on improving Memoria and they are lagging behind.
Glad you found the problem, charlie_38. The indexings of statuses are indeed confusing, because of a mistake we did early on that lead to shift the indexing by 1 in some places. Sorry about that.
@Kapten Teo: Thanks. Unfortunatly, there is no easy way to do that. The main problem is that there are enemies with a 10,000 extra HP that should not be taken into account but are there for scripting purposes. For example, Plant Brain's HP, internally, are 11,431 HP instead of 1,431 HP, and then its AI script manages the way it dies. If you raised its HP by 50%, it would go up to 17,146 HP and require 7,146 damage to be killed, way more than the expected 50% bonus.
And there are plenty of enemies like that, and there are also enemies with a slightly different system, which makes things more complicated.
So, except for checking the option "Edit similar enemies", I don't see a way to ease the task for you (and you'll still need to take into account these extra 10,000 HP when they are present).
The HWS are found here ("AF & PCP source files").
However, it's been a while since I didn't update these source files (althoug the Beatrix Mod's HWS is up-to-date because I didn't update the mod since a long time), partly because I need to update Hades Workshop and partly because I think people tend to import the .hws files for compatibility reasons for situations in which compatibility should be handled by the Memoria engine instead. There are situations that prevent compatibility unless "compiling a mix of both mods", but most of the time it's rather a matter of file conciseness and priority choices.
Well, for the Beatrix Mod, I should be the one improving the file conciseness. But there, you have the HWS.
Sorry, I really need to update my mods at some point. I focus on improving Memoria and they are lagging behind.
11
FF9 Gameplay Releases / Re: [PSX/PC] Alternate Fantasy (v3.2 & v6.0)
« on: 2025-02-01 12:25:28 »
Hello qwepoi. Sorry I didn't see your message earlier.
That's a totally normal behaviour for this final boss:
That's a totally normal behaviour for this final boss:
Spoiler: show
12
FF9 Tools / Re: [PSX/PC] General editor - Hades Workshop (0.50b)
« on: 2024-12-10 18:14:18 »
Mainly, there's Qhimm's discord, although it's not very active concerning FF9, and there's Moogle & Mods: https://discord.gg/b4D9SRG9
Compatibility is not always possible: if a mod decides to give Mage Masher a power of 30 and another mod decides it should be 40, then there's no way to have both be effective at the same time. There are a few ways to try achieving the maximum compatibility with other mods, but no way to make everything compatible with everything. The possibilities are:
1) Make sure that your mod folder contains only the files that are indeed modified. Hades Workshop should do that automatically in most cases.
2) For almost all the CSV files, it is possible to only have the modified entries in the files there. Again, Hades Worshop automatically filters these and only write the entries that were actually modded, but it currently has many flaws in that regard.
3) Same goes with text files (.mes): a MES file that only contains something like [TXID=100][STRT=0,1]And now for something completly different[ENDN] will only change 1 text (of the text block or concerning spell names or item names, etc...) without touching the others. Hades Workshop is rather clumsy for now concerning that aspect.
Still, that's the kind of things you'd not want to do manually, and if you do it's after everything else.
Compatibility is not always possible: if a mod decides to give Mage Masher a power of 30 and another mod decides it should be 40, then there's no way to have both be effective at the same time. There are a few ways to try achieving the maximum compatibility with other mods, but no way to make everything compatible with everything. The possibilities are:
1) Make sure that your mod folder contains only the files that are indeed modified. Hades Workshop should do that automatically in most cases.
2) For almost all the CSV files, it is possible to only have the modified entries in the files there. Again, Hades Worshop automatically filters these and only write the entries that were actually modded, but it currently has many flaws in that regard.
3) Same goes with text files (.mes): a MES file that only contains something like [TXID=100][STRT=0,1]And now for something completly different[ENDN] will only change 1 text (of the text block or concerning spell names or item names, etc...) without touching the others. Hades Workshop is rather clumsy for now concerning that aspect.
Still, that's the kind of things you'd not want to do manually, and if you do it's after everything else.
13
FF9 Tools / Re: [PSX/PC] General editor - Hades Workshop (0.50b)
« on: 2024-12-04 21:08:40 »
No, don't start over: it will be easier to spot that some things are missing (if there are any) rather than doing it all over again, even if you're not far away yet.
14
FF9 Tools / Re: [PSX/PC] General editor - Hades Workshop (0.50b)
« on: 2024-12-03 23:57:24 »
Hello Charlie_38,
Indeed, the HWS files sometimes bug right now. It is quite irritating because it's the first version of HW that has bugs concerning the save format in a long time and it can (and unfortunatly did) make people lose their mod or parts of it.
So I advise to always save your HWS as a new file everytime you save, instead of overwriting them.
Sometimes, a HWS that usually crashes on load can be opened without crash randomly. That's not the renaming that solved it but something random that I have yet to understand. It may be that a part of your changes were lost in the process as well.
An example of what was reported to be randomly lost is the field script modifications, but only in japanese.
I made a couple of changes in my own mod without noticeable problem myself (even though it's a big mod), but maybe i missed them or maybe the bugs really appear when adding new entries as you saw with texts... In any case, we should be careful.
I saw that the "Party -> Special" panel makes the HWS very unstable indeed. Your details about the bug in the texts may help me to find the issue.
I'll try to update the tool to fix these bugs and catch up with a couple of Memoria features, but somehow it's always delayed.
Sorry about that.
Indeed, the HWS files sometimes bug right now. It is quite irritating because it's the first version of HW that has bugs concerning the save format in a long time and it can (and unfortunatly did) make people lose their mod or parts of it.
So I advise to always save your HWS as a new file everytime you save, instead of overwriting them.
Sometimes, a HWS that usually crashes on load can be opened without crash randomly. That's not the renaming that solved it but something random that I have yet to understand. It may be that a part of your changes were lost in the process as well.
An example of what was reported to be randomly lost is the field script modifications, but only in japanese.
I made a couple of changes in my own mod without noticeable problem myself (even though it's a big mod), but maybe i missed them or maybe the bugs really appear when adding new entries as you saw with texts... In any case, we should be careful.
I saw that the "Party -> Special" panel makes the HWS very unstable indeed. Your details about the bug in the texts may help me to find the issue.
I'll try to update the tool to fix these bugs and catch up with a couple of Memoria features, but somehow it's always delayed.
Sorry about that.
15
FF9 Tools / Re: [PSX/PC] General editor - Hades Workshop (0.50b)
« on: 2024-09-01 10:10:13 »
I guess devs had some kind of "macros", ie. they only wrote a single line for changing the party formation and that line was converted into all these lines, doing the process step by step in a way that adapts to all situations. That's why it heals everyone even if they didn't join the party yet or why there are "if ( 0 )" blocks that just never happen. I never added a feature for having macros there.
The "VAR_GlobInt" are restricted to a field.
"local" variables are restricted to the entry, so "VAR_LocInt8_0" in the function "Main_Init" is a different variable than "VAR_LocInt8_0" in the function "Zidane_Init".
"global" variables are restricted to the field, so "VAR_GlobInt8_0" in the field "Prima Vista/Cargo Room" is not the same as in the field "Prima Vista/Meeting Room".
Only "general" variables are unrestricted (and they are the ones saved in save games). It would require a lot of work to identify all of the general variables already and I don't advance on that part anymore since a long time.
If you understand what a global or local variable does, you can name it inside the "local variable panel" right above the function's script. It's lines like
Please don't edit your posts to remove the question after it is solved. It helps other people that read the topic.
The "VAR_GlobInt" are restricted to a field.
"local" variables are restricted to the entry, so "VAR_LocInt8_0" in the function "Main_Init" is a different variable than "VAR_LocInt8_0" in the function "Zidane_Init".
"global" variables are restricted to the field, so "VAR_GlobInt8_0" in the field "Prima Vista/Cargo Room" is not the same as in the field "Prima Vista/Meeting Room".
Only "general" variables are unrestricted (and they are the ones saved in save games). It would require a lot of work to identify all of the general variables already and I don't advance on that part anymore since a long time.
If you understand what a global or local variable does, you can name it inside the "local variable panel" right above the function's script. It's lines like
Code: [Select]
global int8 {variable_name} VAR_GlobInt8_0Please don't edit your posts to remove the question after it is solved. It helps other people that read the topic.
16
FF9 Gameplay Releases / Re: [PSX/PC] Alternate Fantasy (v3.2 & v6.0)
« on: 2024-08-29 15:48:39 »
Hello Asmorano.
That's not a counter-attack, just their unique attack (one of them casts Catastrophe, the other casts Jinx). It is not that unusual to have them run out of MP but indeed that's the most unsatisfying way to get through this battle. Blind is meant to be that annoying, although there are tips to mitigate its effect (only use items on yourself or use them on the only character on your left/right) and the accuracy malus is negated by using things like Free Energy or Quadraslash.
Jinx is indeed a very special ability. The "dummy" effect is the only spell visual effect that is in the game's database but never used and it was used for debugging purpose, but I found it fitting for this fight. It's not exactly Trouble that they inflict to you (they don't attack physically) but it's another kind of damage spreading status, indeed.
There are a couple of fights that have gimmicks like that. The intent there is to make the fight much easier by understanding the gimmick, but also to make it possible to win without understanding the gimmick, so it's not blocking.
There's another occasion to fight Zorn & Thorn in which they have similar abilities, much later in the game. Maybe you'll get it better by then.
That's not a counter-attack, just their unique attack (one of them casts Catastrophe, the other casts Jinx). It is not that unusual to have them run out of MP but indeed that's the most unsatisfying way to get through this battle. Blind is meant to be that annoying, although there are tips to mitigate its effect (only use items on yourself or use them on the only character on your left/right) and the accuracy malus is negated by using things like Free Energy or Quadraslash.
Jinx is indeed a very special ability. The "dummy" effect is the only spell visual effect that is in the game's database but never used and it was used for debugging purpose, but I found it fitting for this fight. It's not exactly Trouble that they inflict to you (they don't attack physically) but it's another kind of damage spreading status, indeed.
There are a couple of fights that have gimmicks like that. The intent there is to make the fight much easier by understanding the gimmick, but also to make it possible to win without understanding the gimmick, so it's not blocking.
There's another occasion to fight Zorn & Thorn in which they have similar abilities, much later in the game. Maybe you'll get it better by then.
17
FF9 Tools / Re: [PSX/PC] General editor - Hades Workshop (0.50b)
« on: 2024-08-27 22:40:40 »
Hello HopefulTarnished
You can use "GetEntryUniqueID(250)". It converts the special UIDs 250-255 to their number counterpart. Let's say if Zidane is the entry 11 (then Garnet is the entry 13), you can do:
Good luck too!
You can use "GetEntryUniqueID(250)". It converts the special UIDs 250-255 to their number counterpart. Let's say if Zidane is the entry 11 (then Garnet is the entry 13), you can do:
Code: [Select]
if ( GetEntryUniqueID(250) == 11 ) {
// Zidane is the player character
}
if ( GetEntryUniqueID(250) == 13 ) {
// Garnet is the player character
}I have not tested it but I think that should be the way to go.Good luck too!
18
FF9 Gameplay Releases / Re: [PSX/PC] Alternate Fantasy (v3.2 & v6.0)
« on: 2024-08-18 15:53:49 »
Sorry, there was a couple of hours with a mismatch between the update of Memoria and the update of Alternate Fantasy; they had to be simultaneously updated this time. Now if you update both Memoria and AF with the latest versions (v2024-08-18 for Memoria and v6.6 for AF), it should work fine.
Most of the time, updates of Memoria shouldn't break compatibility with mods, even heavy gameplay mods like AF, but sometimes we cannot avoid breaking the compatibility (this time, we didn't break compatibility with Trance Seek for example, only AF).
(I answered Yosharian a while ago on Discord but the "Short Range" attacks can still be performed on the back row, that's normal: it's only that they cannot reach far-away enemies like Deathguise and that they deal less damage from the back row, just like the attack command in vanilla)
Most of the time, updates of Memoria shouldn't break compatibility with mods, even heavy gameplay mods like AF, but sometimes we cannot avoid breaking the compatibility (this time, we didn't break compatibility with Trance Seek for example, only AF).
(I answered Yosharian a while ago on Discord but the "Short Range" attacks can still be performed on the back row, that's normal: it's only that they cannot reach far-away enemies like Deathguise and that they deal less damage from the back row, just like the attack command in vanilla)
19
FF9 Tools / Re: Stiltzkin's Bag a FFIX Randomizer Tool
« on: 2024-08-14 10:51:07 »
I think Stilzkin's bag still works. I did a quick test and it seems to be still 100% functional with the latest version of Memoria.
20
FF9 Tools / Re: [PSX/PC] General editor - Hades Workshop (0.50b)
« on: 2024-08-11 08:57:23 »
Hello RoSoDude.
That's most likely MIPS code indeed. I am not sure that would be feasible by modifying the parts of the MIPS code that are accessible through Hades Workshop but there's a chance it is.
The parts that are accessible and that are indexed correspond to effects of abilities. That code (which was most likely written in C for the PSX version before it got compiled to MIPS) has been ported into C# that can be read there: btl_calc.cs
Having both MIPS and C# there might help you to see how that MIPS is written and maybe identify data banks that would be relevant to change what you want. For example, there are references to BTL_DATA's "cur.hp": the current ATB of each fighter is very close to that field because "cur" is a structure like that:
Unfortunatly, I don't know about the parts that identify whether an animation (SFX) is running or not in MIPS. I guess using a debugger there (to scan the RAM during runtime) would be the best way. You can see the list of different SFX identifiers here; that should help you when looking for that kind of info.
There are functions that handles ATB progression globally, not just each individual "at_coef", but the C# port of it is surely not as close to the original MIPS code as other parts. The following C# method determines if ATB should be advancing (and would ideally be the place you'd add the condition regarding SFX) but is part of the HUD class, which were much more re-factored than other parts of the code:
Good luck.
That's most likely MIPS code indeed. I am not sure that would be feasible by modifying the parts of the MIPS code that are accessible through Hades Workshop but there's a chance it is.
The parts that are accessible and that are indexed correspond to effects of abilities. That code (which was most likely written in C for the PSX version before it got compiled to MIPS) has been ported into C# that can be read there: btl_calc.cs
Having both MIPS and C# there might help you to see how that MIPS is written and maybe identify data banks that would be relevant to change what you want. For example, there are references to BTL_DATA's "cur.hp": the current ATB of each fighter is very close to that field because "cur" is a structure like that:
Code: [Select]
public class POINTS
{
public ushort hp;
public short mp;
public short at;
public sbyte at_coef;
public byte capa;
}with "at" being the ATB and "at_coef" being its speed (that depends both on Haste/Slow but also on the battle speed configuration).Unfortunatly, I don't know about the parts that identify whether an animation (SFX) is running or not in MIPS. I guess using a debugger there (to scan the RAM during runtime) would be the best way. You can see the list of different SFX identifiers here; that should help you when looking for that kind of info.
There are functions that handles ATB progression globally, not just each individual "at_coef", but the C# port of it is surely not as close to the original MIPS code as other parts. The following C# method determines if ATB should be advancing (and would ideally be the place you'd add the condition regarding SFX) but is part of the HUD class, which were much more re-factored than other parts of the code:
Code: [Select]
public bool FF9BMenu_IsEnableAtb()
{
if (!this.commandEnable)
return false;
if (FF9StateSystem.Settings.cfg.atb != 1uL)
return true;
if (this.hidingHud)
return this.currentPlayerId == -1 || this.currentButtonGroup == BattleHUD.CommandGroupButton || this.currentButtonGroup == string.Empty;
return this.currentPlayerId == -1 || ButtonGroupState.ActiveGroup == BattleHUD.CommandGroupButton || ButtonGroupState.ActiveGroup == string.Empty;
}Good luck.
21
FF9 Tools / Re: [PSX/PC] General editor - Hades Workshop (0.50b)
« on: 2024-06-05 22:00:13 »
You removed the following lines from the base script:
Code: [Select]
SetTextVariable( 0, 300 ) // Replace "[ITEM=0]" by "Red Stone"
SetTextVariable( 1, 301 ) // Replace "[ITEM=1]" by "Blue Stone"
SetTextVariable( 2, 302 ) // Replace "[ITEM=2]" by "Yellow Stone"
SetTextVariable( 3, 303 ) // Replace "[ITEM=3]" by "Green Stone"
22
FF9 Tools / Re: [PSX/PC] General editor - Hades Workshop (0.50b)
« on: 2024-06-05 10:57:06 »
Hello g_west,
After checking the code, there's indeed an extra subtlety in the way that side-quest is coded. The possibility to deposit the stones depends on a treasure variable instead of whether you have the stones themselves (the key items) in your inventory. Here are the scripts explained:
In order to check for the presence of the items in the player's inventory instead of the treasure pickup flag, you can use the following code instead and use "allocate 2" in the local variable panel.
After checking the code, there's indeed an extra subtlety in the way that side-quest is coded. The possibility to deposit the stones depends on a treasure variable instead of whether you have the stones themselves (the key items) in your inventory. Here are the scripts explained:
Code: [Select]
// The function to pick the Blue Stone, in Mountain Path/Trail (1551)
Function Zidane_15
// The following lines are the movement of Zidane crouching in front of the statue
TimedTurn( Angle(2679, 3842), 32 )
WaitTurn( )
SetStandAnimation( 2605 )
RunAnimation( 2606 )
WaitAnimation( )
// This replaces "[ITEM=0]" in the dialog right below by the name of the item 301 (Blue Stone)
SetTextVariable( 0, 301 )
// Display the dialog with two choices: "[ITEM=0] is set on the stone. Take it out Leave it alone"
WindowSync( 0, 0, 143 )
// The check "!GetDialogChoice" is synonymous to "GetDialogChoice == 0", eg. the player chose "Take it out"
if ( !GetDialogChoice ) {
Wait( 10 )
// Play the pickup sound
RunSoundCode3( 53248, 1340, 0, -128, 125 )
Wait( 10 )
}
// The following lines are the movement of Zidane standing up
SetStandAnimation( 200 )
RunAnimation( 2590 )
if ( !GetDialogChoice ) {
// So, this whole block executes only if the player chose "Take it out"
RunSoundCode3( 53248, 108, 0, -128, 125 )
// Give the key item "Blue Stone" to the player
AddItem( 301, 1 )
// Same as above: replaces "[ITEM=0]" by "Blue Stone" in the upcoming dialog
SetTextVariable( 0, 301 )
// Blocks with "if ( 1 )" always execute; it's a technical leftover to have a "if" block there and it could just have been "WindowSync( 7, 0, 58 )"
if ( 1 ) {
// Display the dialog "Received [ITEM=0]!"
WindowSync( 7, 0, 58 )
} else {
// That part is thus never executed and could be completly removed, it wouldn't make any difference
WindowSync( 7, 0, 59 )
}
// THERE, this is the added subtlety: this variable is a "treasure picked" memo.
// It is enabled once you picked the treasure and usually it
// (1) makes sure that you cannot pick the same treasure multiple times
// (2) counts toward the treasure rank score
// But there, it will also be used to allow the player to place the Blue Stone in the other statue
set VARL_GenBool_2865 = 1
}
WaitAnimation( )
return
Code: [Select]
// The function to place the different stones, in Mountain Path/Roots (1554)
// I'll write much less details there
Function Zidane_16
SetWalkTurnSpeed( 64 )
SetPathing( 0 )
SetWalkSpeed( 30 )
InitWalk( )
WalkXZY( 1445, 174, 1243 )
TimedTurn( 160, 32 )
WaitTurn( )
SetStandAnimation( 2605 )
RunAnimation( 2607 )
WaitAnimation( )
set VAR_LocUInt8_0 = 0
SetTextVariable( 0, 300 ) // Replace "[ITEM=0]" by "Red Stone"
SetTextVariable( 1, 301 ) // Replace "[ITEM=1]" by "Blue Stone"
SetTextVariable( 2, 302 ) // Replace "[ITEM=2]" by "Yellow Stone"
SetTextVariable( 3, 303 ) // Replace "[ITEM=3]" by "Green Stone"
// Here's the tricky part: the variable "VARL_GenUInt8_358" is tied to "VARL_GenBool_2865"
// "VARL_GenBool_2865" is actually the second bit in "VARL_GenUInt8_358"
// So "VARL_GenUInt8_358" is organised in 8 bits:
// The first 4 bytes are "have you picked up the stones"
// The last 4 bytes are "have you placed the stones"
// "VARL_GenUInt8_358 != 255" is "as long as there's a bit that is not set"
// ie. "as long as the side-quest isn't over"
// "( ( VARL_GenUInt8_358 & ( ~( VARL_GenUInt8_358 >> 4 ) ) ) & 15 )" is a complex formula that enables the different choices
// It enables a choice if the related item (1) has been picked and (2) has not been placed yet
while ( ( !VAR_LocUInt8_0 ) && ( VARL_GenUInt8_358 != 255 ) ) {
EnableDialogChoices( ( ( VARL_GenUInt8_358 & ( ~( VARL_GenUInt8_358 >> 4 ) ) ) & 15 ) | 16, 0 )
// "There’s a hole. Put [ITEM=0] in. Put [ITEM=1] in. Put [ITEM=2] in. Put [ITEM=3] in. Leave it alone"
WindowSync( 0, 0, 144 )
if ( GetDialogChoice == 4 ) {
// "Leave it alone" -> Exit the loop
set VAR_LocUInt8_0 = 1
} else {
// Update "VARL_GenUInt8_358" in order to say that the stone has been placed
set VARL_GenUInt8_358 |= ( 1 << ( GetDialogChoice + 4 ) )
SetTextVariable( 4, GetDialogChoice + 300 )
RemoveItem( GetDialogChoice + 300, 1 )
WindowSync( 0, 0, 145 ) // "Put in [ITEM=4]"
RunSoundCode3( 53248, 1339, 0, -128, 125 )
}
}
// etc...
if ( VARL_GenUInt8_358 == 255 ) {
WindowSync( 0, 128, 146 ) // "Zidane “Hmm? Something came out from the back...”"
if ( GetItemCount(229) < 99 ) { // Can carry another Moonstone
if ( VARL_GenBool_7381 == 0 ) {
RunSoundCode3( 53248, 108, 0, -128, 125 )
set VARL_GenBool_7381 = 1
SetTextVariable( 0, 229 )
AddItem( 229, 1 )
WindowSync( 7, 0, 58 ) // "Received Moonstone!"
}
} else {
WindowSync( 7, 0, 62 ) // "Cannot carry another Moonstone."
}
}
}
SetStandAnimation( 200 )
RunAnimation( 2591 )
WaitAnimation( )
TimedTurn( 32, 32 )
WaitTurn( )
InitWalk( )
WalkXZY( 1327, 170, 1228 )
MoveInstantXZY( 1327, 170, 1228 )
SetPathing( 1 )
return
In order to check for the presence of the items in the player's inventory instead of the treasure pickup flag, you can use the following code instead and use "allocate 2" in the local variable panel.
Code: [Select]
set VAR_LocUInt8_1 = GetItemCount(300)
set VAR_LocUInt8_1 |= (GetItemCount(301) << 1)
set VAR_LocUInt8_1 |= (GetItemCount(302) << 2)
set VAR_LocUInt8_1 |= (GetItemCount(303) << 3)
// Replace "VARL_GenUInt8_358 != 255" by "(VARL_GenUInt8_358 & 240) != 240"
while ( ( !VAR_LocUInt8_0 ) && ( (VARL_GenUInt8_358 & 240) != 240 ) ) {
EnableDialogChoices( ( ( VAR_LocUInt8_1 & ( ~( VARL_GenUInt8_358 >> 4 ) ) ) & 15 ) | 16, 0 )
// etc..
}
// Also for the reward that marks the end of the side-quest
if ( (VARL_GenUInt8_358 & 240) == 240 ) {
WindowSync( 0, 128, 146 ) // "Zidane “Hmm? Something came out from the back...”"
// etc...
}
23
FF9 Tools / Re: [PSX] FF9 Blender Importer (0.2)
« on: 2024-05-25 22:22:40 »
Awesome! Good luck with that!
24
FF9 Tools / Re: [PSX/PC] General editor - Hades Workshop (0.50b)
« on: 2024-03-02 15:22:13 »
Hello charlie_38,
Regarding the non-complete CSV and MES files, that's normal. You must get an up-to-date version of Memoria in order for it to work properly though. So once you've updated Memoria, it should be all good.
Regarding that note in the Help window, it only concerns the PSX Japanese version of the game. If I recall correctly, one of the World Maps used for debugging had a "corrupted" script that would make Hades Workshop crash if it tried to read it. In the Steam version of the game, that's not a problem anymore and you can indeed edit the Japanese World Maps' scripts if you change language setting in HW to Japanese and it will work fine.
Regarding the non-complete CSV and MES files, that's normal. You must get an up-to-date version of Memoria in order for it to work properly though. So once you've updated Memoria, it should be all good.
Regarding that note in the Help window, it only concerns the PSX Japanese version of the game. If I recall correctly, one of the World Maps used for debugging had a "corrupted" script that would make Hades Workshop crash if it tried to read it. In the Steam version of the game, that's not a problem anymore and you can indeed edit the Japanese World Maps' scripts if you change language setting in HW to Japanese and it will work fine.
25
FF9 Tools / Re: [PSX/PC] General editor - Hades Workshop (0.50b)
« on: 2024-02-20 08:47:26 »
You should better always save your mod as "Steam Mod" but also as HWS saves ("File -> Save Mod").
You cannot resume the modding of the game after closing Hades Workshop if you don't do that: Hades Workshop should always load the base game when you open it: you can resume a mod you previously started by using "File -> Open Mod" and selecting the HWS file you previously saved.
You cannot resume the modding of the game after closing Hades Workshop if you don't do that: Hades Workshop should always load the base game when you open it: you can resume a mod you previously started by using "File -> Open Mod" and selecting the HWS file you previously saved.