Links
Tags
Creators
Details
Licensed AGPL-3.0-only
Published 5 months ago
Updated 3 months ago
All versions
1.1.9
Beta
EMILink 1.1.95 months ago 234
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Server-side
Client and server
Changes
[1.1.9]
Added
- Quick crafting in BD crafting GUI: press
Bor Ctrl+click the result slot to single-craft to inventory (singleCraft) - Shift+click items from EMI sidebar to extract from network to inventory: BD interface gives priority to BD, fallback to AE2; in other interfaces, AE2 (wireless terminal required) takes priority, fallback to BD
- NeoForge built-in config screen: shows a Config button in the Mods list, supports modifying all config options in-game
- Search compatibility for ExtendedAE
GuiExPatternTerminalwith F/Alt+F - Search compatibility for AdvancedAE Quantum Crafter Terminal (
QuantumCrafterTermScreen) with F/Alt+F
Fixed
- Fixed persistence issue of EAEP recipe type mapping: after setting the search key in the HEAD stage, reflectively read EAEP's
CUSTOM_ALIASESMap to resolve English-derived keys (e.g.,"reaction chamber") into user-saved Chinese provider names (e.g.,"反应"). The ProviderSelect search box automatically fills with the Chinese name to match the provider, avoiding reselection each time - Fixed EAEP 1.5.3 compatibility:
ProviderSearchHelpernow usesExtendedAEPatternUploadUtil, andpresetCraftingProviderSearchKeyis optionally looked up, preventing silent initialization failures on older EAEP versions due to missing methods - Fixed issue where EAEP upload search box had no recipe ID when writing crafting recipes
Changed
enableWrapBookis now disabled by default- Added
/emilink debugclient command to toggle debug log output at runtime - Added
/emilink wbclient command to toggle wrapped book mode at runtime - Added
wbFillInputGridconfig option (default: false): whether to put the original output item into empty input slots in WB mode - Completed English/Chinese translations and tooltips for all config options
/emilink debugand/emilink wbcommands now automatically save configuration to file
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:andySBF0:lwzEqbTg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:andySBF0:lwzEqbTg"
}

