Licensing and community credits

RuneSchema is developed and maintained by the RSDW Modding Community. Credited members are Jonesing4Space, NuLLZz, Snorkles, and CHP. The original RuneSchema work began within the community and is credited to Snorkles in the consolidated member credits.

Official repository and distribution work are published under gh0sted5456-us. The PalSchema foundation is credited separately to Okaetsu.

RuneSchema's code license

Original software and accompanying documentation that RSDW Modding Community owns or has authority to license are available under the MIT License:

Copyright (c) 2026 RSDW Modding Community

The MIT grant permits modification, forks, redistribution, sublicensing, and commercial use of covered code, provided the required notices are preserved. It does not require advance permission for each fork or modification.

• Canonical MIT license
• License scope
• Third-party notices
• Contributor terms

Rights and attribution

Member credits recognize the community's history and contributions. They do not themselves transfer copyright or supply a missing permission grant for existing work. The MIT grant is limited to work the community owns or is authorized to license, as described in the scope document.

PalSchema's and UE4SS's applicable MIT notices remain intact. The root MIT file does not override component licenses or relicense UPX, game assets, Epic Games engine material, or other separately licensed content.

The code license is not permission to impersonate the official project, and it does not grant third-party trademark, game, or engine rights. No extra non-commercial restriction is being added to MIT-covered software.

Downloads

Newly generated packages combine LICENSE, AUTHORS.md, LICENSING.md, CONTRIBUTING.md, THIRD_PARTY_NOTICES.md, and applicable dependency notices into settings/licenses/RuneSchema-Licenses.txt. It is the only packaged license file and contains the complete texts, component names, and upstream links. The same credits travel with the single RuneSchema package, Helpy, source, and example packages handled by the licensing helper.

Maintainers must still review component-specific requirements. Older releases and Nexus uploads are not changed automatically. Each distributed copy must retain the applicable notices.