Version · Updated September 8, 2026

Version 1.0 Relic and Economy Retest Log

Review dated relic-placement, pricing and register observations while separating footage checks from a new client retest.

Quick answer

The records below recheck public footage labelled 1.0: a confirmed relic effect, a displayed price total, and a completed counter sale. They are dated source checks, not a fresh playtest or proof that every early-access rule changed.

Check the dated release record

Steam release recordDate
Early AccessNovember 19, 2025
Full releaseSeptember 2, 2026

Do not transfer a demo shop rule without checking

Digital Sun’s earlier shop discussion explicitly concerns a Steam Next Fest demo and discusses possible changes. It is useful development history, but not a current specification for pricing or shop interactions.

Go directly to the current announcement

The links below lead to the official store and developer news. Compare the relevant dated notice with the behavior on your installed platform; these sources do not establish a universal hotfix number for every storefront.

Read what was actually checked

These entries were reviewed on September 8, 2026 from retained public recordings. Footage-checked means that the stated action and result were compared in that source. It does not mean a new game session was launched or a cross-version regression test passed.

Check and source versionRecorded actionObserved resultNot tested
The Song of Welcome — video labelled 1.0, September 7, 2026Read Corner and confirm its placement beside the receiving row.Four receivers:4, 2, 6, 4→8, 6, 10, 8; Armor marks appear; the Song remains 2.Later burn protection, repeated use, or a different client build
Showcase pricing — video labelled 1.0, September 5, 2026Place the selected relic in the case and enter base price 30.Quality +15% and Total 34 are displayed.A general rounding rule or universal price for other relics
Counter sale — video labelled 1.0, September 5, 2026After an accepted offer, move to the register and complete the interaction.The tutorial wallet changes from 0 to 50.A full-day profit total, every customer type or current-platform behavior

Relic result: compare confirmation with the preview

For the recorded Song placement, inspect the receiving row before confirmation, confirm the corner position, then compare the same four Quality readings after the grid settles. This is the specific relic check documented in the log.

Four receiving relics now show Armor markings and Quality 8, 6, 10 and 8 while the Song remains at 2
The confirmed Song placement leaves its own Quality at 2 while the four other relics in its row show 8, 6, 10, 8. The change is checked against the earlier frame, not inferred from the preview alone. · Image sourceOpen full-size image ↗

Economy result: price and payment are separate checkpoints

The price panel shows the entered base digits and the resulting Total separately. The counter sequence is a separate transaction check: an accepted offer still requires the register action before the wallet changes. The two records should not be combined into a claim that the pictured 34-total relic was the tutorial 50-gold sale.

Showcase panel with selected quality-three relic, base price thirty and total thirty-four
The entered price and Total are separate fields. This example shows Quality +15%; the displayed total is 34. No rounding rule is inferred. · Image sourceOpen full-size image ↗
Customer at the counter with a smiling reaction and task to sell the relic
A favourable reaction does not itself finish the sale: the tutorial then directs the player to the counter. · Image sourceOpen full-size image ↗

Keep announced changes separate from checked behavior

The launch announcement adds Shop Level 5 with one extra Bloblet slot and one extra cosmetic placement slot. That is an announced change; the records above do not demonstrate purchasing or filling those new slots.

For your own retest, record the current build and the selected relic, repeat one action, and save both the initial and final readouts. Mark an unperformed check as pending. Preserve the earlier source record if your result differs instead of calling the difference a confirmed patch effect without a matched comparison.

Sources