Answers · mods

Does a GPL label on a mod pack give me rights to the other people's mods in it?

Short answer: No. A license can only be granted by someone who holds the rights, so whoever assembled a pack can put the GPL only on the parts they made or already had the right to license that way. Every mod in the pack stays under its own author's license, whether that is GPL, MIT, a Creative Commons license, a custom "don't reupload" term or all rights reserved. The GPL itself says so: putting a GPL'd work alongside separate works in an "aggregate" does not make the GPL apply to the other parts. Before you redistribute, modify or reuse a mod from a pack, check that mod's own license, and the game's own rules for mods.

Checklist

1. List the mods in the pack and find each one's own license, on its project page, in its repository's LICENSE file or in the files inside the mod.
2. Treat no license as no permission: a mod with no stated license is all rights reserved, whatever the pack says.
3. Check what each license allows for your plan: redistributing the file, including it in your own pack, modifying it, or using its code or assets in your own mod. Some authors allow modpack inclusion but not reuploads.
4. Prefer linking or a manifest that downloads mods from their official pages over rehosting files, where the platform supports it.
5. Use the pack author's GPL only for what the pack author made: their configs, scripts and original files.
6. Check the game's EULA and the hosting platform's rules: they can limit commercial use of mods and how packs may be distributed.
7. When in doubt, ask the mod author in writing and keep their reply.

Why the label doesn't spread

• Copyright in each mod belongs to its author (or whoever they assigned it to). Collecting mods does not transfer those rights to the collector.
• GPL-3.0 section 5 calls a compilation of separate, independent works an aggregate and says including a covered work in one does not cause the license to apply to the other parts.
• The reverse also holds: if a mod in the pack is GPL, you can use that mod under the GPL, with its source and notice duties, but not the mods next to it.

License checks (computed)

Yes means the license grants the use, on the duties listed. Duties such as source_disclosure, share_alike and network_source_offer are the ones that conflict with keeping a product closed-source.

Ask Rightshold (free, no key)

Add the MCP server https://www.rightshold.com/mcp to Claude, Cursor, ChatGPT, Grok or VS Code, then ask: “My pack has mods under GPL-3.0, MIT and CC BY-NC-SA 4.0. What can I redistribute, and on what terms?”

One-click setup

{
  "tool": "license_compatibility",
  "arguments": {
    "licenses": [
      "GPL-3.0-only",
      "MIT",
      "CC-BY-NC-SA-4.0"
    ],
    "intended_use": {
      "redistribution": true,
      "modification": true
    }
  }
}

• check_rights_batch checks up to 100 items, one per mod, in one call.
• Pass a mod's GitHub page as source_url and Rightshold reads the license that repository declares.

Rightshold reads the licenses you name or point it at. It cannot see licenses that are not published, and it does not interpret a game's EULA or a platform's rules for you.

Sources

• GNU General Public License v3.0 (section 5, aggregates)
• GNU GPL FAQ: mere aggregation
• 17 U.S.C. § 201: ownership of copyright
• Choose a License: no license

Related

• Can I use GPL code in proprietary software?
• Can I use CC BY-NC assets in a paid game?
• GPL vs AGPL

Not legal advice. Updated 2026-10-29. JSON · Markdown · All answers

curl -s -X POST https://www.rightshold.com/v1/accounts/signup -H "Content-Type: application/json" -d '{"accept_terms":true}'
export RIGHTSHOLD_API_KEY=rs_...   # the api_key from the reply (shown once)
curl -s https://www.rightshold.com/v1/licenses/check -H "Authorization: Bearer $RIGHTSHOLD_API_KEY" \
  -H "Content-Type: application/json" -d '{"license":"MIT","intended_use":{"commercial_use":true}}'