dead-air/game-planning
Watch
3
0
Fork
You've already forked game-planning
 1
Code Issues 22 Pull requests 1 Projects Releases Packages Wiki Activity Actions

Modding support: items, maps, assets #17

New issue
Open
opened 2026-10-18 02:51:05 +00:00 by muse-lantern · 1 comment
muse-lantern commented 2026-10-18 02:51:05 +00:00
Member
Copy link

Goal

Major feature: players can create and add content to the game easily.

Moddable content types

  • Items — custom weapons, equipment, artefacts, consumables
  • Maps — new areas/zones to explore
  • Assets — models, textures, sounds

Design notes

  • "Easily" is the key word — the barrier to entry should be low
  • Built-in modding support (mentioned in the ITR fan game discussion, see #3)
  • Ties into the monetization model: game is 100% free, creator-made "mods" exist outside core gameplay

Technical considerations (Redot/Godot)

  • Resource packs (.pck files) are the natural mod distribution format
  • Mod loading system needs to handle: item definitions, map scenes, asset overrides
  • Item modding should hook into the Affected %/Affliction system (see #8 comments)
  • Map modding: what does a "map" need? (spawn points, loot tables, nav, lighting?)

Open questions

  • In-game mod browser/downloader, or external (like Steam Workshop)?
  • PCVR-first makes modding easier (filesystem access); how does this work on Quest standalone?
  • Scripting in mods? (GDScript mods = powerful but security risk)
  • Asset guidelines: poly budgets, texture sizes for Quest compatibility?
  • How do mods interact with the "can t leave" premise? (new zones inside the Region?)
## Goal **Major feature:** players can create and add content to the game easily. ### Moddable content types - **Items** — custom weapons, equipment, artefacts, consumables - **Maps** — new areas/zones to explore - **Assets** — models, textures, sounds ### Design notes - "Easily" is the key word — the barrier to entry should be low - Built-in modding support (mentioned in the ITR fan game discussion, see #3) - Ties into the monetization model: game is 100% free, creator-made "mods" exist outside core gameplay ### Technical considerations (Redot/Godot) - Resource packs (.pck files) are the natural mod distribution format - Mod loading system needs to handle: item definitions, map scenes, asset overrides - Item modding should hook into the Affected %/Affliction system (see #8 comments) - Map modding: what does a "map" need? (spawn points, loot tables, nav, lighting?) ### Open questions - In-game mod browser/downloader, or external (like Steam Workshop)? - PCVR-first makes modding easier (filesystem access); how does this work on Quest standalone? - Scripting in mods? (GDScript mods = powerful but security risk) - Asset guidelines: poly budgets, texture sizes for Quest compatibility? - How do mods interact with the "can t leave" premise? (new zones inside the Region?)
muse-lantern commented 2026-11-02 04:25:37 +00:00
Author
Member
Copy link

Update: the modding system this tracks is implemented in engine branch craftanything (upstream, tip c64b8bd) — Fabric-style module loader with manifests, entrypoints, dependency resolution, replaces, 14 element types in the base deadair module, docs/modding.md + example mod, and a devkit module of placeholder test content.

Still on the branch, not merged, so leaving this open until it lands. Related engine-side tracking: #27 (follow-ups), #3 (pack format), #25 (grab/physics).

Update: the modding system this tracks is implemented in engine branch `craftanything` (upstream, tip `c64b8bd`) — Fabric-style module loader with manifests, entrypoints, dependency resolution, `replaces`, 14 element types in the base `deadair` module, `docs/modding.md` + example mod, and a `devkit` module of placeholder test content. Still on the branch, not merged, so leaving this open until it lands. Related engine-side tracking: #27 (follow-ups), #3 (pack format), #25 (grab/physics).
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
dead-air/game-planning#17
No description provided.