Unlimited Armory
Unlimited Fuel
Unlimited Throwables
Full Ammo Clip
Full Durability
No Health Penalty
No Stamina Penalty
Stop Infection
Unlimited Stamina When Running
Unlimited Stamina When Attacking
Show Hidden Objects/Traps
Can Always Interact
Always Within Interact Range
Craft For Free
Inventory Mouseover
Weapon Mouseover
- Quantity
- Durability
- Clip Count
Experience Multipler new
Game State Pointers
- Knowledge
- Supplies
How to use this cheat table?
Install Cheat Engine
Double-click the .CT file in order to open it.
Click the PC icon in Cheat Engine in order to select the game process.
Keep the list.
Activate the trainer options by checking boxes or setting values from 0 to 1
I added a few of your options to my existing table, if you don't mind. Let me know and I'll remove them if you'd like. Credits given in table and thread.
Learned new stuff like reassemble command from this table. Anyway running into crashes with your table.
The root causes is something I've started seeing a lot on my machine. Basically jmp becomes a 14 byte 64-bit jmp instruction instead of a 5 byte 32-bit jmp instruction and mangles the assembly.
I assume this is known issue in general but not sure if there is reliable workaround. The last time I encountered this I ended up having to assume the 14 byte version and include a lot of nops and related protection to deal with either case.
Not expecting solution as I will figure it out myself. But would love to see a simple reliable workaround that is fairly generic. Example for Inventory Mouseover
This is "Inventory Mouseover". GameAssembly.dll is at 1429D1A0000, inventoryPtr is at 14352DE0000
Here is my alternative version using a different point later in function with 16 bytes open. reassemble would be nice if you give it a size and have it reassemble what it can from the size and then pad with nops or something. Instead of picking individual instructions but then again readmem is sufficient here.
Yea, I don't believe CE has something automatic to assist with this. If these long jumps seem to be occurring a lot, you may just need to write your scripts to always assume it will need to reserve 15 bytes. It happens when CE can't find an empty block of code near your target injection. It's possible that reducing the alloc() size will help it find a better code cave. Instead of $1000, pick a much smaller number that reflects your actual needed space. Although, it probably always reserves a chunk of bytes and doesn't necessarily honor your requested size.
But, for something like this scenario, if you always assume it will require 15 bytes, you could do something like below. Note you don't have to NOP as long as you tell the code where to JMP properly. The disassembler view may look bad, but the code itself doesn't care when running.
Thanks. This was my assumption. Even a smaller block does not always work. I edited post with my approach here. Mentally easier in this case. Would be nice if reassemble could do more than one instruction and do a range but its all doable manually.
Unlimited Armory
Unlimited Fuel
Unlimited Throwables
Full Ammo Clip
Full Durability
No Health Penalty
No Stamina Penalty
Stop Infection
Unlimited Stamina When Running
Unlimited Stamina When Attacking
Show Hidden Objects/Traps
Can Always Interact
Always Within Interact Range
Craft For Free
Inventory Mouseover
Weapon Mouseover
- Quantity
- Durability
- Clip Count
Experience Multipler new
Game State Pointers
- Knowledge
- Supplies
Do you mind updating this for the Epic Games Free Game of the Week?