Repository navigation
reference
Use the example pack index to find a working starting point, the schema index for authoritative JSON contracts, and the generated field-by-field API reference to browse every schema property. The public asset-slot catalog lists supported patch targets.
Validation and errors explains the diagnostic system, while the searchable validation/error-code catalog maps literal runtime codes to their source and message. Troubleshooting covers common author failures, and the Glossary defines project terminology.
Defaults and compatibility defines omission, fallback, migration, and save rules. Resource limits records safety ceilings. Implementation status separates working features from later work, while the v1 release checklist tracks release readiness.
Before publishing one pack, use the smaller mod-author test matrix. Project maintainers use the broader release verification runbook for a complete game release.
The Mod API changelog records public-contract changes and migration guides provide author actions when versions diverge. The authoritative implementation draft remains Docs/Modding/spec-v1.md. Use Implementation status for current capability and the Mod API v1 release checklist for unfinished verification and publication work.
Published from Docs/Modding/Public. The repository documentation is the canonical source.
Captivity Reloaded wiki* Captivity Reloaded Wiki
- Getting started
- Core concepts
- Content types
- Authoring tools
-
Reference
- Example pack index
- Schema index
- Field-by-field API reference
- Public asset-slot catalog
- Core enemy asset slots
- Validation and errors
- Validation/error-code catalog
- Mod API changelog
- Migration guides
- Troubleshooting
- Glossary
- Defaults and compatibility
- Resource limits
- Mod-author test matrix
- Implementation status
- Mod API v1 release checklist
- Release verification runbook
- Release evidence template
- Licensing and redistribution
- Development