- read this
specifically this:
- as Squalor mentioned above, all tables are made strictly for Single Player use only.2. Please keep in mind that if a game contains both a single and multi-player component and the table features scripts/options for the second component (the multi-player one, just to be clear), both the table and adjacent discussions will not be allowed/deleted. No online everything, people (including hijacking/enabling DLC options or any other micro-transactions processing).
////***********************************************************************************************///
@Tiffany
first off, here are some info about cheat engine using:
- table changes:
there's "Save" and "Save as" option in the "File" tab, just like the notepad.
after you made the changes (merge, added address, or edited script, etc.), you can choose to save the changes if you wish.
- ticking the box in front of an entry means:
if the entry contains child scripts/pointers/addresses.., you expend it.
if the entry is a pointer/address, you freeze the value (CE would attempt to force the value to stay the same as when you freeze it).
if the entry is a script, you enable it.
if it's a pointer/address, DO NOT tick the box unless you need to freeze the value.
if it's a script generated pointer, DO NOT leave the address freeze for the whole game session.
if you just want to change the value, just change the value, the changes is in real time.
- scripts:
now this happens mainly on my tables, as I usually use a main mother script to gather necessary pointers for some sub-scripts integrity check (if applicable).
so, if you de-activate the mother script (in this case, "enable" script) without de-activate its sub-scripts first (e.g., in this case, "inf. ammo clip" script need a pointer located by "enable" script to make sure it applys on the player's weapons only), some sub-scripts may attempt to read an address of a pointer that is no longer existed, as it was reside in a code cave generated by the mother script. as the code cave is "closed" by disabling the mother script, thus leads to a crash.
now to answer your questions:
1. as the pics you shared shows that you unnecessarily freeze some "modifiers" (GREEN pointers.address) of some scripts, so, did you freeze any pointers in RED when the freeze happens? if so, stop that. as most of the RED pointers are script-generated, they're obtained in "real-time", freezeing them isn't a good idea most the time.
2. the pics didn't show which 1096bimu's scripts/pointers did you use. so, did you activate any scripts/pointers from 1096bimu's table when freeze happens?
3. as mentioned above, as long as you leave the "enable" script the last one to disable, it should be fine. and I've just try disabling all the scripts and re-enabling them right now, game still running.
4. "I got into the habit of doing it after a few games I've played end up with the cheated values baked into the game if the table/trainer isn't deactivated"
it depends on what the "cheated values" you mentioned is.
e.g., if you modified the exp, then save the game. then of course it'd be saved to the game.
but if you enabled undead and quit the game without disabling the script, the functionality won't be "baked" to the game. in fact, none of my scripts would be baked into the game whatsoever.
5. the moon jump (and its sub-script) is hidden for a reason, they are ugly, and not even "fully" tested, it's just for you to play around, or you want to make a inf. double jump, that could be a good place to start tracing the codes, instead of starting it from fresh.
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