1.1.0
Compatibility
Required content
Changes
BeaCraft 1.1.0
For Minecraft 1.21.1 only. The 1.0.0 listing claimed compatibility up to 1.21.11: it was compiled against 1.21.1 and crashes on anything else. If you installed it on another version, that is why.
Shipped at last
These landed in the source months ago and never made it into a published build.
- In-game chat is now heard. The mod could write to chat but never read it; agents were deaf to everyone around them. Player messages arrive with the sender's UUID, system lines are marked as such.
- Player join and leave events, diffed from the tab list.
follow_player/goto_player— walk to a player and stay with them.give_item— carry an item to a player and drop it at their feet.
The mod now tells you what it is
- Handshake on connect. The welcome packet carries
mod_version,mc_version,protocoland the full list of actions this build supports. An outdated jar can no longer pass for a current one — before this, a stale mod connected happily and silently ignored half the commands. - Unknown actions answer back with
FAILURE_UNKNOWN_ACTIONinstead of leaving the agent waiting for a completion event that never comes. An unknown action also no longer cancels the skill that was running.
Configuration and packaging
config/beacraft.jsonsetshostandport(defaults127.0.0.1:8080). The port was hardcoded; when something else already held 8080 the server failed silently and the game looked fine.- A busy port is now a loud error in the log rather than one scrolled-past line.
- Declared client-only (
environment: client, client entrypoint). The mod touches client classes at init and had no business claiming to load on a dedicated server. - Relicensed to MIT, matching the rest of projectBEA. The jar declared CC0-1.0 while the Modrinth listing said MIT; MIT is the intended one.
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:px0NmIO6:dC05gK9y"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:px0NmIO6:dC05gK9y"
}

