Technical wiki for creators and addon developers.
Permitted addons and developer guidelines
What you may build around Flash Replay, what is not allowed and how to publish compatible addons without breaking license or stability.
Free downloadAll Rights ReservedNeoForge 1.21.1
01
Base rule
Flash Replay is a Free download and is All Rights Reserved. You may create compatible addons or content, but you may not redistribute the mod, its assets, a modified jar or source code.
An addon must be a separate project that depends on the official mod installed by the user.
Permitted add-ons are external content, presets, compatibility layers or integrations that respect user consent, license boundaries and the technical limits documented here.
02
Permitted addon types
| Addon type | Allowed when |
|---|---|
| Resource packs / translations | They use your own assets or text and do not copy proprietary logo, icons or media without permission. |
| Visual presets or look guides | They distribute values, instructions or your own files, not internal mod files. |
.franim animation libraries | They contain animations created by you and not private replay material without consent. |
| Actor skin/cape packs | They use correctly licensed skins/capes and clear import instructions. |
| Export profiles | They distribute presets or documented values without force-overwriting user config. |
| Compatibility mods | They use optional dependency, do not bundle Flash Replay, do not modify the official jar and fail safely. |
| Server companion integrations | They require client consent and never start recordings without explicit opt-in. |
03
Not allowed
- Redistributing the Flash Replay jar inside an addon or as a modified file.
- Publishing a patched Flash Replay build.
- Copying code, UI, logo, banners, GIFs or official screenshots as your own assets.
- Using names or icons that make an addon look official when it is not.
- Bypassing user consent for recording, Save Last, export or upload.
- Reading or uploading user replays/exports to external services without clear consent.
- Treating unstable internal classes as a public contract when this wiki has not declared them as API.
04
Recommended technical contract
- Treat
com.lordbanana.flashreplay.*as internal unless a future public API page explicitly says otherwise. - No stable SDK-style entry points are public yet: until they are documented here, do not treat them as supported.
- Use optional dependencies and loader checks so your addon does not crash when Flash Replay is absent.
- Do not mix into Flash Replay classes to change core behavior without explicit agreement.
- Do not write directly into the user's config JSON; provide presets or controlled import instead.
- Declare the tested Flash Replay, Minecraft and NeoForge versions.
05
Naming and publishing
- Recommended naming:
Addon Name for Flash ReplayorFlash Replay compatibility for ModName. - Write
Unofficial addonclearly when it is not published by the Flash Replay maintainer. - Link the official Flash Replay page as the dependency.
- Do not use
Flash Replayas the only name of your project. - Your addon can use your own license, but it cannot grant rights over Flash Replay or its assets.
06
Release checklist
- Verify the addon works without bundling the Flash Replay jar.
- Declare dependencies and tested versions.
- Remove copied Flash Replay assets unless you have explicit permission.
- Add a privacy note if you touch recording, replay files, exports or upload.
- Test startup with and without Flash Replay installed.
- Test on a fresh Minecraft profile so you are not relying on local config.