Reverse engineering guidelines

People who have read the Minecraft source code are most valuable to us as reverse engineers. This is the process of reading the decompiled Minecraft source and explaining in (detailed) plain english how it works, in the form of documentation on this wiki. The idea is to have enough detail that we can write code from scratch that behaves exactly the same way. See the Sky page for a good example.

There are a few guidelines here to ensure that TrueCraft remains a clean-room effort.

1. Never share Minecraft source code with clean developers.
2. Never share any Minecraft-related source code that you have written as a result of your reverse engineering efforts with clean developers.
3. Use the beta 1.7.3 codebase for your reverse engineering.

When writing your documentation, try to describe how the subsystems work without using code - write down equations and plain english explanations of things instead. If you must resort to code, use psuedocode (fake "code" that uses a made-up programming language and doesn't compile).

Wishlist

Things we'd like to see documented in detail:

• Terrain generation
• Physics engine (this one will be nasty to reverse engineer)
• TODO: fill in more wishlist items