Changelog

1.4.0

• New: spectators can vote for the ship to leave early on Gordion. Dead players get the vanilla "Tell autopilot ship to leave early" prompt, so the last one alive is warned and the round can end. None of the vote itself was ever disabled at the Company — VoteShipToLeaveEarly, the server-side count and the warning to every player never look at the moon. The only thing hiding it is one line in HUDManager.Update, if (shipIsLeaving || !currentLevel.planetHasTime), which is also the only read of that flag anywhere in HUDManager (checked against the game's IL). A transpiler routes that single read through a check that answers differently only on Gordion while its day is running; the rest of the vanilla flow — prompt, three-second hold, vote count, "Ship leaving in one hour" and the warning — runs as shipped.
• The departure a passed vote schedules normally happens in TimeOfDayEvents, behind the same flag, so the time driver performs it through the same SetShipToLeaveOnMidnightClientRpc. A passed vote departs even when Ship leaves at end of day is off, because that is what the players asked for.
• The 90%-of-day warning no longer repeats when a warning has already gone out; vanilla checks shipLeavingAlertCalled for exactly this, and the vote's own announcement sets it.
• New [3. Time] Spectators can vote to leave, on by default. RealTime only: a vote to leave "in one hour" means nothing on a moon whose clock does not move.
• The Clock tick heartbeat from the 1.2.2 diagnostics now only logs while Clock diagnostics is on; it had been writing a line every 30 seconds for everyone.

1.3.0

• The HUD clock is on screen. Alpha was never the problem, which is why two fixes aimed at it changed nothing. The clock shares a HUD cluster with the profit quota — HUDManager.Clock.canvasGroup sits on the object named ProfitQuota — and that cluster is revealed by an Animator, in a line gated on spawnEnemiesAndScrap && planetHasTime. Gordion has neither, so the animator was never told to show and the cluster stayed scaled to nothing. Everything else had been correct all along: the diagnostic build reported alpha 1, the object active in the hierarchy, the icon set, and the text reading "07:41" and ticking up second by second — all of it invisible. The mod now sets that animator and re-checks it each frame, since vanilla's indoor logic still flips the alpha underneath, and clears it again on leaving.
• The diagnostics from 1.2.2 stay in, now off by default: [1. General] Clock diagnostics. Turn it on if the clock ever goes missing again and the log will name the link that broke.

1.2.2 — diagnostic build, not for release

The HUD clock has failed to appear twice now, after two fixes that each looked right. Both went unverified because everything in the drawing path logged through DebugMode, which is off by default. This build changes no behaviour; it only makes the failure visible.

• Clock chain: — the full state of the vanilla element on landing and again once the HUD has settled: the element and canvas group, every ancestor above it with its active flag, the canvas, the rect, the text and icon, and the time values behind them.
• Clock patches: — every mod that has patched HUDManager.SetClockVisible, SetClock, SetClockIcon, Update and TimeOfDay.SetInsideLightingDimness, by name, via Harmony.GetPatchInfo. Names the interference instead of guessing at it.
• Clock alpha at frame start: — read before this mod writes anything, which separates "never set" from "set and then cleared again between frames".
• Clock tick #N — proof the time driver is running at all, with the clock values as it goes.
• Each HUD call is now guarded on its own, so a throw in one no longer skips the alpha write that actually shows the clock, and the failure is reported once at warning level naming the step.
• New [1. General] Clock diagnostics, on by default in this build only.

1.2.1

• The ban now reads a combination's components straight off the weather object. A combination is a WeatherTweaksWeather, so its WeatherTypes is right there; going through Variables.GetFullWeatherType first added a lookup that could come back empty and silently cost the component list — and with it the only way to catch a combination whose name says nothing about what is inside it, like Combined Weathers Toolkit's "The Great Flood".
• Each component is matched by both its weather type and its name, and a component that is itself written as a combination is split again, so nothing slips through on spelling.
• With DebugMode on, each weather logs what it was found to be made of — the list the ban was actually tested against, which is what you need to see if something was expected to be caught and was not.

1.2.0

• New: Never allow, even in combinations. Switching off [Weather.Rainy] only removes plain rain — "Stormy + Rainy" is a separate weather with its own section that turns the rain on as well, and so are "Foggy + Rainy", "Eclipsed + Rainy" and the rest. Listing a weather here refuses it everywhere it can appear, by reading what each combination is actually made of rather than trusting its name. Written for rain specifically: its puddles do not render correctly at the Company, and they arrive with any combination containing it.
• Components are read from WeatherTweaks' WeatherTypes, with the weather's own name split on + and > as a fallback, so the ban still holds if WeatherTweaks is absent or its types have moved.

1.1.0

• Every weather can now be switched off on its own. Each registered weather gets its own [Weather.Name] section with Enabled and Weight, matching how MonstersGordion handles enemies. Turning one off takes it back out of Gordion's pool and touches nothing else — no other moon, no other weather.
• The single Weather weights line is gone. Setting a weight to 0 there already removed a weather, but nothing about a semicolon-separated string said so, and there was no way to keep a weight around while temporarily disabling it.
• Rain, Fog, Stormy, Flooded and Eclipsed are on by default. Dust Clouds and every combination from WeatherTweaks and Combined Weathers Toolkit are bound switched off, so installing a weather pack does not quietly change what happens at the Company.
• Upgrading: delete the old Weather weights line from the config. The new sections appear after the next launch, once the weather list exists — the same timing as WeatherRegistry's own per-weather sections.

1.0.5

• Config sections renumbered 1. General, 2. Weathers, 3. Time. The gap where a scrap section used to be looked like something had gone missing. Done now, before release, because renaming a section later would leave everyone's settings behind in the old one.

1.0.4

• Clients could have got the same weather with different numbers. WeatherRegistry syncs which weather a moon gets, but not the values behind it: every client runs RoundManager.SetToCurrentLevelWeather from its own level generation and reads weatherVariable/weatherVariable2 out of its own pool entry. On a client the pool was only being built when they joined the lobby, so anyone who missed that window would have found no Gordion entry, kept whatever those fields held before, and seen the flood at a different height and the fog at a different density than the host. The pool is now rebuilt immediately before that read, on every player, on every landing.
• Weather variables are borrowed from a vanilla moon in preference to a modded one, so host and clients settle on the same donor even when their moon mods differ.

1.0.3

• Multiplayer: every player now gets the same time of day. The day offset was being set from the local globalTime at the moment each machine noticed the landing, so host and clients each started their Gordion day from a slightly different number — different clocks, different flood levels, different progression timing. It is a flat zero now, and globalTime itself is server-synced, so the same arithmetic runs on identical inputs everywhere.
• Lightning target rescans are host-only. StormyWeather's targeting loop already returns early for anyone who is not the owner, so clients were paying for a scene-wide sweep that could only disagree with the host about what may be struck.
• The end-of-day freeze guard no longer fires when the day has genuinely run out, and reports itself once instead of every frame.
• README documents the networking model in full: what the host decides, what is computed locally from shared inputs, and what a player without the mod sees.

1.0.2

• The Gordion day froze the instant it started, and took the weather with it. TimeOfDay derives local time as (globalTime + OffsetFromGlobalTime) * DaySpeedMultiplier % (totalTime + 1) and then sets globalTimeAtEndOfDay from it; Gordion's authored offset — never meant to produce a sensible time on a moon with no day cycle — landed past the end of the day, so that value came out behind the current time and MoveGlobalTime's clamp pinned globalTime in place. The log showed it stuck at 100 every visit. The offset is now zeroed against the current global time so the visit starts at dawn with a full day ahead, and the driver re-checks each frame in case anything recomputes it. This one bug also explains the previous report of Flooded water not rising and storms never striking: the water level is globalTime / 1080 * weatherVariable2, and random thunder fires on globalTime > randomThunderTime. Neither could ever advance.
• Lightning now has targets on Gordion. StormyWeather scans for conductive items exactly once, fifteen seconds after the storm starts, and the targeting loop skips anything still in the ship. On a moon that spawns no scrap and where every metal object starts in the ship and is then carried out and sold, that single scan leaves the storm with nothing it may hit. The list is now rebuilt every few seconds while on Gordion.
• The HUD clock is asserted rather than requested. SetClockVisible only nudges HUDElement.targetAlpha, which HUDManager.Update lerps towards, so a later writer or a disabled element wins. The canvas group's alpha is now written directly, and the element re-activated if something turned it off.
• Dust Clouds is no longer in the default weather line. Existing configs keep their value — remove DustClouds@80 from Weather weights by hand, or delete the setting to pick up the new default.

1.0.1

• The mod could not load at all. The declared dependency GUID for MrovLib was mrov.MrovLib, taken from its config file name; the plugin actually registers itself as plain MrovLib, so BepInEx refused the mod with "missing dependencies" and neither the config file nor any weather ever appeared.
• Flooded water stayed at world height 0 and never rose. RoundManager.SetToCurrentLevelWeather copies weatherVariable/weatherVariable2 out of the moon's own pool entry, and FloodWeather derives its rise from globalTime / 1080 * weatherVariable2 — so the zeroes in an injected entry meant no depth and no rise. Injected entries now borrow their variables from a moon that defines the weather, which also fixes Foggy's density range collapsing to an empty span.
• The HUD clock never showed. Vanilla only touches clock visibility from TimeOfDay.SetInsideLightingDimness, reached from MoveTimeOfDay and only when sunAnimator is set, and it hides the clock whenever the player counts as indoors — which at the Company is most of the visit. The clock is now asserted from LateUpdate, indoors included, in both time modes.
• New: Ship leaves at end of day (RealTime, on by default). The whole midnight-departure branch lives in TimeOfDayEvents behind planetHasTime, so it can never fire at the Company; the mod now calls the game's own networked SetShipToLeaveOnMidnightClientRpc instead, warning at 90% of the day exactly like vanilla. Turn it off to keep departure manual.
• normalizedTimeOfDay is recomputed each frame in RealTime mode. Vanilla only updates it inside if (sunAnimator != null), and progressing weather is driven by that value.

1.0.0

• First release. Weather on 71-Gordion: the moon's empty randomWeathers pool is filled and it is removed from the Company blacklist WeatherRegistry applies to every weather by default, so rain, fog, dust, storms, floods and eclipses can all happen at the Company.
• Per-weather weights in one config line, using the same names as the section titles in mrov.WeatherRegistry.cfg — so combined and progressing weathers from WeatherTweaks and Combined Weathers Toolkit work by name too.
• Three time modes. RealTime starts the game's own clock for the visit so progressing weather and the rising Flooded water work; Simulated drives a day and the HUD clock entirely on its own timer without touching the game clock; Off keeps the moon timeless.
• planetHasTime is deliberately never changed. It is not what runs the clock — TimeOfDay.Update keys off currentDayTimeStarted — but it is what decides whether leaving burns a deadline day, whether the ship departs at midnight, whether landing late is refused, and whether the end-of-round stats screen plays. Leaving it alone keeps all of that vanilla, and keeps every other mod that identifies the Company moon by !planetHasTime working.
• The quota deadline is held at its pre-landing value while the clock runs, because TimeOfDay.MoveGlobalTime drains it regardless of moon and would otherwise cost days and move the company buying rate.
• Nothing is written to mrov.WeatherRegistry.cfg: filters and weights are changed in memory with BepInEx config saving suppressed for the duration of the write.