Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
UnBattletech — BattleTech: The Crescent Hawk's Inception reverse engeneering | Kitploit
Tools/GitHubGitHub/velteyn/unbattletech
Static AnalysisReverse EngineeringDebuggersBinary AnalysisLearning & EducationFirmware Analysis
GitHubvelteyn/unbattletech

UnBattletech

BattleTech: The Crescent Hawk's Inception reverse engeneering

View Repository
813910 days agoNot yet reviewed
Share

UnBattletech

Reverse engineering of BattleTech: The Crescent Hawk's Inception (1988, MS-DOS; published by Infocom, engine by Westwood Associates) — and an in-progress Godot 4 / C# recreation of it.

Read this section before trusting anything else in this repo. The project is two efforts with very different maturity, and the word "phase" elsewhere in the docs means code written, not behaviour proven.


1. Two deliverables, built in parallel

This project produces two artifacts at the same time, and the second one poses on the first:

(1) The documented reverse engineering. The reko/ decompilation, docs/ specifications, the Spice86 emulator with BattleTech-specific MCP tools, and the Python tooling. This is the real RE work: file formats, story text, memory map, and a large part of engine logic are documented and cross-checked against decompiler output and live emulator traces. It is a deliverable in its own right, and it is also the specification for (2).

(2) The recreation (BattleTechCHI/). A Godot 4 C# program that derives from (1): it reads original data files (.BLD, .MTP, .ANM, GAME* saves) and re-implements the engine behaviour as documented by (1). It is data-faithful, not behaviour-faithful, and has never been validated end-to-end against the original.

They run in parallel, but the dependency direction is fixed:

(2) can only be as faithful as (1) is complete and verified. Where (1) says inferred or open, (2) is a guess.

That is why the roadmap puts closing the RE gaps (Track 1) and differential validation of (2) against the emulator (Track 3) ahead of feature work. A recreation is only as good as the reverse engineering that poses it.

If you are looking for a bit-exact port, it does not exist yet. If you are looking for a tool-assisted RE environment plus a data-driven reconstruction that runs on original assets, that is what is here.


2. Honest status matrix

Legend: ✅ true / done · ⚠️ partial, approximate, or with silent gaps · ❓ unknown / unverified · ❌ absent

SystemReads original files at runtimeBehaviour matches the originalValidation
BLD decrypt + cipher text✅ BldLoader.cs✅ (text)✅ round-trip BLD↔JSON byte-identical (tools/bld)
BLD opcode interpreter (28 slots 0xE4–0xFF)✅⚠️ partial❓ never played end-to-end; operand sizes fixed (EB/EC/F6/F7 and ED: 4 bytes idx/thresh/LE-target, match→jump); all slots handled (no silent drop)
Fn1CD3 dispatch (47 cases)✅⚠️ partial❓ implemented from decomp; several cases are approximations; known-wrong: 0x23 is arena/room combat setup (1CD3:1062 → fn0FDC_0629(8)), not new-game init — the rebuild's NewGameInit would wipe a run if an arena bout fires it; ED UnitCheckLoop consumes 2 bytes instead of 4 and skips the skill check + jump
MTP map header/tiles✅ MapLoader.cs / LocalMapView.cs✅ (structure)⚠️ layout decoded, not diffed frame-by-frame
ANM animation (XOR-delta RLE)✅ runtime, PNG fallback⚠️❓; repo has no ANM spritesheets (Assets/Animations/ empty)
ICN/CMP tiles❌ (pre-converted)—TileManager loads BMP; Assets/Tilesets/ empty
Save files GAME1–6 (4096 B)✅ parser SaveManager.cs❓❌ round-trip not verified against original saves
Story state (b0057, props)✅ (reads)❓ meaning inferred❓ semantics not confirmed in play
Combat (to-hit, damage, AI, heat, ammo, fog)— (own logic)❌ approximate❌ RNG/formulas never diffed against the original
Viewport / screen layout—⚠️ approximate❓ no canonical viewport struct located
Sound / music❌❌❌ format undecoded
Map→BLD trigger mapping✅ decoded✅ ([0x5460]:0x4602 + building-position tables → MTP name list; docs/formats/map-bld-triggers.md)⚠️ entrances hand-verified only on MAP1 so far

What the rebuild can do today

  • Boot the title/startup sequence and the local-map + world-map views.
  • Load and decrypt the real .BLD scripts and interpret them (dialogue, menus, shops, many dispatch cases) — with silent gaps on unimplemented opcodes.
  • Parse the real .MTP maps, and read/write the real 4096-byte save layout.
  • Run a from-scratch tactical combat loop (own RNG/LoS/to-hit/damage/AI).

What it cannot do honestly claim

  • That it reproduces the original's behaviour. Combat, viewport rendering, and parts of the story state machine are reconstructions, not verified ports.
  • That it is self-contained visually: tilesets, animations and fonts are not in the repo (only 15 converted map PNGs and 44 mech-sprite PNGs are).

3. What is genuinely RE'd (and where)

AreaStateCanonical doc
BLD format, cipher, opcodes🟢 soliddocs/formats/bld-bytecode.md
Story text (all 26 BLD)🟢 extracteddocs/story/STORY_TEXT.txt
Memory map (100+ addresses, segments)🟢 soliddocs/formats/memory-map.md
World map / local maps🟢 soliddocs/world-map.md
Combat model🟡 ~90%, some inferreddocs/combat-system.md
Economy / shops / stock🟡 UI flow now observed livedocs/story/story-system.md
ANM format🟢 documenteddocs/formats/anm-format.md
Viewport abstraction🔴 incompletedocs/engine/viewport.md
Sound🔴 0%—

4. Known unknowns (the RE still to do)

These are the real blockers; the roadmap in §6 is gated on them.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    732
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    506
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    405
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    342
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    261
  • 6

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    259

Explore all tools

Browse our collection of tools

View all tools →