Re: Atelier Lulua - The Scion Of Arland
Posted: Wed Jun 05, 2019 4:25 pm
For those interested how I debugged the item-editor/tips (Yes it is long, and you might probably know all that):
for the rest:
hopefully on (if there is) a next update, the scripts might still work.
--infinite snyth materials: still worked for me (copy pasted them)
--infinite item usage: changed 1 aob (that was breaking the script)
--item Editor: wasted all my time, hope it works now
rest was already included.
PS: Days value cant be 1byte (max=255 decimal). the offset with mins and secs are +4 (and the values are 00).you can safely have them 2bytes(max=65535=FF (that's why it was the last-slot on traits)
the mins and secs have enough space to write 4bytes too, but you don't have values over 60 anyways
(bonus trick: browse-memory: rightly-click (on some byte)-->Display type-->xx byte decimal.. Suddenly gibberish becomes readable)
And Zachillios you don't have to give me creds on the table (mentioning me here is enough).
Whoever filled in the spreadsheet the values deserves more anyway (something i admit i would have never done, (only if there was some lazy way))
Spoiler
Thing is, if you inject on (or near) calls and jumps, sometimes not only you might crash the game but on updates it is (almost) guaranteed to change the addresses. (then the OP code changes and the AoB wont work).
If even one aob doesn't return a result the script doesn't execute further. (You can search which one it was if you search for (valuetype: AOB) and tick writable box to gray(=either read or write). If you done it correctly it should always return exactly 1 (unique) result, if it doesn't its faulty
This search is helpful when some bytes changed but some others didn't. This is where the previous code snippet comes handy. You combine prev OP codes (which i forgot to include)
and form an array of bytes that hopefully didn't change (like top/bot of your injection point). You can even use wildcards (like: * ?? xx), if you know there is a byte there (don't know what it is) but you know the next.
another one is, u can try to inject on the previous instruction (so you can avoid injecting on the calls or jmps and avoid this mess
and another trick is when you find one instruction (eg: by what accesses/writes this address) and right-click it (on disassembler), you can select what other addresses this instruction access. (you will see that on the original highlight editor, it pops many other addresses (and that's why you don't want to write/freeze).
This is a common problem eg if you find what decreases health/mana but want to see if it also is the one that decreases health/mana on enemies.
If you done the (old)cheat-engine tutorial it was similar to the final problem
On the original highlight editor (searched what instructions accessed some random item (the itemID), then went to synth and hovered again on the same item. Some others instructions will pop up.
In this case only 1updated only once when i hovered exactly over 'that' item (it happened to be the last). Thats how i ended up with aob_itemSynth
then i merged the code in 1 script. I ll spare you the details on that I hope it might help you in the future
If even one aob doesn't return a result the script doesn't execute further. (You can search which one it was if you search for (valuetype: AOB) and tick writable box to gray(=either read or write). If you done it correctly it should always return exactly 1 (unique) result, if it doesn't its faulty
This search is helpful when some bytes changed but some others didn't. This is where the previous code snippet comes handy. You combine prev OP codes (which i forgot to include)
and form an array of bytes that hopefully didn't change (like top/bot of your injection point). You can even use wildcards (like: * ?? xx), if you know there is a byte there (don't know what it is) but you know the next.
another one is, u can try to inject on the previous instruction (so you can avoid injecting on the calls or jmps and avoid this mess
and another trick is when you find one instruction (eg: by what accesses/writes this address) and right-click it (on disassembler), you can select what other addresses this instruction access. (you will see that on the original highlight editor, it pops many other addresses (and that's why you don't want to write/freeze).
This is a common problem eg if you find what decreases health/mana but want to see if it also is the one that decreases health/mana on enemies.
If you done the (old)cheat-engine tutorial it was similar to the final problem
On the original highlight editor (searched what instructions accessed some random item (the itemID), then went to synth and hovered again on the same item. Some others instructions will pop up.
In this case only 1updated only once when i hovered exactly over 'that' item (it happened to be the last). Thats how i ended up with aob_itemSynth
then i merged the code in 1 script. I ll spare you the details on that
I hope it might help you in the future
hopefully on (if there is) a next update, the scripts might still work.
--infinite snyth materials: still worked for me (copy pasted them)
--infinite item usage: changed 1 aob (that was breaking the script)
--item Editor: wasted all my time, hope it works now
rest was already included.
PS: Days value cant be 1byte (max=255 decimal). the offset with mins and secs are +4 (and the values are 00).you can safely have them 2bytes(max=65535=FF (that's why it was the last-slot on traits
)the mins and secs have enough space to write 4bytes too, but you don't have values over 60 anyways
(bonus trick: browse-memory: rightly-click (on some byte)-->Display type-->xx byte decimal.. Suddenly gibberish becomes readable)
And Zachillios you don't have to give me creds on the table (mentioning me here is enough).
Whoever filled in the spreadsheet the values deserves more anyway (something i admit i would have never done, (only if there was some lazy way))