TImingLeague is a Minecraft plugin designed to work with the Timing System plugin. It helps server admins manage racing leagues: track multiple events, score drivers (and teams), generate leaderboards / standings, etc. All core functionality is now implemented; what remains is polishing, UX tweaks, and refinements.
- Support for leagues spanning multiple racing events.
- Score drivers based on performance; customizable scoring systems (in progress).
- Support for teams: drivers can belong to teams, team standings are tracked.
- Driver / team standings across events.
- Permissions system: e.g.
timingleague.adminfor full access,timingleague.viewfor viewing standings and team info. - Soft-dependency support for Decent Holograms for showing holographic outputs (if available).
- Minecraft server (version compatible with Timing System).
- The Timing System plugin installed (hard dependency).
- Optional: Decent Holograms for holographic display of standings.
- Download the plugin JAR (from releases or build it).
- Place the JAR in your server’s
plugins/directory. - Ensure
Timing Systemplugin is also inplugins/. - Restart or reload the server.
-
Permissions:
Permission Effect timingleague.adminFull access: create leagues, manage teams, modify settings. timingleague.viewCan view standings, team information. -
Commands & GUI: (to be finalized — e.g. how to create an event, how to add drivers, how to view standings, etc.)
-
Teams: Drivers can be grouped into teams; team owners (or admins) can manage drivers on their team.
-
Scoring: (If implemented) support for different scoring presets or custom scoring systems.
- Event generation based on presets.
- Allow for completely custom scoring systems.
- Reworking the team system (e.g. only team owners can edit their drivers).
- Fix issue: teams not always persisting correctly in the database.
- Store team colors in database.
- Add feature: export standings, teams, etc., to CSV.
If you want to help:
- Fork the repo, make changes, submit pull requests.
- Coding standards: follow existing style (e.g. Java conventions).
- Tests or sample worlds are helpful.
- Bug reports & feature suggestions: open an issue.