1.2.0
Compatibility
Changes
1.2.0 - whitelist mode and profiles
Added
-
Whitelist mode. Each list can now be read the other way round: instead of "never pick these up", a whitelist means "pick up only these, filter out everything else". Switch it with the new "Filter mode" button on the settings screen.
An empty whitelist is treated as filter off, not as "block the whole game" - a fresh profile you have not filled in yet leaves pickups alone, and the screen says so in red.
-
Profiles. The list of items is now one of several named profiles, shown in a sidebar on the left of the settings screen. Click a profile to switch to it; New, Rename and Delete sit above the list. Each profile keeps its own items and its own mode, so a "mob junk" blacklist and a "mining trip" whitelist can live side by side and switching between them is one click.
Every profile row shows a B or W marker, so a whitelist is recognisable without switching to it first. Deleting a profile asks for confirmation, and the last remaining profile cannot be deleted. Up to 32 profiles.
-
The keybind that opens the settings screen now closes it again when the screen is already open, so it works as one toggle.
-
The item picker shows which profile you are editing and in which mode.
Changed
- The item counter under the grid reads "X items blocked" on a blacklist and "X items allowed" on a whitelist.
Notes
- Existing configs are migrated automatically: the old item list becomes a single blacklist profile named "Default", with nothing lost and nothing to click. The file gains "profiles" and "activeProfile" keys on the next save, and the old flat "blocked" key is no longer written - a config saved by 1.2.0 opens as an empty list on 1.1.0 and earlier.
- Server behaviour is unchanged. On a dedicated server a filtered item is still picked up and thrown straight back out, whichever mode decided it was filtered.
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:whZIYBvg:dozCS21d"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:whZIYBvg:dozCS21d"
}

