Revisit CC-BY-NC-ND license for code, snippets and templates #46

Why it matters

CC-BY-NC-ND-4.0 forbids derivatives and commercial use. For a developer tool this has real consequences:

• Contributions: ND means nobody may distribute modified versions, which conflicts with CONTRIBUTING.md inviting PRs and forks (a fork with changes is a derivative).
• Adoption: NC excludes commercial game studios and indie developers selling games, which is most of the target audience. It is unclear whether code generated from the snippets or templates inside a commercial game is permitted.
• Distribution: some marketplaces and MCP directories prefer or require OSI-approved licenses. Creative Commons itself recommends against CC licenses for software.

Evidence

• LICENSE, .cursor-plugin/plugin.json ("license": "CC-BY-NC-ND-4.0"), README badge.
• mcp-server/ (Python code) and snippets/ / templates/ (C# meant to be pasted into games) fall under the same license.

Options to decide

1. MIT or Apache-2.0 for code (MCP server, snippets, templates) and CC-BY-4.0 for prose (skills, rules, docs). This is the common pattern and maximizes adoption.
2. Keep restrictions on skills and rules but explicitly grant users rights to use snippet/template code in any game, commercial or not.
3. Keep as is, but add a FAQ that clearly states what users may do with generated code.

Pair the choice with sponsorship tiers (GitHub Sponsors is already linked) if monetization is the goal of NC.

Done when

A license decision is recorded and README has a short "Can I use this in my commercial game?" answer.