Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/TheNextLvl-net/cinematics/llms.txt

Use this file to discover all available pages before exploring further.

Cinematics ships with sensible defaults — no manual plugin.yml editing is required. This page documents the built-in settings for server administrators who need to understand how the plugin integrates with Paper/Folia.

Plugin Metadata

The following values are baked into the plugin at build time via the paper block in build.gradle.kts. They are exposed to the server through the generated plugin.yml.
FieldValue
NameCinematics
Version0.1.0
Main classnet.thenextlvl.cinematics.CinematicsPlugin
API version1.21
Load orderSTARTUP
Folia supportYes
AuthorsNonSwag
Websitehttps://thenextlvl.net

Permissions

Cinematics exposes a single permission node that guards every /cinematic sub-command. Assign it to any role or player you want to grant recording and playback access.
Permission nodeDescription
cinematics.command.cinematicGrants access to all /cinematic commands (record, stop, play, etc.)

Granting the permission with LuckPerms

Use the commands below to assign the permission to a specific player or to an entire group:
/lp user <player> permission set cinematics.command.cinematic true
/lp group <group> permission set cinematics.command.cinematic true
Replace <player> with the player’s username and <group> with your desired LuckPerms group name (e.g. admin, moderator, vip).

Load Order

The plugin declares a load order of STARTUP, which means Cinematics is initialised before any world has finished loading. This guarantees that:
  • All /cinematic commands are registered and tab-completable as soon as a player joins.
  • Internal data structures are ready before any world-specific events are fired.
  • No timing race conditions occur between Cinematics and plugins that depend on world state.
In practice you do not need to change this value. It is documented here so that server owners who sequence plugin load order manually are aware of the intent.
No configuration files are generated by the plugin at runtime in the current version — all configuration is handled via plugin.yml defaults and the messages bundle.

Build docs developers (and LLMs) love