Vox Seas Hub

Update log · maintained by observation

Vox Seas update log

Official Vox Seas updates almost daily and publishes no patch notes.Roblox’s API exposes one “updated” timestamp, and the developer’s Trello board moves without announcements — so this log is built by observation: dated reads of both, recorded move by move, with nothing inferred into the gaps.

01

The log, newest first

Two kinds of events live here, and keeping them separate is the point: client updates (the game itself changed — what the API timestamp proves) and board moves(the developer’s documentation changed — what our board reads prove). A board reorganization without a client patch is not patch notes; treating one as the other is how rumor-grade wikis get built.

NOVEMBER EVENT RAIL · DATED OBSERVATIONS11-14Relaunch11-17Code batch ×311-18Client patch ×211-19Board reorgRelaunch (±1 day, community) · code batch (community) · client patches (official API) · board moves (official board reads)
Drawn for this site from the log below — one rail, four dated observations, each kind graded by how we know it.
  1. Official

    The official Trello board was reorganized mid-day: ten level-tagged bosses (Lvl 375-1100) left the board, five masked "???" raid cards appeared, three game passes (Abyssal Blade, 2x Money, 2x Drop) and five island entries (including the Sky Lands and Fountain endgame zones) were removed, and the "Vox Fruits" roster stayed at 16.

    • · Board card count dropped from 587 (13:05 read) to 389 (14:02 read, stable across two consecutive fetches).
    • · Boss list changes: Vice Admiral, Valion Ironmaul, Koaby, Muzzlejaw, Admiral Vulkan, Lord Triton, Wsyper, Abandoned Experiment, EX-77 Ironfist and Wandering Soul removed; Raid Bosses now carries sword-named cards (Tenrai, Golden Rapier, Azure Glaive) plus five "???" placeholders.
    • · Island changes: Sky Lands Upper (775-925), Fountain (925-1100), Air jump Island, Shipwreck and Drowned Fleet removed; the progression ladder now ends at Vulcan Island / Ashforge Bastion (415-450).
    • · No client update was observed on the game itself during this window (the API 'updated' timestamp did not move); this is board-side restructuring, not a shipped patch — which is why it is logged rather than treated as patch notes.
  2. Official

    Two updates shipped on 2026-11-18 (observed 11:13Z, then 17:38Z).

    • · The official API 'updated' timestamp moved twice within one day: first snapshot of the day read 2026-11-18T11:13:55Z, the evening read 2026-11-18T17:38:55Z (observed by the site's own API sampling).
    • · Content of the patches is not published anywhere we can verify; no patch notes are claimed here.
  3. Community

    A new code batch surfaced: Patch2Reset and Release2026 were marked NEW by two independent code pages on 2026-11-17.

    • · Patch2Reset (1 Stat Reset Token) and Release2026 (1 hour Double XP) marked NEW on 2026-11-17 by Eurogamer and the Vox Seas wiki.
    • · PatchReset (1 Stat Reset Token) also listed active across sources.
  4. Community

    The game relaunched as "Dawn of Legends" (±1 day), restarting its public ecosystem after an earlier takedown-and-renaming period.

    • · Relaunch date inferred from official update timestamps and multi-source coverage; no single official announcement was captured, so the site always carries the ±1 day caveat.
    • · The relaunch issued a fresh code batch; codes from the 2025 Blox Seas era no longer work.

02

Why a dated log beats a one-line answer

Every competitor site answers “when did the game last update” with a sentence written once and never revised. The infrastructure for doing better is public and cheap: the games API returns a millisecond-precision timestamp on every read, and the Trello board exports its full state as JSON to anyone who asks. The only cost is showing up and reading both on a schedule — which is also the only thing nobody else is doing.

The method has one honest limitation worth stating: a timestamp proves something changed, not what changed. Where the board’s before-and-after reads tell us exactly what moved (like the 2026-11-19 reorganization), the log says so item by item. Where only the client timestamp moved and no notes exist anywhere, the entry says exactly that much and stops — inventing patch contents would be the one thing that permanently discredits this page.

What changed for you, practically

Log entries connect to the pages they touch: a code batch lands → the codes matrix re-checks; a boss leaves the board → the roster updates with a flux note; the ladder ends at 450 → the island table says so. The log is the index of site changes; those pages are the content.

03

Code batches follow patches — track them together

The one reliable pattern in the data so far: code batches surface within a day of patches. The 2026-11-17 batch (Patch2Reset, Release2026, PatchReset) appeared the day before the double update on the 18th, and the relaunch batch landed with Dawn of Legends itself on the 14th. No batch appeared after the 2026-11-19 board reorganization — consistent with it being documentation work, not a shipped patch.

Practically, that makes the 24 hours after any client timestamp move the highest-value window for the codes page: a new string usually appears on Discord or the board first and gets picked up by code sites within a day. Our rule stands regardless — a code enters the active table only when two independent sources list it, so early reports land in the disclosure zone first.

The reverse connection matters too: codes die with patches. The relaunch killed every 2025-era string overnight, and any patch can rotate the current batch. If a code on the matrix stopped working after an update, the fastest fix is a dead-code report with the date you tried it — reports move codes to the expired table with your date recorded.

04

Known unknowns — what this log deliberately does not claim

Three things the data cannot say yet, stated plainly so the gap is visible rather than invisible. Patch contents: the API timestamp proves a client change shipped on 2026-11-18 twice, but nothing public describes what either patch touched — no notes exist on the board, in the Discord announcement channels we can read without joining, or on any source we can verify. Endgame scope: the board currently ends the ladder at 450 while five masked raid cards sit in staging, so the shape of the next content drop is a guess we refuse to print. Player impact: CCU moves with time of day; comparing two snapshots taken at different hours proves nothing about the trend.

Each unknown gets resolved the same way the log is built: a new dated read, a new line, and a page update if the answer changes something players act on. That cadence — not confident-sounding filler — is what makes a log worth checking after every patch.

05

Frequently asked questions

When did Vox Seas last update?

The last client update we observed was 2026-11-18, which shipped twice in one day (the API's updated timestamp moved from 11:13Z to 17:38Z). The developer also reorganized the official Trello board on 2026-11-19 without shipping a patch — board moves and client updates are logged separately here.

How does this update log work when the game publishes no patch notes?

Roblox's API exposes one 'updated' timestamp per game, so the log is built from timestamped observations: each entry records what the API said at a known time plus what changed on the official board between reads. We log moves and dates; we do not invent patch contents.

Why did bosses and islands disappear from the Trello board on 2026-11-19?

The developer reorganized the board that day: ten level-tagged bosses, the endgame islands (Sky Lands Upper, Fountain), three special islands and three game passes came off the board, while five masked "???" raid cards appeared. The reasonable read is endgame content being rebuilt ahead of a patch.

Do updates bring new codes?

Code batches have followed patches so far — the 2026-11-17 batch (Patch2Reset, Release2026, PatchReset) surfaced a day before the double update. The codes page tracks each batch with per-source status and is re-checked after every patch.