Skip to content

Values of This Community

Free, Open Source Community

  • We are built on open-source principles for collaboration and sustainability.
  • We cannot and will not provide support for private closed source mods.
  • Mods must be freely available to all to avoid burnout, frustrations and resentment. Please review the Monetization Policy.

Proper Attribution and Credit

  • Credit the original creator of any code, asset, idea, or work that you use, modify, or build upon.
  • Credit is best listed in readmes for viewability. It can also be in descriptions, in the mod itself, or anywhere the mod is listed.

Follow Licensing Requirements

  • Adhere to the licensing requirements associated with any work you use. This may include specific attribution instructions, providing a copy of the license with the work, or restrictions on use, particularly commercial use.
  • See Licensing & Attribution for practical guidance on choosing a license and crediting others' work.

Collaboration

  • Pull Requests: If a mod exists that already covers your interest, consider contributing via pull request on GitHub. Keep PRs simple and clear. Do consider PRs submitted to you: you don't need to accept them if they don't follow your vision, but communicate those issues.
  • Be mindful that you need to share framework triggers; respect longstanding uses by other mods. Similarly, if you can change something to make room for others, consider it.
  • Respect Active Projects: While we are open source, we do not support or platform re-releases of active mods. Building on an active project should involve meaningful expansion or rework, not minor additions under a new name. Names must not use unique titles of active mods.
  • Follow the procedures regarding taking over abandoned mods.

Responsibility for Mod Content

  • Transparency: Maintain transparency through open source. Document significant changes via readme files and changelogs. If your mod has potential risks, make them clear.
  • Security: Ensure your mod does not contain harmful code, such as malware, hidden data collection, or unannounced commands.
  • Testing: Test your mods thoroughly to provide a stable experience. Bugs will happen, but strive to minimize them. If you need help testing, ask the community or release test versions via GitHub and link them on the Discord rather than publishing to sites first.
  • Ethical Practices: Do not create or distribute mods that violate the game's terms of service, EULA, or community guidelines. No cheats, backdoors, or unlocking player access to DLCs. As a community, we want to stay on good terms with the studio to keep mods available.

Education

  • Sharing knowledge is essential for community growth and progress. Passing on expertise and tools allows for new features to be developed.
  • Treat all members with respect, regardless of experience level. While we expect a level of self-initiative from people learning, we are here to provide guidance.
  • Contribute articles to the Wiki for ease of learning for others.