FD Bosses

FD Bosses

Minecraft 1.20.1 / Forge: this page documents that build and its measurements. For the separate 171-control Minecraft 1.21.1 port, see Minecraft 1.21.1 NeoForge.

Two controls for FD Bosses 3.1.0.3 (Minecraft 1.20.1) (mod id fdbosses): arena-protection, drop, sky and kinetic-field searches are skipped while the level has none to find, and a fix limits the Phase Sphere's client-side effect to your own player. Every switch checks the code it would change against the tested build; another build is left untouched with one WARN line (see How the patches are applied).

Key	Target	Side	Since	Kind
fdbosses_phase_sphere_local_only	FD Bosses 3.1.0.3 (Minecraft 1.20.1)	CLIENT	1.0.30	fix
fdbosses_spawner_presence_gate	FD Bosses 3.1.0.3 (Minecraft 1.20.1)	BOTH	1.0.30	opt

---

fdbosses_spawner_presence_gate

Since: 1.0.30 · Target: FD Bosses 3.1.0.3 (Minecraft 1.20.1) · Side: BOTH · Kind: opt

Mixins: BossEventsSpawnerGateMixin, KineticFieldGateMixin, HellscapeSkyGateMixin

FD Bosses: arena-protection, drop, sky and kinetic-field searches are skipped while the level has none to find. FD Bosses searches for its boss spawners within 100 blocks of every broken or placed block and every explosion (that is how it protects boss arenas), within 50 blocks of a player whose items drop, and every client tick at night within 30 blocks for a Malkuth spawner; on every move of a player or thrown ender pearl it looks for Chesed kinetic fields within 20 blocks. Mining with drills, quarries or area tools runs the 100-block search for every block. While the level holds no entity of the searched kind, the search can only come back empty, so it is now answered with an empty list and FD Bosses' own code runs as before on it. With a spawner or kinetic field anywhere in the level the search runs as before. Requires vanilla_entity_class_count_layer; with that switch off this one changes nothing. -Dbons_and_furious.fdbossesSpawnerPresenceGate.shadow=true runs the original next to the gate and logs any difference (for testing).

Measured: offline on FD Bosses' own listeners and Minecraft's entity search, 3,500 calls with and without the gate gave the same results (cancelled events, protected blocks, sky fade, collision shapes). Per broken block 4,361 -> 59 ns and 1,875 -> 88 bytes; per player move 1,168 -> 50 ns; per night-time client tick 1,682 -> 38 ns. With Collections Of Optimizations (tested 4.6): its options fdbosses.skipHellscapeSkyScan, skipArenaProtectionScan and skipKineticFieldCollision skip the same three searches. While any of them is on, this switch steps aside; otherwise this switch applies and leaves COO's copies out. One log line says which (since 1.0.36).

---

fdbosses_phase_sphere_local_only

Since: 1.0.30 · Target: FD Bosses 3.1.0.3 (Minecraft 1.20.1) · Side: CLIENT · Kind: fix

Mixin: PhaseSphereLocalOnlyMixin

FD Bosses: the Phase Sphere's client-side effect applies to your own player only. FD Bosses runs its Phase Sphere code for every player your client sees, but the client part of it is about your own player. While you used the Phase Sphere in multiplayer, every other player in view was given flying, no-clip and not-on-ground on your client (they could look like they float or pass through blocks), and your use timer ran once per player in view each tick instead of once. Now the client part runs only for your own player. Your player and everything the server does are unchanged.

Measured: offline on FD Bosses' own handler, 600 calls for your player, other players and server players: other players were changed in 80 of them before (the bug) and never now; your player and server players unchanged.