Skip to content

Frontiers Engine SRD License

License Version: 1.0
Applies to: All documents published under the Frontiers Tabletop Engine team on HackMD (located at https://hackmd.io/@frontiers-engine), including overviews, section expansions, modules, revisions, and official variants among other things.

 

1. License Framework

The Frontiers Tabletop SRD is licensed under the Open RPG Creative (ORC) License.

All Open Game Content within this project is made available under the terms of the ORC License. Except for content explicitly designated as Product Identity in Section 6.

To use Frontiers content, you must comply with the ORC License in full.

The full ORC License text can be found at: https://paizo.com/orclicense

 

2. Scope of This License

This License applies to all documents published under the Frontiers Tabletop Engine team on HackMD (located at https://hackmd.io/@frontiers-engine), including but not limited to:

  • Overview documents
  • Section Expansions (ⓘ linked documents)
  • Modules
  • Revisions
  • Official variants
  • Supplemental or expanded materials
  • Future updates and published versions

Unless otherwise explicitly stated within a specific document, all rules text contained within these materials is designated as Open Game Content under the ORC License.

If a module or document lists additional contributors, those contributors retain authorship of their contributions. However, unless explicitly stated otherwise, their contributions are also released under the ORC License.

 

3. Attribution Requirements

If you publish a project using Frontiers content, you must include:

Required Attribution Line:

Powered by the Frontiers Engine, Version X.X (https://hackmd.io/@frontiers-engine)

You must:

  • Specify the exact version number of the Frontiers document you are referencing
  • Include a link to the Frontiers Tabletop SRD team page
  • Credit individual modules separately if used

Module Attribution

If you use material from a specific Frontiers Module, you must additionally include:

Includes material from the [Module Name] Module by [Author Name] (link)

Each module must be credited independently.

 

4. Version Referencing

Because Frontiers is a living system, version clarity is mandatory.

When referencing Frontiers content, you must:

  • State the specific Frontiers version used
  • Avoid implying compatibility with versions not used
  • Avoid presenting modified versions of the engine as official Frontiers releases

You may not represent your project as an official Frontiers release unless explicitly authorized.

 

5. Use of the Name “Frontiers”

You may use:

  • “Powered by Frontiers”
  • “Compatible with Frontiers”
  • Clear attribution statements

You may not:

  • Use “Frontiers” as the primary title of your product in a way that implies it is the official core engine
  • Present a fork as the official continuation of the Frontiers SRD

Derivative systems must maintain clear brand distinction.

 

6. Product Identity

The following are designated as Product Identity and are not Open Game Content:

  • The name “Frontiers Tabletop SRD” and “Frontiers Tabletop Engine” as titles of the core engine
  • The Frontiers logo and associated visual branding
  • Official Frontiers layout, formatting, and graphical presentation
  • Any official artwork, logos, layout files, or branding assets published by the Frontiers team

You may reference the name for attribution purposes, but you may not use official branding assets without explicit permission.

 

7. Commercial Use

Commercial use is permitted under the ORC License.

You may:

  • Publish paid products using Frontiers
  • Monetize compatible systems
  • Release independent modules

All such works must comply with attribution requirements.

 

8. Community Guidance (Non-Binding)

Frontiers is intended to function as a shared ecosystem rather than a fragmented field of competing core engines.

While the ORC License allows forks and derivative engines, it is strongly encouraged:

  • Maintaining compatibility where possible
  • Publishing derivative competing works as “Powered by Frontiers”
  • Avoiding monetized forks that directly compete with the Frontiers core engine

This section is not a legal restriction.
It is a good-faith request to preserve a collaborative design space.

 

9. License Updates

Future versions of the Frontiers SRD may be released. Each version of the Frontiers SRD will include its own version number or ID for clarity.

Projects may continue using the version under which they were originally published.

New versions may refine rules, structure, or modules, but will not retroactively alter permissions granted under prior releases.

 

10. Contact

For official releases, module submissions, or partnership inquiries:

contact@jaykepaver.me

Frontiers Tabletop SRD
Created by Jayke Paver