Tags
Creators
Details
1.1.0
Compatibility
Changes
Automation
- Command scheduler (
/scheduler) — named schedulers inconfig/mktessentials/scheduler.yml, each with its own command list, selection mode and schedule. Intervals (every: 5m, or5m-10mfor a random one), fixed times of day with weekday filters, a one-shot run after startup, and aspreadthat staggers the commands of a single run. Selection modes:all,random(never the same line twice in a row),random:N,weighted,sequentialandshuffle(every command runs once before any repeats). Conditions gate a run on player count, a named player being online, someone being in a dimension, server uptime, a real-time window or an in-game time window — an unmet condition either skips the run or holds it until it is met./scheduler list|info|history|run|enable|disable|reloadinspect and drive them, and/mkt reloadpicks up file edits without a restart. Permissions:mktessentials.admin.scheduler.view/.manage(ormktessentials.admin.scheduler.*). Config:commands.yml -> admin.scheduler.
Saved Items
- Item storage (
/itemstore) — save exact copies of custom items into named categories and hand them out later./itemstore edit <category>opens a chest: whatever is in it when you close it becomes the category, so adding, removing, replacing and reordering are all one GUI. Every component survives the round-trip — display name, lore, enchantments, attributes, custom model data and mod-added data. Per-item draw weights power crates and random rewards (/itemstore giverandom), items that do not fit drop at the player's feet, and/itemstore announcebroadcasts the reward with the item's own hover tooltip. Combine with/cmdqueueto pay out to offline players. Permissions:mktessentials.admin.itemstore.view/.edit/.give(ormktessentials.admin.itemstore.*). Config:commands.yml -> admin.itemstore.
Command Queue
-
Command queue (
/cmdqueue) — queue console commands to run for a player reliably: as soon as they are online, after a delay, or both. The queue survives a restart, so a purchase made while the server is down is still paid out on the next boot. Statuses (pending,completed,failed,cancelled), full history with who queued what and when, andcancel/retry/remove/clearfor administrators. An optionalkeymakes an entry idempotent so a webstore retry cannot grant the same reward twice. Permissions:mktessentials.admin.queue.view/.add/.manage(ormktessentials.admin.queue.*) (all level 4 — queueing a command equals console access). Config:commands.yml -> admin.queue. -
Report log (
/reports) —/helpopand/reportare now persisted to<world>/mktessentials/reports.loginstead of only reaching the console, and staff can page through them in game with clickable navigation. Permission:mktessentials.admin.helpop.
Optional dependencies
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:dzLZCn7R:QUNgk5Xr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dzLZCn7R:QUNgk5Xr"
}

