Orrery Terrain · support
Support and versions
How to reach us, the reply time (a first reply within two business days), what is supported, and what each version number promises.
Channels
| Channel | Use for | Contact |
|---|---|---|
| Bugs, feature requests, questions, licence and purchase questions, private project data, security reports | support@brassorrery.com |
Reply time
You get a first reply from a person within two business days (Monday to Friday, Belgian public holidays excluded). A fix may take longer.
Supported
- Engine versions: Unreal Engine 5.8 at launch. Each new Unreal Engine version is supported within 30 days of its release.
- Platforms: Windows 64-bit (built and tested; multiplayer tested on a listen server). Linux runtime modules build, but no Linux server has been run, so Linux is not supported yet. Mac, mobile and consoles are not supported.
- Plugin versions: the latest major version gets fixes. The previous minor version gets fixes for critical bugs (data loss, crashes) until the next minor ships.
- Stable API: the headers and Blueprint nodes marked stable (see the versioning policy). Experimental and internal API is answered on a best-effort basis.
Not supported
- Engine or other plugins’ bugs, modified engine builds, and projects that edit the plugin’s source (we will look at a reproduction on the unmodified plugin).
- Custom game code. We answer how the plugin’s API behaves, not how to design your game.
- Platforms and engine versions not listed above.
Reporting a bug
E-mail the details. Include the plugin version, engine version, platform, a minimal reproduction, and the log lines under LogOrreryTerrain. A project we can open beats a description.
If Brass Orrery stops
The licence you bought does not expire, and you keep the C++ source. You can go on using it, modifying it and shipping it in your projects under the same licence terms, even if Brass Orrery stops developing or supporting the plugin.
Refunds and purchases
Orrery Terrain is sold on Fab only. Refunds go through Fab Support under Fab’s refund policy, not through us.
Bug reports
A bug report needs these fields. Fields marked required must be filled in. Send them by e-mail to support@brassorrery.com.
- Plugin version (required)
- Unreal Engine version (required)
- Platform (required)
- Where does it happen? (required)
- What did you expect, and what happened? (required)
- Steps to reproduce (required)
- Log lines
- Checks
Security reports go by e-mail only, never to a public tracker: support@brassorrery.com.
Versioning and saves
Version numbers
MAJOR.MINOR.PATCH.
- Patch: fixes only. No API change.
- Minor: new features and new API. Stable API only gains additions. Experimental API may change, with a changelog line.
- Major: the only version that may remove or change the meaning of stable API.
API stability levels
Every public header says which level it is.
| Level | Promise |
|---|---|
| Stable | Frozen within a major version; changed only by addition. |
| Experimental | Supported, but may change in a minor version. The change is listed in the changelog. |
| Internal | No promise. It is public only because other modules of the plugin need it. |
Deprecation
A stable function or type that is going away is first marked deprecated (UE_DEPRECATED, Blueprint DeprecatedFunction, or [[deprecated]] in the native layer) with a message naming the replacement. It stays for at least one minor version and is removed only in a major version. Blueprint renames keep a redirect.
Save files
- A save written by v1.0 or any later version loads in every later version. It is migrated in memory; the next save writes the newest format.
- An older plugin refuses a newer save with a clear error. It never misreads one.
- The save format is a directory of typed sections. A loader skips a section type it does not know, so additions do not break old readers of the sections they understand.
Engine versions
A new engine version is a minor release. See the support policy for which engine versions are supported (each new one within 30 days of its release).
Determinism
Within a major version, the same inputs and the same edits produce the same state hashes on the same plugin version. A change that alters hashes is listed in the changelog.
What changed in each version: the changelog.