Tags
Creators
Details
All versions
1.4.16+26.3
Release
Simple AutoPickup 1.4.16+26.36 days ago 355
Uploaded by
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Server-side
Client and server
Required content
Any compatible version
Changes
Added
- 26.3 support (Fabric and NeoForge).
- 1.16.5 support (Fabric and Forge). 1.16.5 uses the built-in config screen because YACL isn't available for this version.
- 1.12.2 support (Forge 14.23.5.2864). Requires MixinBooter 11 or newer. It has the same commands, per-server client profiles, master keybind and three-tab config screen as the other versions (open it from the Mods list or with
/autopickup gui).
Fixed
- Forge/NeoForge clients now sync on dedicated servers. On Forge 1.20.1 and 1.21.0-1, and NeoForge 1.21.0-1 through 26.2, joining a dedicated server never sent your client profile or loaded the server's admin state and global config. LAN hosts also re-synced every time a guest joined. Both are fixed.
- NeoForge client profiles now switch per server. On NeoForge 1.21.9 through 26.2, players were always on
client_default.toml. The profile now switches when you join and leave a server, like on every other loader. - Fabric crash on older Fabric Loader versions. Builds made with Loader 0.19.5 crashed at startup on older Loaders with a
ClassCastException. They now load on both. Behavior is unchanged.
Changed
- On 26.1 and 26.2, YACL is now pinned to 3.9.6 for each loader. This replaces the temporary Fabric build that both loaders were using.
- Internally, the logic that doesn't depend on Minecraft now lives in one module that every version shares. Settings, commands and loot splitting should now behave the same on every version.
Optional dependencies
Any compatible version
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:ycs4OjaI:7lRk1WD7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ycs4OjaI:7lRk1WD7"
}

