Can we have mods in DCSS?

Back Room Game Design Discussion
1

Proposal: Implementing a Modding System for Dungeon Crawl Stone Soup (DCSS)

Re-written by AI so the world doesn’t need to read my jumble of confusing Ideas. Original.

Overview

This proposal outlines a system for integrating modding capabilities into DCSS. By enabling modular gameplay changes through a well-defined modding framework, the game can foster greater community engagement, experimentation, and longevity while maintaining the integrity of the core game.

Background

DCSS is an open-source game that actively welcomes community contributions. Many successful additions have come from player-driven innovations, including new vaults, monster speech, and gameplay tweaks. However, larger-scale changes or divergent ideas often conflict with the game’s core design principles and end up as separate forks. While this allows for creativity, it fragments the community and makes it difficult for experimental features to stay current with the main game.

A modding system would provide a solution by enabling players to experiment with new features without creating separate branches. Mods could integrate seamlessly into the existing game and coexist alongside the core experience, offering a flexible approach for both developers and players.

Proposal

Modding Framework

Introduce a dedicated directory within the DCSS installation:

/dat/mods

Each mod would have its own folder containing the required files and metadata. Players can activate mods by specifying them in their configuration file (e.g., options.rc):

mods += example_mod

A basic in-game mod management menu could allow players to enable or disable certain mods dynamically, but only for UI or visual changes (not gameplay mods).

Mod Structure

Mods would follow a standardized structure, including a manifest file (e.g., mod.json) that defines key attributes:

{
  "name": "example_mod",
  "version": "1.0",
  "description": "Adds a new race and two new gods to the game.",
  "compatibility": ">=0.27",
  "files": [
    {"source": "zig.cc", "target": "src/zig.cc"},
    {"source": "cloud_generator.h", "target": "src/cloud_generator.h"}
  ]
}

Compatibility Handling

  • Version Checks: Mods designed for older versions of DCSS would prompt the user to confirm activation in newer versions, with warnings about potential issues.
  • Mod Conflicts: If two mods are incompatible, the game could prompt the user or disable one automatically.

Modding Capabilities

Mods could:

  • Add new races, gods, or spells.
  • Modify existing gameplay mechanics (e.g., balancing tweaks).
  • Introduce UI changes or visual overhauls.
  • Replace assets such as tiles or sound effects.

For example:

  • A mod could introduce a new race, the “Frostborn,” with cold resistance and ice magic specialization.
  • Another mod could add a god, “Ixar, the Shifting Sands,” with abilities tied to desert-themed mechanics.

(Examples by Chat-GPT. Obviously, Frostborn would be a cheating Draconian)

Benefits

For Players

  1. Customization: Players can tailor their experience to match their preferences.
  2. Innovation: Experiment with new ideas without waiting for official integration.
  3. Ease of Use: A centralized system simplifies mod installation and activation.

For Developers

  1. Focus: Developers can concentrate on maintaining the core game while supporting an ecosystem for experimentation.
  2. Testing Ground: Mods can serve as a testing ground for features that might later be integrated into the core game.

For the Community

  1. Collaboration: Encourages players and developers to share ideas and collaborate.
  2. Longevity: Keeps the game fresh and engaging over time, even as official updates slow down.
    (Um, what, AI? Do you know what our dev-team is like?)

Challenges

  1. Development Effort: Implementing a robust modding system requires significant time and resources.
  2. Server Compatibility: Multiplayer servers would need to handle mod synchronization and validation.
  3. Testing: Ensuring stability with mods enabled adds complexity to the development process.

Implementation Steps

  1. Design the Modding Framework:

    • Define the folder structure, metadata format, and file handling mechanisms.
    • Create hooks in the game engine to allow mods to override or extend functionality.

  2. Build Core Functionality:

    • Implement basic mod loading and activation.
    • Develop a configuration system for enabling/disabling mods.

  3. Add Compatibility Features:

    • Implement version checking and conflict resolution mechanisms.
    • Provide fallback options for mods designed for older versions.

  4. Develop Example Mods:

    • Create sample mods to demonstrate the system’s capabilities and serve as templates for the community.

  5. Documentation:

    • Publish guidelines and best practices for creating mods.
    • Maintain a central repository or forum for sharing mods.

  6. Community Feedback and Refinement:

    • Collect input from players and modders to refine the system.
    • Address edge cases and improve usability.

Conclusion

A modding system for DCSS would empower the community to contribute in new and exciting ways, fostering innovation and ensuring the game’s continued growth. While challenging to implement, the long-term benefits for players, developers, and the game’s legacy make it a worthwhile investment.

2 Thanks
2

Um, ai, how would changing zig and cloud gen add a new race and two new gods?

1 Thank