Repository navigation
Gateway 0.7.11: a route to the Gateway from every planet, with the planets on a ring around it - #423
Merged
Merged
Conversation
…a spoke from every planet
…ub_<planet>, capture with the pack mods
…oduction profile; docs describe a route from every planet
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Gateway 0.7.11: a platform at any server's planet can now fly to the Gateway. In 0.7.10 the only route to the Gateway was from Nauvis, and planet policy locks Nauvis on servers whose planet is something else, so platforms on those servers got
no_path.What changes
surfexp_gateway_link_hub_<planet>; Nauvis keepssurfexp_gateway_link_hub, now drawn as a line). Hidden planets such asmaraxsis-trenchand outer locations such as the Shattered Planet get none and keep only their existing routes.surfexp-ring-layout, on by default: planets sit evenly on a ring around the Gateway in their original angular order. The radius grows with the planet count (minimum 12). Moons (PlanetsLiborbit.parentother than the star) keep their offset from their planet. With the setting off, positions are unchanged and the routes still exist.client run ... --pack-mods yesloads the other mod zips fromdocker/seed-data/mods. The starmap scenario puts a platform at Fulgora scheduled to the Gateway and records its state.check-gateway-map.mjsderives the hub planets from the route names and requires Nauvis.vm.json, the production-profile pins and the artifact test pin 0.7.11 (sha1e938514aaf7c44745ed13a236a092b33c051a5b1). The two doc passages that said "connected to Nauvis" now describe the route from every planet.Evidence
waiting_for_departureat 120 s and 300 s (control with only the 0.7.10 Nauvis route:no_path). Pack spokes: aquilo, fulgora, gleba, maraxsis, nauvis, vulcanus.Release order
Publish 0.7.11 to the Mod Portal before reconciling pve7, so clients can download the version the pack requires:
Checks at 115b205
run-lua-tests.ps1: 278 PASS, 0 FAIL (includestests/mods/gateway-layout.lua: ring, ring off, layout, backdrop, eclipse)build-plugin.ps1 lint: OKnode --test "tests/**/*.test.mjs": 898 pass, 0 fail, 21 skippedcheck-pr-scope.ps1 -Base main: PASS