FearLess Cheat Engine

Call Of Duty Infinite Warfare (v6.5.1233116)
(also supports [IW7-Mod a37ae3a] w/ v6.23.1435251)


- Health (incl demi/godmode & invisibility)
- Ammo
- Shield, Double-Jump & Air
- Jackal Handling (health, gatling/cannon heating, missiles)
- Miscellaneous:
> console: fov, speed, unlimited sprint, free roam
> informational: coordinates, list dvars, IW7-Mod Command List, map info

Note: based on my other COD x64 tables/experience.


Readme is included/updated !

Before reporting any issues, reproduce the situation so that I have something to go on...

* Other table(s):
> #Rhark: [ viewtopic.php?t=17575 ]
> #Kito: [ viewtopic.php?t=21114 ]

* For tablemakers: most COD games seem to "behave" like this in that values are (always) static.
- You'll find most/all values much faster by selecting the game_exe in the [Memory Scan Options] drop_list...
- AOB scans are - for most games - executed with 'Writable' enabled !
- On Windows 10, 'jmp far' needed to be introduced !
- To debug 'IW7-Mod', you'll either need to use [x64dbg & ScyllaHide] or 'DBVM-level debugger' (v7.4+)
- The features in this table have mostly been "taken" from my other COD tables
(as opcodes are "pretty much" identical)

* IW7-Mod Command/Dvar List: [ [Link] ]
(the list links the 'hashId's with its corresponding descriptives !)

Your readme file is passworded

Can't seem to use this on windows 10, the Enable Cheats script fails with error "<<Lua error in the script at line 15:[string "-- You must accept to execute..."] attempt to perform arithmetic on a nil value (field 'Result')>>" every time.
And I don't quite understand what "jmp far needs to be introduced" means.

^ that means that you are using a different game version. 2 things:
a. double-click the main script, and you'll find 5-6 'getStaticAddr("xx xxx...' functions. place a double '--' (without them '') in front of the 1st one, press [Ok] and try to enable the script. Nogo: do this with 2nd one, etc
Note: as soon as it enables, try to find out which one(s) are causing the script to fail: iow remove them '--' respectively again to identify the culprit...
b. upload your game_exe and pm me download link. that said: don't hold your breath, because it is almost certain that offsets have changed (which I can not find because of the way the code collects most info)
Note: I'll be waiting for your feedback on a.) before taking any action...

ps: as stated in my readme, the table has been set up in such a way that - if knowledgeable - one can "easily" update it to any/most versions since offsets are managed via a table/array 'xOffsets'...