Links
Tags
Creators
Details
0.0.1
Compatibility
Changes
invertoTimer v0.0.1 — Release Notes
This is the first public release of invertoTimer, a lightweight Velocity plugin for network-wide countdowns and scheduled events.
Highlights
invertoTimer introduces a simple but flexible timer system built around two core ideas: Timers (when an event happens) and Outputs (what players see and what actions run).
Timers
Timers can be scheduled using either:
- Cron (repeatable schedules)
- Fixed time (one-shot, absolute timestamp)
Showcases (Countdown Displays)
Timers can broadcast countdown information using multiple showcase types:
- Actionbar
- Bossbar
- Chat text
- Title showcase (supports both title and subtitle under a single
showcases.titleconfiguration)
Player-visible showcase text supports:
- Placeholders such as
{remaining},{days},{hours},{minutes},{seconds},{id},{description},{target} - MiniMessage formatting for rich colors and styles
{i18n:key}tokens for language-based text substitution
Actions (Scheduled Triggers)
Timers can trigger actions at offsets relative to the target time:
- Text action: message/actionbar/title/subtitle output
- Transfer action: send matched players to a target backend server
- Command action: run commands as console or as matched players
Player selection for transfer and command (executor=player) uses:
transfereeas a Java regex matching online player usernames (matches()), with".*"selecting all players.
Server Limitations
Both global and per-timer server limitations are supported to control where timers apply (blacklist/whitelist by backend server name).
i18n
The plugin supports language files via .properties bundles and can be reloaded with configuration reload.
Notes
- This is an early release (
0.0.1). Configuration format and features may evolve based on feedback. - Please report issues and suggestions via GitHub Issues, including config files and logs when possible.
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:wi8i7ZIl:hqWtldW3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wi8i7ZIl:hqWtldW3"
}

