My set of tools. The code is more important than the features, so feel free to reuse it. π
Supported games
Name | Decompiler | Compiler |
---|---|---|
Call of Duty: Black Ops 4 (T8) | β | β |
Call of Duty: Black Ops Cold War (T9) | With predecode | β |
Call of Duty: Modern Warfare III (JUP) | With extension | β |
Prototype libary for random stuff, probably not linked to Call of Duty.
This tool is using and providing
- ANTLR-4 - BSD-3-Clause license.
- Detours - MIT license.
- Madler/zlib - Custom license.
- asmjit - ZLib license.
- ladislav-zezula/CascLib - MIT license.
- lz4/lz4 - Custom license.
- vimpunk/mio - MIT license.
- JustasMasiulis/xorstr - Apache License 2.0
- ocornut/imgui - MIT license
- biocomp/hw_break - MIT license
- Tencent/rapidjson - MIT and JSON license
You can download the latest release here:
- Latest Release
- Latest Dev Build (Might be unstable)
- ate47/t8-atian-menu : All the notes and dump generated by this tool. (All games)
- ate47/bo4-source : Black Ops 4 Dump
- ate47/bocw-source : Black Ops Cold War Dump
- ate47/BOHashTool : Tool to test hashes with error (en/de)coder for Black Ops games
Mods implemented in my tool, run acts mod
for the list.
acts mod t8cee
- enable EEs in Custom mutations, offline or casual (Black Ops 4).acts mod t9cee
- enable EEs in offline (Black Ops Cold War).
Tools to decompile or disassemble the GSC scripts, a bo4 script decompilation is available in the bo4-source and bocw-source repositories.
- gsc disassembler, made in 3 days with a lot of alcohol so don't use it.
acts gscinfo -a -o "output" [input=scriptparsetree]
- gsc decompiler, same as the disassembler, but 10 days after, not any better.
acts gscinfo -g -o "output" [input=scriptparsetree]
GSC compiler, not for all the game, scripts can be compiled using the command acts gscc -g [game] [directory]
.
Tools to help with the GSC development.
- gsc vm debugger, dump the function stack when the vm has a crash,
acts dbg
- can dump the var stack
-s
local var-v
- can look inside structures with the depth for array
-A [depth]
and structs-S [depth]
(need the game started)
- can dump the var stack
To have a lookup over the extracted hashes, you can use a file named strings.txt
when using the process, it will be loaded automatically, one string per line.
You can also use .wni compiled files, create a directory with the name package_index
and put the .wni files in it.
- Serious's t8-compiler for some opcodes for Black Ops 4, it fasted up the process of understanding the internal game functions. Also for the childthread operator syntax.