Tags
Creators
Details
1.15.7
Compatibility
Changes
MineboxAdditions 1.15.7
Older versions of MineboxAdditions are still compatible. Please read carefully "Trusted sessions" section below.
Features
- Item Atlas: elemental resistances — Resistance stats (Earth, Air, Fire, Water) now display with their proper localized names.
- Item tooltips: resistance roll ranges — Holding ALT on an item now shows the
min/max roll range (e.g.
[-8 to -4]) for elemental resistance stats.
🔒 Trusted sessions
There are now two modes for MineboxAdditions: "trusted" mode and "untrusted" mode. In "untrusted" mode, the server ignores all client events (Shinies, Shops, Weather, Siren, etc.). This mode still allows you to use all of MineboxAdditions features (you will still receive everything), but you cannot send events.
"trusted" mode works the same way as it did before this update.
How do I get trusted ?
This process is automatic upon connecting to Minebox.
How does it work then ?
It works by doing a background Minecraft connection to the server session.mineboxadditions.bartier.me when connecting to Minebox. This server has online-mode=true, so Mojang servers checks if you are legitimate or not (like it would do when connecting to Minebox). Once this is done, the session server kicks you with a signature message. This signature is sent when connecting to the MineboxAdditions server where it's authenticity is checked. You are then "trusted" or "untrusted".
Okay but does the signature contains any data ?
Yup! But no more than already used by MineboxAdditions: player name, player uuid, and a timestamp (to know when the signature has been generated). Feel free to take a look
Why this ?
This have been in the box for two months already. To prevent malicious actors from annoying players. It will still happen from time to time, but now irrevocable actions can and will be taken on my side.
I want to opt-out
You can opt-out by using a version <1.15.7 of MineboxAdditions. "untrusted" mode only builds and sources will be provided on Curseforge and Github respectively.
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:HFGMc58X:XEytSpSE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HFGMc58X:XEytSpSE"
}

