Chindopopito wrote: ↑Sat Oct 12, 2024 8:59 pm
SakakiChizuru wrote: ↑Sat Oct 12, 2024 7:57 am
I may found fix of
"Pointers"->"Game Shop/Loot Settings Pointers" in v0.9.3b
Step:
Load the OG CT.
Edit "
Game Shop/Loot Settings Pointers" Lua Script.
At end of the script:
Change:
[ENABLE]
populateSettings(memrec,6)
to
[ENABLE]
populateSettings(memrec,13)
Here's the screen cap with modification and it's effect(Idk if those are the correct Shop/Loot settings,but I guess it is.):
[Link]
Devs maybe changed Pointer sequence of each settings group. IMO it changed from 6(v0.9.2f) to 13(v0.9.3b)
You beat me to post the fix, lol. Nice to know I'm not the only one interested in keeping this amazing CT alive. I'm fairly new to making tables, so I started to fiddle with the lua code, and said to myself: "what if the only thing preventing this script from working, is a change in the memory record?".
Thank you, @SakakiChizuru for keeping this alive too.
Ahahaha..Actrually I almost wants to PM you for your fix
My friend introduced this game to me about 3 days ago and I found this CT then I found Game Shop/Loot Pointers not working.
At the very beginning, I want try to fix but there's a big problem - IDK what CE will shows while this CT can run normally because I cant get v0.9.2f version of the game.
So I decide to analyze those pointers stucture in memory view(I do modify lua to output those Pointers' base addresses).
BTW I'm an amateur programmer, working on .Net and WinForms.
I checked both "Shop/Loot" and "Expendition"'s Lua script and found their BaseAddress are sorted as an regular structure, then I found populateSettings(memrec,6) in shop/loot and populateExpenditionSettings(memrec,9) - Those 2 functions have almost the very same codes.
Then I goto memoryview, change the 2nd parameter of populateSettings, and get BaseAddress, goto the address, till I found the right ones.
So I guess, Devs store those Settings' baseaddress pointer in an regular structure, but every update will/willnot change it's order - That's why you said - "Pointers, they always break".
Finally, I guess this Pointer BaseAddress Structure will remain regular ordered but may or maynot change indexes of each one. I think we can try changing the 2nd parameter to fix CT if new versions' coming and Pointers not working again.