Tags
Creators
Details
1.5.4.1-26.1.x
Compatibility
Changes
Aurelium builds each market item at the moment you buy or sell it, so the item you end up with always matches the item the dashboard showed you. This release finishes that for the two kinds of item that share one base item between them: mob spawners and enchanted books. The developer patch notes cover the same change file by file and are at patchnotes.md.
What Was Wrong
- Buying a mob spawner from the dashboard gave you an empty spawner - every mob spawner is the same basic item, with the specific mob stored inside it. When you bought through the dashboard that detail was dropped, so you paid the iron golem spawner price and received a spawner with nothing in it. Enchanted books had the same problem: you paid the price of the spell you picked and received a book with no spell on it.
- Selling a spawner or an enchanted book paid out the most expensive price - this was the more serious half. When you sold through the dashboard, the check only confirmed you were holding something of the same basic kind, so one empty spawner could be sold over and over as the most valuable spawner in the game, and one empty book could be sold as the most valuable spell. If you sold any mob spawner or enchanted book through the dashboard, it is worth checking your balance.
What Changed
- Items bought through the dashboard are now built exactly the way they are when you trade through the in-game shop, so a mob spawner arrives with its mob in it and an enchanted book arrives with its spell on it.
- Selling now only takes the exact item you picked. A plain spawner can no longer be sold as an iron golem spawner, and a plain book can no longer be sold as a named spell.
- Buying and selling through the dashboard now check the money actually moved. Previously the server would hand over the item without confirming the payment had gone through, and would take your items without confirming it could pay you. If a payment fails you now get a clear message and nothing changes hands.
- If your server's database is not on the same machine, money commands may feel slightly slower. Buying, selling, paying and any other money operation now waits for the database to confirm before reporting back, instead of reporting immediately and quietly sorting it out afterwards. That wait is what makes it possible to tell you the truth about whether the money moved. If you notice lag spikes on money operations and your database is remote, this is why.
- Everything else, including all ordinary blocks, ores, mob drops and crops, behaves exactly as before.
What You Need To Do
Nothing. This replaces your current download, your prices are unchanged, and no configuration needs editing. Take the download that matches your Minecraft version, the same as always.
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:LJ9k5olE:NlFnceAQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LJ9k5olE:NlFnceAQ"
}

