0.1.0
Compatibility
Required content
Changes
AE2 Quick Stow is a lightweight quality-of-life addon for Applied Energistics 2.
While exploring dungeons, structures, or modpack worlds, open a loot chest or another container and click the “Stow into AE Network” button below the container, or press the default F key. Eligible items are sent directly into the ME network connected to a wireless terminal carried by the player, without using the player inventory as an intermediate step.
Features
- Adds a stow button below real container screens, including chests, barrels, furnaces, crafting tables, and modded containers.
- Provides a rebindable GUI key mapping, bound to F by default.
- Moves items directly from the open container into the connected ME network.
- Respects AE2 network status, wireless range, power, security permissions, and available storage capacity.
- Supports partial insertion: anything the network cannot accept remains in the original container.
- Reports successful transfers, missing terminals, and full-network states through the action bar.
- Optionally detects wireless terminals equipped in Curios slots.
How to Use
- Carry a connected and usable AE2 wireless terminal.
- Open any real container.
- Click “Stow into AE Network” below the container, or press F.
- Read the action-bar result.
The key can be changed in Minecraft's control settings. The button is not shown in the normal player inventory or the creative inventory.
Terminal Compatibility
The mod detects terminals through AE2's GridLinkables, IMenuItem, and IPortableTerminal APIs instead of maintaining a fixed item-ID list.
Wireless terminal addons implemented through AE2's standard terminal contracts will generally work without dedicated compatibility entries. Portable storage cells are intentionally not treated as wireless terminals.
Transfer Rules
- Only slots belonging to the currently open container are processed.
- Player inventory slots are never moved.
- Empty slots and output-only result slots are skipped.
- All real insertion operations are performed server-side by the AE2 terminal host.
- Items that cannot fit in the network remain in the original container.
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:V96xAnJU:M8H4iwyM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:V96xAnJU:M8H4iwyM"
}

