This is a savegame editor for the cyberpunk retro game HardWar. This editor was created as an experiment on the highly dynamic data structures of its savegame file. While it mostly serves as a savegame parser, it does have the ability to edit basic information like pilot cash, moth health/shields, and hangar cash.

To use this editor, simply navigate to the deployment page Here. You can begin editing a savegame by clicking 'Open', then selecting your savegame file. Note that this editor only supports UIM 6 (Steam release or latest patch) savegames. Use the tab control to navigate between moths, pilots and hangars. Use the dropdown to select the moth, hangar, or pilot you wish to edit. Click 'Save' when you are done, and the editor will generate a new savegame file based on the modifications made.

The data structures of the HardWar savegame are highly dynamic. The pilot entity list start offset is pointed to by the pointer stored on 0xDF8. The hangar entity list start offset is pointed to by the pointer stored on 0xDE0. The moth entity list is pointed to by the pointer stored on 0xDD4. Pilot entities are 0x37C in size, hangar entities are 0x964 in size, and moth entities are 0x448 in size. Offsets relevant to the savegame entity lists can be found in the table below.

The moth entity list start is pointed to by the pointer stored on 0xDD4. With each moth data structure being 0x37C in size, this value can be used as an iterator to step through the moth entity list. Stored at the end of the moth data structure is a pointer to the dynamic address of the next moth in the entity list. When a moth is destroyed, it is removed from the moth entity list. So the moth "array" is more than likely a vector, rather than an array.

The hangar entity list is stored after the moth entity list. The location of the hangar entity list start is stored on offset 0xDE0. With the offset of the first hangar in the entity list, it is then possible to step through the hangar entity list using the iterator 0x964.

After the hangar entity list is the final entity list; pilots. The total pilot entity count is stored on offset 0xDF4. The start of the pilot entity list is pointed to by the vaue stored on offset 0xDF8. The value stored on offset 0xDFC points to the list of dynamic pilot addresses. When a pilot "dies", they are teleported to the Limbo! hangar.

For the moth data structure itself, the value on offset 0x1D0 points to the hangar that the moth is currently parked in. If the moth is not in a hangar, then it becomes a null pointer. Similarly, the values on offsets 0x2DC and 0x2E0 are both pointers that point to the pilot and the passenger, respectively. If there is no pilot or passenger, they also become null pointers. The value stored on offset 0x1DC stores the "type" of moth. The remaining offsets hold the values of shields and damage.

The hangar data structure's values on offset 0x010 points to the owner of the hangar. If the hangar is owned by a pilot, it will point to the pilot's dynamic address. If the hangar is owned by a faction, it will point to the location of the faction's headquarters (i.e. "Police HQ"). The values stored on offsets 0x8D8 - 0x8EC point to the moth that is currently residing in the respective hangar bay. If the hangar bay is empty, the pointer is null.

For the pilot data structure, the value on offset 0x030 represents the location of the pilot. If the pilot is in a moth, it will point to the moth's dynamic address. If the pilot is on foot in a hangar, then it will point to the dynamic address of the hangar. The value on offset 0x298 represents the faction that the pilot belongs to. If a pilot belongs to a faction, it will point to the dynamic address of the faction's headquarters. If the pilot is not a member of a faction, it will be a null pointer.

• Special thanks to ShroudedNight for improving the editor's pilot and moth parsing ability.