Analyzing Game Code

The Challenge: Obfuscation

Crab Game is compiled with Il2Cpp (C++ instead of C#) and obfuscated with Beebyte Obfuscator. This means:

1. You can't easily decompile it like a normal Unity game.
2. Type names, fields, and methods appear as random gibberish.

To mod effectively, you need two things: a way to reference code in your mod (CrabDevKit) and a way to read the code logic (Mac Build).

Part 1: Deobfuscating Your Project

To write code that references the game, you need to translate the gibberish names into readable ones. We use CrabDevKit for this.

1. Fix Type Names (Intermediary.cs)

Copy CrabDevKit's Intermediary.cs into your project. This file gives the obfuscated types global aliases.

// Instead of accessing "MonoBehaviour1PublicInamUnique", you can now use "PlayerManager"

2. Fix Fields & Methods (Extensions)

Refer to CrabDevKit's IntermediaryExtensions.cs. You can either:

• Copy the specific extensions you need into your project.
• Include CrabDevKit as a dependency.

Part 2: Inspecting Logic (The Mac Build)

While CrabDevKit helps you write code, it doesn't help you read the game's internal logic. For that, we use the Mac build of Crab Game, which uses Mono instead of Il2Cpp. This allows us to view the source code in tools like dnSpy.

How to Download

steam://nav/console

download_depot 1782210 1782212 4682332062135883449

Tips for Navigation in dnSpy

Even in the Mac build, names are obfuscated. However, you can now:

• Rename types/methods in dnSpy as you figure them out.
• Delete garbage methods generated by the obfuscator.
• Cross-reference with Intermediary.cs to match the gibberish names to real names.