1. Modlet Structure
Identify the folder, config files, and what the mod changes before writing instructions.
Modlet
Modding Basics
7DTD modlet basics.
Prepare folder structure, ModInfo.xml, XPath edits, server scope, and release notes before sharing files.
Modlet Checklist
Version, scope, rollback
Name the game version, explain the change, and test on a copy before anyone uses it on a real save.
2. ModInfo.xml
Record name, author, description, version, dependencies, and compatibility notes clearly.
Metadata3. XPath Edits
Keep XPath changes small, readable, reversible, and tied to the game version being targeted.
XPath4. Release Notes
Explain install scope, server-side support, save risk, permissions, dependencies, and test status.
PublishCommon modding questions
| Topic | Check | Risk boundary |
|---|---|---|
| First modlet | Small scope, clear metadata, and one change you can test. | Never edit a live server or only save first. |
| Modlet scope | Small XML/config changes that can be explained and reversed. | Safe only after target-version testing. |
| XPath edits | XML paths can break when updates rename, move, or restructure game data. | Mark version-sensitive edits as Needs Review. |
| ModInfo.xml | Name, author, version, description, dependencies, and compatibility notes. | Dependencies and permissions must be visible. |
| Server-side scope | Confirm whether players need client files or only the server needs the mod. | Always confirm multiplayer scope. |
Author FAQ
Before you share a modlet
Local modlet build
Prepare folders, metadata, XPath notes, test save, and release notes.
What belongs on a release page?
Version support, install scope, dependencies, permissions, changelog, save risk, multiplayer notes, and a clear support contact.
How does this connect to server owners?
Server owners need clear server-side mod notes, pack requirements, update checks, and player instructions before a season or event starts.