Links
Tags
Creators
Details
Licensed CC0-1.0
Published 4 years ago
Updated last month
All versions
1.1.0-1.21.1
Release
FURC 1.1.0-1.21.1 (NeoForge)last month 57
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Remote Controlled 1.1.0 - Minecraft 1.21.1
Fixed in 1.1.0
- Binding now works on modded blocks that handle clicks themselves (Create's Stock Ticker and similar): sneak-binds are intercepted before the block or any other mod sees the click, and remote use now triggers the same interaction hooks vanilla does, so blocks whose screens live in the item-aware hook respond.
- Sneak-clicking an entity with a remote now says remotes bind to blocks, instead of silently doing nothing (or triggering the entity).
The 1.21.1 line (Fabric + NeoForge)
- NeoForge support. The energy remote charges through Forge Energy machines on NeoForge and Team Reborn Energy chargers on Fabric.
- Channel Upgrade: craft one (copper + amethyst around an ender pearl) and use it while holding a remote in your other hand to add a binding channel. Sneak + scroll with an upgraded remote to switch between its bound blocks (up to 5 channels by default, configurable).
- Claim and protection mod support: remotes respect claim mods and vanilla spawn protection.
- Five advancements, sounds and particles, energy readout in the tooltip, a Remote Controlled creative tab, and a mini icon of the bound block on the remote's item icon.
- Config: requireLoadedChunk, maxChannels, energyMaxIO; xpPerUse set to -1 disables the XP cost.
- Fixes carried over from 1.20.1: remotes no longer interfere with each other, only remote-opened screens stay open at range, off-hand use works, double chests open fully, range respects dimensions, the XP cost reads your real XP, renamed remotes work.
Notes
- Fabric requires Fabric API, Architectury API and Forge Config API Port. NeoForge requires Architectury API.
- Config file: config/remote_controlled-common.toml.
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:B5KGNfnU:x6IvH7Xd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:B5KGNfnU:x6IvH7Xd"
}

