test(construction): measure start-zone building capacity (21.1, #92) - #100
Merged
Conversation
Sprint 21 package 21.1 (issue #92, D-108): the reported tightness of the build zone gets a number before any value changes. Two lanes keep it honest: a real-system lane drives ValidatePlacement + PlaceCompletedBuilding at the current constant, and a geometric model must reproduce that lane cell-for-cell before its variant numbers count. Result for the canonical HQ anchor zone (uniform 3x3 footprints, Power plants as the yardstick): 15 buildings at MinimumBuildingDistanceCells = 2, 23 at 1, and 23 at 0 — footprint occupancy already forbids every sub-1 configuration, so the only effective lever would be 2 -> 1. Both constants stay unchanged per the corrected D-108; the 15 are a lower bound for the opening zone, not a cap, since every anchor pushes the boundary outward. Also rewrites the BuildInfluenceRadiusCells docstring to name the anchor roles (HQ, Storage, Power — D-104) instead of the ambiguous "an own construction anchor" that fed the D-108 misreading. The corrected D-108 rule change (every own completed building becomes an anchor) is a separate PR and deliberately not implemented here.
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
1 participant
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.
Was
Paket 21.1 aus Sprint 21 (#92, korrigierte D-108), zwei Lieferungen:
tools/Nova.SimRunner.Tests/BuildZoneCapacityTests.csbeziffert die Kapazität der kanonischen Startzone in zwei Spuren: eine echte Systemspur überValidatePlacement+PlaceCompletedBuildingam unveränderten System, und ein parametrisiertes Geometriemodell, das die Systemspur beim geltenden Wert Zelle für Zelle reproduzieren muss, bevor seine Variantenzahlen zählen.BuildInfluenceRadiusCellsnennt jetzt die Ankerrollen (HQ, Lager, Kraftwerk, D-104) statt des mehrdeutigen „an own construction anchor", das die Fehlprämisse der ursprünglichen D-108-Fassung gespeist hat. Reine Dokumentation, kein Verhalten.Warum
Der Testbericht T-01 meldete, der Bauplatz sei „nach einigen Kraftwerken relativ schnell ausgeschöpft". Die Messung (kanonische Startlage: HQ (4,4), alle fünf Felder, einheitlicher 3×3-Footprint, Kraftwerke als Maßstab):
MinimumBuildingDistanceCellsDie 15 sind eine untere Schranke für die Anfangszone, keine Kapazitätsgrenze: Kraftwerke sind heute schon Anker und schieben die Grenze mit. Die gemeldete Enge ist damit kein Abstandsproblem — Sichtbarkeit (21.4) ist die Antwort, nicht der Wert.
Entscheidungen (Inhaber, korrigierte D-108)
Betroffene Bereiche
tools/Nova.SimRunner.Tests/BuildZoneCapacityTests.cs(neu)Assets/_Project/Scripts/Simulation/Construction/ConstructionSystem.cs(nur Docstring)CHANGELOG.md(eine Zeile unter[Unreleased], an die bestehende 21.1-Messungszeile angehängt)Nachweis
dotnet test tools/Nova.SimRunner.Tests -c Releaselokal: 725/725 grün (~15 s, Repo-SDK 8.0.318), Stand nach Rebase aufe650864.