https://github.com/jeff-1amstudios/carmageddon-1-cheat-code-disassembly

Reverse engineering Carmageddon 1 cheat code system
https://github.com/jeff-1amstudios/carmageddon-1-cheat-code-disassembly

assembly c carmageddon dos gamedev reverse-engineering

Last synced: 24 days ago
JSON representation

Reverse engineering Carmageddon 1 cheat code system

• Host: GitHub
• URL: https://github.com/jeff-1amstudios/carmageddon-1-cheat-code-disassembly
• Owner: jeff-1amstudios
• Created: 2018-11-23T04:16:07.000Z (about 6 years ago)
• Default Branch: master
• Last Pushed: 2019-10-29T17:26:57.000Z (over 5 years ago)
• Last Synced: 2024-11-29T15:51:28.635Z (3 months ago)
• Topics: assembly, c, carmageddon, dos, gamedev, reverse-engineering
• Language: C
• Homepage:
• Size: 4.31 MB
• Stars: 14
• Watchers: 5
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Carmageddon 1 disassembly [![Build Status](https://travis-ci.org/jeff-1amstudios/c1-disassembly.svg?branch=master)](https://travis-ci.org/jeff-1amstudios/c1-disassembly)

Join the [Discord channel](https://discord.gg/f5StsuP)!

In 1997, [Carmageddon 1](https://en.wikipedia.org/wiki/Carmageddon), a fun destruction/racing open-world game was first released.

In 2014, Watcom debugging symbols for an earlier internal build [were discovered](http://1amstudios.com/2014/12/02/carma1-symbols-dumped) on the [Splat Pack](http://carmageddon.wikia.com/wiki/Carmageddon_Splat_Pack) expansion CD release. The symbols unfortunately did not match any known released executable, meaning they were interesting but not immediately usable to reverse engineer the game.

This is what it looked like from the Watcom debugger - the names of all the methods were present but the code location they were pointing to was junk:

![watcom-debugger](http://1amstudios.com/img/watcom-debugger.jpg)

_CrayzKirk_ from the Carmageddon community did the painstaking work of manually matching up functions and data structures in the executable to the debugging symbols.

And now we begin the next step - reversing the assembly code back into _as original as possible_ C code.