The pages are grouped the way a mod is made: write, assets, build and ship, world, run. Each one reads the game from your Steam folder, never writes there, and explains itself with F1.
Every page in two minutes, narrated.
Edit Enforce Script with the whole vanilla game indexed: completion, go to definition, references, errors as you type.
Draw menus and HUDs with the game's own fonts and imagesets, or write them as HTML (DZML) and get the .layout. Then give them buttons and panels of your own.
Everything about UI · Layout guide · How DZML works · Style Studio guide
Look at any game model with its LODs, selections, proxies and textures, write model.cfg, and bring your own meshes in from Blender or an AI generator.
Both pages are previews: test an edited effect or graph in game before you ship it. Particles guide · Animations guide
Pack and binarize, create your key, sign, check, then publish to the Workshop with pre-flight checks and a Discord announcement.
Start a local DayZ server and the game with your mods in one click, or the offline diag game. Logs are followed live and script errors are explained.
The same guides are on this site: documentation.
Every format is re-implemented from the files themselves and checked against the real game data on each build.
The game folder and its !Workshop mods are never written. Nothing from the game is exported or redistributed.
Encrypted and obfuscated PBOs stay closed. Hotfixes are separate mods, and one that copies the author's code can't be published.
Private keys, Steam sessions and Discord webhooks never leave your computer and are never sent to a model.