Skip to content

0.8.35 - retrievals recorded again, who is with you, and what loot is worth - #39

Merged
peans99 merged 3 commits into
mainfrom
release/0.8.35
Aug 28, 2026
Merged

0.8.35 - retrievals recorded again, who is with you, and what loot is worth#39
peans99 merged 3 commits into
mainfrom
release/0.8.35

Conversation

@peans99

@peans99 peans99 commented Aug 28, 2026

Copy link
Copy Markdown
Owner

Integration branch for 0.8.35. Three branches, tested as one thing from
C:\QuantumWake against the real install.

What is in it

Ship retrievals are recorded again (fix/vehicle-spawning-tag)
Game build 12519617 stopped emitting SetVehicleSpawnedInformations, the line
the parser read. Nothing failed — the tag simply stopped appearing, so
! unmatched known tags stayed at 0 while every retrieval on the current build
went unrecorded. The game still writes SetVehicleSpawningInformations, and
SessionBuilder already collapsed the pair by entity id, so reading both
restores current builds without double-counting archived ones. The ASOP
[Error] twin is skipped rather than counted as a parse failure.

A Party card on Now (feat/now-party-card)
The party channel is the only place a 4.9 log names another player, and it was
read only into history. The live snapshot now carries it. Latest-wins rather
than a tally, because somebody who dropped and came back is present. Worded as
a floor throughout — a member already online when the party formed is never the
subject of a toast.

Loot says what things are worth (feat/loot-typical-price)
Median across every terminal UEX stocks the item at, not the cheapest. The two
differ tenfold on at least one item here: the MaxLift Tractor Beam is stocked
near 19,175 by ~100 terminals and at 1,975 by one. Unstocked items show a dash
and a reason rather than a zero.

Verification

check result
dotnet test Quantumwake.slnx -c Release 645 + 227 green
CLI against the 159-file corpus vehicle.spawn 35 → 152, ! unmatched known tags 0
152 cross-checked independently 35 spawned + 117 valid spawning lines
Driven against the real install party card, loot prices and retrievals all render

PayloadVersion moves 7 → 8 in the spawn fix, so existing installs re-read and
the retrieval history fills back in.

backlog-network is deliberately not included and is left untouched.

peans99 and others added 3 commits August 28, 2026 11:09
Build 12519617 stopped emitting SetVehicleSpawnedInformations, the line the
parser read to mark a ship being brought to the pad. Nothing failed: the tag
simply stopped appearing, so unmatched-known-tags stayed at 0 while every
retrieval on the current build went unrecorded.

The game still writes SetVehicleSpawningInformations, logged when the request
goes in rather than when the ship arrives, and older builds write both for one
retrieval. SessionBuilder already collapsed the pair by entity id, so reading
both restores current builds without double-counting archived ones.

The ASOP terminal also emits an [Error] twin of the request line when it cannot
resolve the landing area name, repeating an entity id already being retrieved
beside it. It is skipped rather than counted as a parse failure.

Against the 159-file corpus: vehicle.spawn 35 -> 152, matching 35 "spawned"
plus 117 valid "spawning" lines counted independently, unmatched still 0.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01C5xdyEeEFuvh5nPTGFSjnF
The party channel is the only place a 4.9 log names another player, and until
now it was read only into history: the Crew page and the session debrief. The
live snapshot carried nothing, so the Now page could not say who was with you
while you were flying with them.

Adds a Party card listing everyone the channel has named this session and the
last thing it said about each. Latest-wins rather than a tally of arrivals
against departures, because the moments are not commutative - somebody who
dropped and came back is present, and counting would score that a draw.

The reduction lives in Core's Party rather than the server: it is a question
about what the channel said, the same question the Crew page asks, and Core is
where it can be tested.

Worded as a floor throughout, permanently rather than when the list is short.
A member already online when the party formed and still there at the end is
never the subject of a toast, so absence means nothing - and a list of two is
exactly when it would be read as the whole party. The card hides rather than
showing a zero, because flying alone and flying with a silent party look
identical from here.

Nothing stored changes shape, so PayloadVersion stays where 0.8.33 put it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01C5xdyEeEFuvh5nPTGFSjnF
The Loot page listed what was picked up and where, and said nothing about
value. The join needed already existed - the stash prices items by taking the
item class to a community entry and its uuid to UEX - so this is that same hop
at the loot endpoint.

The number is the median across every terminal stocking the item, not
UexData.ItemPrice, which is documented as the cheapest. The two answer
different questions and on this install they differ tenfold: the MaxLift
Tractor Beam is stocked near 19,175 by about a hundred terminals and at 1,975
by one, so the cheapest reads as a tenth of what the thing is worth. A mean
would still be dragged by that row, which is why this is a median.

UEX stocks 64 of this install's 109 looted item classes, so 41% of the table
has no price. Those show a dash and a reason rather than a blank that reads as
worthless or a zero that reads as free, and a summary tile says how many rows
carry a price so a sparse table is explained rather than looking broken.

Nothing stored changes shape, so PayloadVersion stays where it is.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01C5xdyEeEFuvh5nPTGFSjnF
@peans99
peans99 merged commit 5576ce8 into main Aug 28, 2026
2 checks passed
peans99 added a commit that referenced this pull request Aug 28, 2026
0.8.35 - retrievals recorded again, who is with you, and what loot is worth
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant