Tags
Creators
Details
2.0.0
Compatibility
Changes
READ ME!
This update has many changes, please read the changelog carefully before updating.
Config Overhaul
The plugin should automatically migrate to the new formats for you.
Each GUI now has its own config file instead of putting everything in config.yml.
The config files of the GUIs are under gui/ directory.
gui.main > main.yml
gui.your-orders > your-orders.yml
gui.choose-item > choose-items.yml
gui.search-sign > search.yml
gui.delivery > deliver.yml
gui.enchant-item > enchant.yml
gui.new-order > new-order-dialog.yml
gui.confirm-delivery > confirm-delivery.yml
gui.manage-order > manage-order.yml
In container GUIs, you can now specify the amount of rows.
For main, your orders, choose items, enchant item GUIs, you can now specify a list of slots where the
orders/items/enchantment books should be put in respectively.
Buttons now have 2 keys, item and slot; name, lore, item model of the button is now moved to the item key, under
components, providing a more vanilla format.
name-prefix in enchant GUI's config is changed to name.active and name.inactive
sort-prefix and sort-types are now merged to sorts-display, allowing you to set the text for each sort type when
it is active and inactive.
FastStats
The plugin now uses FastStats to collect anonymous data. Besides default metrics it collects, Orderium also tracks errors at different places, and these data:
- API Usage: a boolean determines if your server is using API from Orderium
- Experimental features: a string array contains names of experimental features being used
- Order amount: an integer shows the amount of orders have been created
- Items collected: an integer shows the amount of items collected from all orders
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:EH2l9h8i:61H49hkl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EH2l9h8i:61H49hkl"
}![Orderium [Order System]](https://cdn.modrinth.com/data/EH2l9h8i/b8588f4efad9cc563b50d8568cb3c6ee3629a336_96.webp)

