All versions
1.0.5
Release
LootRun 1.0.54 months ago 56
Compatibility
Minecraft: Java Edition
1.20.1–1.20.6
Platform
Forge
Supported environments
Client and server
Changes
LootRun 1.0.5 Changelog
This update focuses on stability in large modpacks, trade-terminal quality of life, and safer price scanning.
Main Fixes
- Fixed enchanted books showing
Cannot buy: No price sourcein the trade terminal. - Fixed raid return/extraction teleport clearing the player's experience level and progress.
- Added exact full-stack selling support in the trade terminal so stacks with non-power-of-two counts no longer leave awkward leftovers.
- Fixed multi-select selling from the trade terminal triggering server anti-spam kicks.
- Added a dedicated batch sell packet for selected stash items. The client now sends one packet instead of many
/lootrun trade sell_stashcommands. - Batch selling now validates all selected stash entries on the server, processes them together, saves once, and syncs player data once.
- Added
jeiPriceScannerconfig for the JEI price scanner. It is enabled by default and hot-reloadable. - Improved Create 6.x compatibility by guarding Create recipe reflection behind optional runtime checks.
- Reduced the chance of large modpacks freezing or exiting during startup because of broken third-party JEI recipe categories.
- Deferred expensive generated-price refresh behavior while editing trade prices so editing does not repeatedly rebuild prices mid-input.
- Kept the manual
lootrun trade sell_stashcommand available for admin/debug use, but the trade screen no longer uses command spam for normal selling.
New Config
Configuration file:
config/lootrun-common.toml
Section:
[compatibility]
New option:
jeiPriceScanner = true
What it does:
true: creative operators and singleplayer owners may scan JEI recipe layouts to provide extra generated price seeds.false: LootRun will not run the JEI layout scanner. This can help very large modpacks that have broken JEI categories or severe startup memory pressure.- The option is hot-reloadable. Save the config while the game/server is running and LootRun will resync trade configuration to online players.
Why These Issues Happened
- The old multi-sell flow sent one client command per selected stash row. Selling many selected items could send many commands in one moment, which some servers treated as command/chat spam.
- Enchanted books use runtime enchantment data instead of a simple registry-item price. Some buy checks did not route through the runtime price path correctly, so the trade terminal could report no price source.
- Minecraft/Forge teleport paths can reset or desync experience data during dimension changes. LootRun now snapshots and restores player experience around internal hideout teleports.
- JEI layout scanning is useful for unusual recipe displays, but some modpacks contain JEI categories that throw errors while building recipe layouts. LootRun already catches those errors, but the scan can still be expensive in large packs, so it now has a config switch.
- Create recipe APIs can change between Create versions. LootRun now treats Create special recipe reads as optional reflective compatibility instead of assuming a fixed API shape.
Upgrade Notes
- Replace
lootrun-1.0.4.jarwithlootrun-1.0.5.jar. - Clients and servers must both update to 1.0.5 because the network protocol changed for the new batch sell packet.
- If a server or LAN pack still feels slow while opening a world, try setting
jeiPriceScanner = falseinconfig/lootrun-common.toml. - If JEI price scanning is disabled, normal server-side recipe pricing still works. The disabled part is only the client-side JEI layout scan for extra unusual recipe data.
- Existing trade configs and player data are kept.
Testing Checklist
- Buy an enchanted book from the trade terminal and confirm it no longer says
No price source. - Extract or return to the hideout with experience levels and confirm the experience is preserved.
- Select many stash items in the trade terminal and sell them at once, then confirm the server does not kick the player for spam.
- Sell a stack with a non-power-of-two count and confirm the full-stack sell action can sell the whole stack.
- In a large modpack with JEI installed, start a world with
jeiPriceScanner = true, then toggle it tofalseand confirm the config hot reloads without restart. - Test with Create 6.x installed and confirm LootRun no longer crashes from Create recipe API differences.
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:9BfkbLEO:8lDCjPoR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9BfkbLEO:8lDCjPoR"
}

