T
Tirlititi
Guest
Thanks Satoh, but the unknown integers are displayed properly ; the values are too round to be 2 splitted numbers and the Steam code source name them "offsets" (as signed shorts).
There are usually sufficient free space to add a bit of code (in general, a good big entry would fit in). The problem is that the exact free space is quiet random and can indeed cause trouble if you need to add some constant code to all the scripts ; there are surely several for which you'll be unlucky and there won't be enough space... For now, and for long, the only solution will be to be inventive and grab some space elsewhere in the script (either by shortening the code, either by cutting unneeded lines).
The length by itself will never "corrupt" the script. You'll get bugs if the script that you added is in conflict with the normal script (or if you do things like dividing by 0 :evil: ), but that's all.
It would be really useful to have a list of unused variables, indeed. I know there are a few gaps in the "chest-opened" flags, but I don't know if there are large ranges of unused (and memory card-saved) variables. I don't have time to investigate it for the moment though :/
I updated my Hidden Dialogs video with the Steam version ; t'was a good practice to see what problems arise with the Steam version when trying to import the modification patterns from the PSX version.
I have a clearer idea of how Hades Workshop could be made compatible with the Steam version now. Don't expect it to come out before 2 weeks (that's my target time, but I know from experience I always pass it because of technical problems I didn't expect ^^"). You won't be able to use the most basic features of HW with the Steam version at the beginning. Oddly enough, the modification of party's spells and items will be more difficult than the enemies spells and AI, or Field scripts.
EDIT : I've had even more technical difficulties than I thought, and I'm just at the stage of reading datas (after that, I'll need to create modded files). And overall, I'm fed up of this steam version...
I'll definitely make a compatibility update next, but it'll take more time than expected.
There are usually sufficient free space to add a bit of code (in general, a good big entry would fit in). The problem is that the exact free space is quiet random and can indeed cause trouble if you need to add some constant code to all the scripts ; there are surely several for which you'll be unlucky and there won't be enough space... For now, and for long, the only solution will be to be inventive and grab some space elsewhere in the script (either by shortening the code, either by cutting unneeded lines).
The length by itself will never "corrupt" the script. You'll get bugs if the script that you added is in conflict with the normal script (or if you do things like dividing by 0 :evil: ), but that's all.
It would be really useful to have a list of unused variables, indeed. I know there are a few gaps in the "chest-opened" flags, but I don't know if there are large ranges of unused (and memory card-saved) variables. I don't have time to investigate it for the moment though :/
I updated my Hidden Dialogs video with the Steam version ; t'was a good practice to see what problems arise with the Steam version when trying to import the modification patterns from the PSX version.
I have a clearer idea of how Hades Workshop could be made compatible with the Steam version now. Don't expect it to come out before 2 weeks (that's my target time, but I know from experience I always pass it because of technical problems I didn't expect ^^"). You won't be able to use the most basic features of HW with the Steam version at the beginning. Oddly enough, the modification of party's spells and items will be more difficult than the enemies spells and AI, or Field scripts.
EDIT : I've had even more technical difficulties than I thought, and I'm just at the stage of reading datas (after that, I'll need to create modded files). And overall, I'm fed up of this steam version...
I'll definitely make a compatibility update next, but it'll take more time than expected.
Last edited: