Links
Tags
Creators
Details
1.0.2
Compatibility
Required content
Changes
ZyloLotto Changelog
[1.0.2] - 2025-11-26
New Features
-
Max Tickets per Player
- New configuration option
max_ticketsinconfig.yml:max_tickets: 0 # 0 = unlimited, any positive number = max tickets per player - Players can now only buy a limited number of tickets if
max_tickets> 0. - New language file entries (
de_DE.yml,en_US.yml):button.buy_ticket.lotto_status: Shows the current lottery status (auto-draw on/off) in the buy button.message.max_tickets_reached: Message when a player reaches the ticket limit.message.max_tickets_set: Confirmation when the limit is changed.message.max_tickets_prompt: Prompt to enter the limit in chat.button.set_max_tickets: Button in the admin menu to set the limit.
- New configuration option
-
Admin Menu: Set Max Tickets
- New button in the admin menu (
AdminGUI.java) to configure the maximum number of tickets per player. - New utility class:
MaxTicketsSetter.javafor chat input of the limit.
- New button in the admin menu (
Changes to Existing Features
-
GUI Titles and Button Lore
- MainGUI: The "Buy Ticket" button now displays the current lottery status (auto-draw on/off).
- AdminGUI: New "Set Max Tickets" button (slot 14) with dynamic display of the current limit.
-
Language Files (
de_DE.yml,en_US.yml)- New entries for the max tickets feature (see above).
- Adjusted lore for the "Buy Ticket" button to show the lottery status.
-
Configuration File (
config.yml)- New option
max_tickets(default:0= unlimited).
- New option
Bug Fixes & Improvements
-
GUI Navigation
- TicketGUI, DrawHistoryGUI, WinnersGUI: Improved title checking in
onInventoryClickmethods to prevent incorrect GUI interactions. - "Back" button in all GUIs now always returns to
MainGUI(no direct closing).
- TicketGUI, DrawHistoryGUI, WinnersGUI: Improved title checking in
-
Code Structure
- Consistent formatting and comments in all new/modified classes.
- New utility class
MaxTicketsSetter.javafor chat input of the ticket limit.
Technical Changes
-
Database & Backend
- No changes to the database structure.
- Logic for the ticket limit integrated into
MainGUI.java(buy button) andZyloLotto.java(chat event handler).
-
Build & Dependencies
- No new dependencies.
- Maven Shade Plugin and Spigot/Vault dependencies unchanged.
Summary of Changes
| Category | Change |
|---|---|
| New Features | Max tickets limit per player, admin option to set the limit. |
| GUI | New button in admin menu, lottery status in buy button. |
| Language Files | New entries for max tickets feature. |
| Configuration | New option max_tickets in config.yml. |
| Bug Fixes | More robust GUI navigation, consistent "Back" button functionality. |
| Version | 1.0.1 → 1.0.2 |
Note for Users
- Backward Compatible: Existing databases and configurations remain intact.
- Optional: The new max tickets feature is disabled by default (
max_tickets: 0).
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:TB8RPfRf:jPU4gVPq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TB8RPfRf:jPU4gVPq"
}

