Paul44 wrote: ↑
Thu Jan 14, 2021 6:35 pm
^ I will try to reproduce, .....
thanks, man, this kind of support for a free table is most appreciated.
but as i said it is not regular, i guess there's a function that uses this injection point but the game does not call it regularly, sometimes too often sometimes not so. i think its better to counter the problem rather finding its source. manual exception handling if possible cuz testing all pointers one by one ..... gonna take time to write its AA.
im sending you my exe, maybe its a problem on my side only.
btw, about the quest items, i asked in my previous post; i found some interesting stuff in the contract structure i hope you make something out of it:
Code: Select all
160 (hex) 0004BBEA ---->> always this value for missions having items
164 (hex) 0004Cxxx ----->>> ????
168 (hex) FFxxxxxx ------>>> changing last bytes changes item. (its a pointer- object maybe?! because items cant be found by value search)
16c (hex) 00100100 ----->>> always this value for missions having items but changing the first 01 (+16e offset)changes the item
i couldn't figure out how long the ID is or how it works, copying these values does not give the same item so there is another deciding offset?!?! ( edit: copying sometimes gives the same results. gold ingot for example)
careful when changing them. not recognized ID = crash.
tested it with a non-item giving mission and it worked.