Skip to content
InputBooster
InstallationDeployment

Client only

What InputBooster sends to a server, what it cannot do, and why there is no server-side component.

2 min readInputBooster 4.1.2-alphaMinecraft 26.2 / 26.3

InputBooster runs entirely in your client. A server does not install it, does not detect it, and cannot see it. Every action the mod produces ends in an ordinary vanilla client call.

Where it runs

The mod metadata declares the client side in both loaders:

json
"environment": "client",
"entrypoints": {
  "client": [
    "dev.inputbooster.platform.InputBoosterFabric"
  ]
}

There is no server entrypoint, no network packet and no server-side mixin in the project.

What the server receives

The mod does not send packets of its own. It calls the same vanilla entry points a player would call:

ActionVanilla callServer sees
Attack an entitygameMode.attack(player, target)An ordinary attack packet
Use itemgameMode.useItem(player, InteractionHand.MAIN_HAND)An ordinary use packet
Jumpplayer.jumpFromGround()The usual movement state
Sprintplayer.setSprinting(true)The usual movement state

What the mod does not do

  • It does not extend reach. The drainer only attacks a target that is still alive and within vanilla melee range — squared distance 36, which is the 6-block reach vanilla uses.
  • It does not change hit registration or attack cooldown.
  • It does not generate input. Every action starts from a physical key or button press that the mod observed.
  • It does not cancel another mod's key events or remap another mod's bindings.
  • It does not play the game for you. There is no auto-attack loop, no auto- mine and no aim assist.

Why there is no server component

A server-side component would have to either:

  1. Trust the client, which changes nothing about how the client works.
  2. Validate actions, which is the server's job already for reach and cooldown.

The problem the mod solves is entirely client-side: the game reads input once per tick, so a tap that starts and ends inside one tick window is never seen. No server can fix that, because the action never leaves the client.

Multiplayer and other players

Other players see the same thing they would see from a vanilla client: your attacks land, your movement changes, your items get used. Nothing about the mod's internal state — poll rate, queue depth, engine mode — is transmitted.

The replay recorder is a local testing tool. Recordings live in memory only, are never written to disk and are never sent anywhere.