Links
Tags
Creators
Details
2.0.0
Compatibility
Changes
Changelog
⨠New Features
š Stage Preview
- Added
/stage preview <name>to preview a stage before loading. - Added
/stage preview exitto leave preview mode. - Preview now uses a smooth fade transition.
š¤ Selective Loading
- Added support for loading only a specific player's state.
- Added support for loading only the environment (time & weather), leaving players untouched.
š Stage Notes
- Added stage notes.
- Use
/stage notes <name> <text>to attach notes to a stage. - Use
/stage notes <name> clearto remove notes.
ā Stage Rename
- Added
/stage rename <old> <new>to rename stages without saving them again.
ā Pin / Favorite Stages
- Pin important stages so they always appear at the top of the stage list.
š¦ Export & Import
- Export stages to JSON files.
- Import stages from JSON files.
- Makes sharing and backing up stages much easier.
š„ Completely Redesigned GUI
- Brand-new interface.
- Cleaner layout.
- Better organization.
- Improved usability.
- Added GUI animations.
- Added confirmation GUI for important actions.
š Save Props
- Stage saves now include props used during recording.
⨠Cosmetic State Saving
Save Stage now also preserves:
- Active potion effects
- Glowing status
- Scoreboard tags
This makes scene retakes much more accurate for cinematic productions.
š” Improvements
Load Conflict Prevention
If two staff members try to load the same stage almost simultaneously, the plugin now displays a confirmation warning:
"This stage was just loaded by <player>. Proceed anyway?"
This helps prevent directors from accidentally overwriting each other's work.
Player Notifications
Players affected by a stage load now receive a Title or Action Bar notification informing them that their state has been restored by the director.
Smooth Fade Transition
Loading and previewing stages now use a fade transition for a more cinematic experience.
Spectator Protection
Players in Spectator Mode can now be excluded from stage loading, allowing camera operators to remain unaffected.
GUI Improvements
- Improved navigation.
- Cleaner stage list.
- Better visual feedback.
- Smoother animations.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:bluPllfg:6g9vYiJ2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bluPllfg:6g9vYiJ2"
}

