TeamVanilla 
MWEncyclopedia is a reference book for Need for Speed: Most Wanted on PC. It covers every file format, data structure, class and subsystem in the game, built on EA Black Box's EAGL engine, so that someone with a hex editor, a disassembler and patience can understand the game the way its authors did. With it you can swap a texture, rebuild geometry, retune the pursuit AI, replace the soundtrack, or trace a value from a menu screen down to the float it reads out of a vault record.
Everything in it comes from the retail PC data and the shipped executable. It's written format first: byte layouts, the algorithms that read and write them, the runtime classes that consume them, worked examples in portable C++ and Python, and the reasoning behind why each thing is built the way it is.
How it's organised
Every chapter is a short overview followed by eight to twelve pages, each taking one mechanism and answering four questions: what it is, how it works, why it's built that way, and what happens if you change it, done right or done wrong.
Every claim that isn't self-evident carries a label. Verified means confirmed against retail bytes or the executable's code, and reproducible. Reasoned means a well-supported inference about intent or mechanism. Open marks where knowledge stops, stated plainly rather than papered over.
The example code reads and writes raw bytes rather than depending on one program, so it works in any language and outlives any tool. And the world is Z-up and stays Z-up: no parser in the book converts axes, and conversion happens only at an explicit import or export step.
The fourteen parts
| Part | Covers |
|---|---|
| Foundations | The chunk container model, Joaat and Bin hashing, JDLZ compression, byte-level toolcraft |
| Textures and geometry | Texture packs and codecs, materials, solids, vertex formats, mesh import and export |
| Attribute vaults | The VPAK container, the reflection schema, car tuning, pursuit and gameplay vaults |
| The world | Streaming sections, scenery and the cull tree, trigger regions, the CARP road network |
| Audio, video, animation | Sound banks and codecs, music routing, engine sound, VP6 video, NIS cutscenes |
| Front end and saves | Shell scenes, fonts, the minimap, string tables, save containers |
| Runtime classes | The object model, the class registry, vtable anatomy, memory, the file system, the frame spine, streaming |
| Simulation | The vehicle pipeline, the eight mechanics, rigid bodies, tyres, collision, surfaces, damage |
| AI and gameplay | Goals and actions, racer AI, pursuit and heat, cops and roadblocks, traffic, rubber-banding, camera, input |
| Progression | Sessions and modes, the Blacklist, the race rulebook, the game in playing order |
| Rendering | The Direct3D 9 frame order, reflections and car paint, the post chain, particles, sky, weather |
| Customisation | Upgrades and tuning bars, visual parts, vinyls, a car-modding walkthrough from start to finish |
| Scripting and networking | Embedded Lua 5.0.1, the message vocabulary, the online services |
| Workflow | Safe modding, advanced reverse engineering, hash recovery, reading live state from the running game |
Reference material
- Glossary: every term and acronym, the master table of chunk IDs, an extension index with a decision tree for identifying unknown files, and a file-by-file catalogue of the retail data.
- Code library: every reader and writer in the book, collected in one place.
- Struct reference: every documented struct, with offsets and confidence.
- Command vocabulary: the full lists of game actions, messages and cutscene verbs.
- Coverage audit: what's verified, reasoned and open, subsystem by subsystem.
The book's data files are also the source that MWSDK generates its address database from, so the book and the SDK never disagree about a number.