Tags
Creators
Details
Licensed Apache-2.0
Published 8 months ago
Updated 7 months ago
All versions
2.0.0
Beta
Ly+ Settings 2.0.07 months ago 400
Compatibility
Minecraft: Java Edition
1.21.x
1.20.4–1.20.6
Platforms
Bukkit
Geyser Extension
Paper
Purpur
Spigot
Changes
Ly+ Settings — Changelog
2.0.0 — Major Rewrite
2026-03-11
This is a full rewrite. Nothing from 1.x was carried over unchanged.
✨ Added
- LyPlusAddon API — addons can now register themselves, inject GUI items, handle clicks, and share player data with the core
- AddonRegistry — thread-safe registry for all installed Ly+ addons
- Navigator row — bottom row of the
/settingsGUI shows a shortcut icon for each installed addon /settings addons— lists every currently loaded Ly+ addon with version/settings reload— reloads core config and triggersreloadAddonConfig()on every registered addon- Persistent player data via Gson (
data.json) — supportsboolean,int, and freeformaddonDatastring map for cross-addon storage - Utility methods exposed on
LyPlusSettingsfor addons:createInventory,fillBackground,createItem,addBoolItem,addCycleItem,updateBool,updateInt,playSound,getBoolSetting,getIntSetting,getPlayerData - Paper Brigadier commands — rewritten using
LifecycleEvents.COMMANDSandCommands.literal();paper-plugin.ymlreplacesplugin.yml - Distinct sounds per action in the settings GUI
🔧 Changed
- Command registration moved from
getCommand().setExecutor()to Paper's Brigadier API (required forpaper-plugin.yml) - Chat filter packet listener rebuilt cleanly with correct system/player message detection logic
🗑️ Removed
- Legacy
plugin.ymlreplaced bypaper-plugin.yml CommandExecutor/TabCompleterinterfaces removed from main class
1.x.x — Legacy
No public changelog. These versions are no longer supported.
💬 Questions or issues? Join our Discord
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:xxkx0cjZ:H2Nn9KON"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xxkx0cjZ:H2Nn9KON"
}

