EasyAFK

The problem

Most Minecraft servers auto-kick players after a period of inactivity to keep the player list clean and protect against AFK farming exploits. That's reasonable server design — right up until you actually need to step away for a few minutes and lose your spot, your queue position, or an in-progress task.

The approach

EasyAFK is split into two parts that mirror how the mod actually works in practice: the mod itself (Java) runs client/server-side inside Minecraft and handles the moment-to-moment logic of staying "present" without needing constant input, while EasyAFK-Server is a separate Python companion service that handles logic that doesn't belong inside the game's mod loader — coordination, configuration, or control that's easier to reason about outside the JVM.

Why two languages

Splitting the client mod from the server-side companion let each half use the right tool: Java because that's the language Minecraft mod loaders (Forge/Fabric-style) expect, and Python for the companion server because it's faster to iterate on for anything that isn't tightly bound to Minecraft's game loop. It's the same pattern I lean on elsewhere — pick the language the specific half of the problem actually needs, not whatever the rest of the project happens to be written in.

What it does well

• Keeps a player's session alive without requiring constant manual input.
• Separates in-game mod logic from server-side coordination logic cleanly.
• Ships as a real, installable Minecraft mod — not just a script.