Licences
Draft
Not in forceVersion 1
In short
- Open scripts carry a licence you choose.
- MPL-2.0 is the default.
- Protected and unlisted scripts keep all rights.
1. Choosing a licence
Only an open script carries a licence you choose, and MPL-2.0 is the default. Protected and unlisted scripts keep all rights.
2. The licences
Mozilla Public License 2.0
- You allow
- Anyone may use, change and share it, also inside a larger closed project.
- You require
- Changed files are shared under the same licence with their source, and your notices stay.
- You disclaim
- You give no warranty and are not liable for how others use it.
MIT License
- You allow
- Anyone may use, change, share and sell copies.
- You require
- Your copyright notice and the licence text stay with every copy.
- You disclaim
- You give no warranty and are not liable.
Apache License 2.0
- You allow
- Anyone may use, change, share and sell copies, with a patent licence for your part.
- You require
- Keep your notices, include the licence and mark the files you changed.
- You disclaim
- You give no warranty and are not liable.
GNU General Public License 3.0
- You allow
- Anyone may use, change and share it.
- You require
- Anything built from it and shared is also GPL-3.0, with its source.
- You disclaim
- You give no warranty and are not liable.
All rights reserved
- You allow
- Others may run it inside Forge as the content licence allows, and nothing more.
- You require
- Nobody may copy, change or share the code without your permission.
- You disclaim
- The Forge terms' limits on warranty and liability apply.
3. What a licence does not change
The house rules and the credit rule on the publishing rules apply whatever the licence. A summary is not the licence: the licence text decides.
Changes to this page
- 6 Oct 2026, Version 1: First draft.