Tags
Creators
Details
All versions
1.3.0+1.21.1
Release
AE2Organizer-neoforge-1.21.1-1.3.0.jar3 months ago 136
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Required content
Any compatible version
Changes
AE2 Organizer v1.3.0
Filter tabs grow up: organise them into multiple movable windows, exclude items, and share your setups.
Added
- Exclude (Not) conditions — an Is/Not toggle on every condition;
Nothides matches on top of your positive filters (e.g. "oak OR spruce, NOT sophisticatedstorage" in one tab). - Multiple filter windows — split your tabs across several on-screen windows.
- Movable windows — drag any window by holding Alt, or via a dedicated move mode.
- Vertical or horizontal layout — per window; horizontal renders as an icon-only bar.
- Per-window options — size, labels vs icons, gear on/off, "All" entry on/off.
- Per-terminal positions — a window remembers a different spot per terminal type; new terminals inherit your first layout.
- Per-terminal visibility — show or hide a window per terminal type.
- Windows & tabs tree editor — collapsible; copy a tab or a whole window, move tabs between windows, reorder.
- Copy tab button and a "Window…" picker to move a tab between windows.
- Clipboard import/export — copy a window's filters (or your entire setup) as plain JSON and paste to share or back up. Import replaces (with a confirm).
/ae2organizer resetwindows— recover to a reachable layout at any time.
Changed
- Renamed the editor and settings screen titles.
- Presentation settings (size, labels) moved from global settings to per-window.
Notes
- Fully client-side; works on any server. Config auto-migrates from older versions.
- Available for Minecraft 1.20.1 (Forge), 1.21.1 and 26.1 (NeoForge).
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:xugd56Pv:qbVpLstY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xugd56Pv:qbVpLstY"
}

