From ce554684983908bcb12e5e82450db291c20054d6 Mon Sep 17 00:00:00 2001 From: Tim Date: Fri, 14 Aug 2026 21:16:08 -0400 Subject: [PATCH] Enable flight so Ad Astra works in space Stepping out of the ship on the Moon kicked players with "Flying is not enabled on this server". ALLOW_FLIGHT was false, and the comment on it said to keep it that way. That advice predated space travel and is now wrong, so it is rewritten rather than left to contradict the setting. The name misleads. This does not grant anyone the ability to fly. It controls whether the server kicks a survival player for staying airborne longer than vanilla expects. Ad Astra's low gravity, jetpacks and rocket flight all look exactly like that to the check, so with it false the mod is unusable for its entire purpose. Players still cannot fly at will: flight needs creative mode, an elytra, or a jetpack they had to build. What is genuinely given up, stated plainly rather than buried: the vanilla airborne kick was the last automatic fly-hack check on this server, because the anticheat was uninstalled on 2026-08-02 after it kicked a whitelisted player for opening a door. A modified client could now fly unnoticed. Accepted deliberately. The whitelist is enforced, every player is a verified Microsoft account, PvP is off, and the population is five known family members, so there is no untrusted player for the check to defend against. PrismProtect still records every block change against the player who made it, so anything done while flying stays attributable and reversible. That is a better trade than a control that reliably kicks children out of a space mod installed on purpose. Revisit if this server ever opens beyond the family. --- docker-compose.yml | 27 ++++++++++++++++++++++----- 1 file changed, 22 insertions(+), 5 deletions(-) diff --git a/docker-compose.yml b/docker-compose.yml index 27813e2..3337d6e 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -186,11 +186,28 @@ services: # who made it and can roll it back. # If world spawn is ever moved somewhere public, reconsider this. SPAWN_PROTECTION: "0" - # false = vanilla kicks a player who stays airborne too long. This is now - # the ONLY fly control: the comment here used to credit MythicalAC, which - # was uninstalled 2026-08-02, so the anticheat it referred to no longer - # exists. Keep this false. - ALLOW_FLIGHT: "false" + # true since 2026-08-14, required by Ad Astra. It was false, and the + # comment here said to keep it that way; that advice predated space + # travel and is now wrong. + # What this setting actually does is narrow, and the name misleads: + # it does NOT grant anyone the ability to fly. It controls whether the + # server KICKS a survival player for being airborne longer than vanilla + # expects ("Flying is not enabled on this server"). Ad Astra's low + # gravity, jetpacks and rocket flight all look exactly like that to the + # check, so with it false, stepping out of the ship on the Moon kicks you. + # Players still cannot fly at will. Flight still requires creative mode, + # an elytra, or an Ad Astra jetpack they had to build. + # What is genuinely given up: the vanilla airborne kick was the last + # automatic fly-hack check on this server, since the anticheat was + # uninstalled on 2026-08-02. A modified client could now fly unnoticed. + # Accepted deliberately: the whitelist is enforced, every player is a + # verified Microsoft account, PvP is off, and the population is five + # known family members. PrismProtect still logs every block change with + # the player who made it, so anything done while flying is attributable + # and reversible. That is a better fit than a check that reliably kicks + # children out of a space mod we installed on purpose. + # If this ever opens to players outside the family, revisit it. + ALLOW_FLIGHT: "true" MAX_PLAYERS: "20" ONLINE_MODE: "TRUE" # Java accounts only (blocks cracked/anonymous clients)