Botting and mods

FortressMC permits client modifications and non-combat automation that remain within the actions available to a human using an unmodified client. Modifications that enable impossible movement, reach, interaction, or sustained input rates are prohibited. Automated inputs may not be used in player-versus-player combat.

This page expands upon the cheating policy in the server rules.

Display modifications

Client modifications that change only the presentation of information are permitted. These include x-ray overlays, freecam, entity radar, ESP, minimaps, cave maps, light-level displays, schematics, build holograms, and interface or nametag changes that do not alter gameplay hitboxes.

Server-side anti-xray obfuscates concealed ore blocks in the Overworld. It does not hide player-built blocks, containers, or bases from client display modifications.

Cosmetic modifications, texture packs, shaders, performance improvements, world downloads, replay tools, mapping tools, and level-of-detail renderers are also permitted. Inventory utilities such as block selection, tool selection, replenishment, and chest sorting may be used outside combat. They may not be used during combat or to provide a direct combat advantage.

Prohibited modifications

Prohibited modifications include:

  • kill aura, aimbot, automatic targeting, and other combat automation;
  • automated inputs of any kind during player-versus-player combat;
  • interaction beyond vanilla reach;
  • flight, speed, noclip, Jesus, spider, and comparable movement modifications;
  • fast breaking or interaction that bypasses vanilla distances or cooldowns; and
  • duplication, illegal-stack, packet, or protection-bypass exploits.

Automation

Bots, macros, scripts, and accessibility tools may automate mining, farming, crafting, movement, trading, building, and similar activities outside combat. Their actions must remain reproducible by a skilled human using a vanilla client.

The following limits apply to automated input:

InputLimit
Sustained clicking20 clicks per second
Horizontal rotation180 degrees per second, or 9 degrees per tick at 20 TPS
Vertical rotation90 degrees per second, or 4.5 degrees per tick at 20 TPS
Reaction timeAt least 100 milliseconds after newly observed client information

Brief human-like click bursts above 20 clicks per second are permitted, but sustained rates above that threshold are not. Automated view movement may not snap to a target within a single tick. Movement and interaction must obey vanilla physics, collision, visibility, and reach.

Combat

All combat inputs must be manual. The prohibition includes auto-clickers, aiming assistance, combat macros, and inventory automation used while fighting another player. Display modifications remain permitted during combat.

Questions about a particular modification or automation design may be submitted through the FortressMC Discord. Reports of impossible movement, reach, or combat automation should include supporting evidence.