Click on a field like Damage or AmmoCount . Change the value from 30 to 100 . Hit Apply . Then, crucially, run Tools > Fix Checksum . Save the file. Copy it back to your game directory (backup the original first).
Launch zedit32, go to File > Open . Navigate to your game’s directory (e.g., JediKnight/Resource/ ). Select a .GOB or .KEY file. Don’t be alarmed by the binary gibberish. zedit32
If you have ever tried to alter the fabric of a classic Dark Forces game, tweak the assets of a 1998 LucasArts title, or simply want to understand the pre-history of modern game editing, you need to know what zedit32 is, how it works, and why it remains relevant today. zedit32 is a 32-bit hex editor and resource explorer initially designed to work specifically with proprietary game engine archives. While the name might sound generic, in modding circles, it is synonymous with editing files for games built on the Jedi Engine (used in Star Wars: Dark Forces II: Jedi Knight ) and the Sith Engine (used in Star Wars: Jedi Knight II: Jedi Outcast and Jedi Academy ). Click on a field like Damage or AmmoCount
For the Jedi Knight modding community (often called the "Massassi Temple" era), zedit32 was nothing short of revolutionary. If you manage to find an archive of the original tool (often distributed as a ZIP file under 500KB), here is what you can expect: 1. Dual Pane Interface The classic layout featured a hex view on the left and an ASCII/decoded view on the right. But the killer feature was the template pane at the bottom, which would dynamically parse data structures as you clicked through the file. 2. Template Compiler Users could create .tpl (template) files. A simple template might look like this: Then, crucially, run Tools > Fix Checksum