Command aliases were just causing issues with other commands, therefore they have been removed. Also increased some thread counts for better performance

This release will add Resources as a dependency to generate a resource pack on the server effortlessly, as well as adds chroma gradient events.

Also, 1.19 support.

Featured beatmap: Noctua by glacier

https://www.youtube.com/watch?v=dz9uMqrcbec

Nightclub is now cross-compatible with spigot and minestom

Includes 1.18.2 support

What's Changed

• Added optional flag to not use chroma events (/beatmap play (map) [true/false]) the player will still automatically use chroma events by default, just add the flag true to disable chroma events.
• Fixes delay with speed events
• Fixes(?) critical issue causing weird behavior when modifying data of a cloned light

What's Changed

• Proper chroma support
• More user-addressable variables (startX, lightID)
• General code refactoring
• In-depth command errors
• Debug markers to show the color of a light
• Light cloning (/light clone) to clone all the properties of a light except for location and name

Featured beatmap: Aiobahn - About U Download

What's Changed

• Strobes now have moving laser beams aswell
• Fixed various issues (e.g lights not stopping before/after playback) and cleaned up code
• (re-)Added bStats https://bstats.org/plugin/bukkit/BeatMapVisualiser/12300

Please read (or re-read) the previous beta for instructions on how to get started with v2.0.

Featured beatmap: Its time to live a lie. DOWNLOAD

This release is a beta version of v2.0. There may (will) be bugs, and you will encounter errors ingame and in the log. A tutorial on how to use v2.0 will come at a later date.

Since this is a beta of v2.0, there are still some missing stuff, namely the beat saber rings, API or chroma support

To get started:

1. Create a new LightUniverse with the command /lightuniverse build
2. Load the newly created LightUniverse with /lightuniverse load Unnamed-Universe-1
3. You can now use the /light build command to create lights, and then /light data <option> <parameter> to change its data. 3.5. To modify a previous light, use /light load <light name> to load it back in
4. Once you are happy with your light setup, do /beatmap play <beatmap name> to visualise it

Please use the light and lightuniverse naming tools to keep track of your lights and universes, namely the commands /lightuniverse setname <name> (Only renames currently loaded light universe) /light data name <name> (Only renames currently loaded light) All names must be one-liners-like-this