-
Notifications
You must be signed in to change notification settings - Fork 690
Description
Hi everyone,
I'm experiencing a persistent issue when running my Mindcraft bot on a Minecraft LAN world (Open to LAN). The bot connects successfully, spawns, and can receive chat messages, but shortly after executing any action (or even just standing idle), it gets kicked with the error:
[LoginGuard] Disconnected: multiplayer.disconnect.invalid_entity_attacked
Environment:
· Mindcraft version: Latest from GitHub (develop branch)
· Minecraft version: 1.16.5 (Java Edition)
· Server type: LAN world (Open to LAN from singleplayer)
· OS: Windows 11 Pro (64-bit)
· Node.js version: (e.g., v18.17.0)
· AI Model used: Local Ollama with custom model sweaterdog/andy-4:micro-q8_0
Logs:
C:\Users\Мансур\Desktop\ai for minecraft\mindcraft-develop\mindcraft-develop>node main.js
MindServer running on port 8080
MC server found. (Host: localhost, Port: 25565, Version: 1.16.5)
Client connected
Connecting to MindServer
Client connected
andy connected to MindServer
Starting agent
Initializing agent andy...
Examples initialized.
No task.
andy logging into minecraft...
andy logged in!
andy updating available agents
Initializing vision intepreter...
andy spawned.
received message from system : Respond with hello world and your name
Saved memory to: ./bots/andy/memory.json
selected examples:
Example: miner_32: Hey! What are you up to?
Example: say hi to john_goodman
Awaiting local response... (model: sweaterdog/andy-4:micro-q8_0, attempt: 1)
executing code...
[LoginGuard] Disconnected: multiplayer.disconnect.invalid_entity_attacked
Agent andy disconnected
Agent process exited with code 1 and signal null
Restarting agent...
What I've tried so far:
· Disabled all automatic modes (self_defense, elbow_room, cowardice, etc.)
· Added long delays (30 seconds) after spawn
· Implemented "human-like" behavior (random looks, small movements, inventory checks)
· Set physics to match normal player speeds in mcdata.js
· Used viewDistance: 'tiny' and disabled chat signing
· Tried both with and without only_chat_with settings
Additional notes:
· The bot works perfectly on a dedicated local server (Paper 1.16.5 with anti-cheat disabled), but the issue only occurs on LAN worlds.
· I suspect the client-side anti-cheat (or the LAN host) is flagging the bot's behavior as invalid.
· Error appears even when the bot is just standing still after receiving items or chat messages.