Chrono Odyssey Matrix system | public progression evidence

Use this page to track progression-system claims without inventing node math.

Current answer

The Matrix/progression page should publish source-backed mechanics only and keep unsupported build formulas out.

Use this page to track progression-system claims without inventing node math. The current evidence package treats Chrono Odyssey as pre-release. The strongest source is the Steam app record, then the official site, then dated Steam news items. That order matters because a player-facing wiki page does not convert anticipation, trailers, or search demand into exact build, recipe, route, enemy, or vehicle data.

Source list

Confirmed public facts

Steam describes the game as a next-generation action MMORPG with Unreal Engine 5 visuals, open-world exploration, action combat using time manipulation, and extensive customization.

• Action, Adventure, Massively Multiplayer, and RPG genres in Steam app details.
• Multi-player, MMO, PvP, Online PvP, Co-op, and Online Co-op categories in Steam app details.
• Full controller support and multiple PlayStation controller support categories in Steam app details.

These facts are enough to justify this page as a public watch page. They are not enough to publish final database rows where the official material has not named the entity and shown the field. That distinction is the main evidence rule for this site.

Page-specific evidence map

• The latest dated news item observed for this site is Developer's Notes #5, which makes progression notes a high-priority recheck source.
• Steam confirms customization and action combat, supporting a progression-system page at the category level.
• The checked public extracts do not provide node names, node costs, reset rules, cap values, or full progression formulas.
• A future Matrix table shows source URL, date, node label, observed effect, and whether the value came from official text or captured gameplay.

Claim status table

What players can do with this page now

Use this page as a decision filter. A player can safely learn what the public sources actually confirm, which topics deserve tracking, and which guides need a future update when launch, demo, beta, or official news data becomes more specific. If another site publishes exact values that this page does not list, compare that claim against the source ledger above before trusting it.

For matrix system evidence, the useful current action is to keep a short confirmed-so-far list instead of a final answer sheet. Save the relevant source URL, record the checked date, and write down the exact player consequence. If a source only confirms a broad system, keep the page at system level. If a source names an entity but gives no value, create a watch item. If a source names an entity and shows a value, then a table row can be considered.

Evidence needed before stronger advice

A build row needs at least one named public source for the class or system, one source for the relevant ability or gear item, and a checked date newer than the current saved evidence package. The new source needs to be public, stable enough to cite, and specific enough that a reader can verify the same claim without relying on interpretation. Screenshots or captured gameplay can help after public access exists, with separate labels from official text.

Before changing this page, collect these fields:

1. Source URL and publisher or uploader.
2. Date checked and date published if available.
3. Exact claim being added.
4. Player-facing consequence of the claim.
5. Confidence level: confirmed, supported, partial, or blocked.
6. Whether the claim affects a route, item, ability, requirement, phase, reward, price, platform, or release answer.

Unsupported claims kept out

The current sources do not support exact class comparisons, skill coefficients, gear stat rows, Matrix node values, dungeon routes, economy values, and endgame rotations. Leaving those details out is intentional. A thin but sourced page is more useful than a large table that has to be corrected after launch. This page is designed so unsupported rows can be added quickly later, but only after the source package can defend them.

Recheck sequence

1. Reopen the Steam app page and confirm the release field, developer, publisher, genres, and categories.
2. Check the official site for announcements or press updates that are newer than 2026-09-13.
3. Query the Steam News API and compare the newest title/date against this page's latest saved item.
4. If the new material changes a player decision, update the Current answer and Claim status table first.
5. If the new material only adds flavor, keep it out of gameplay advice unless it confirms a useful field.

Source links

• Steam store: Chrono Odyssey on Steam
• Official site: Chrono Odyssey official source
• Steam News API: latest public news feed
• Main hub: /
• Release status: /guides/release-status/

Quick FAQ

Is this enough evidence for final recommendations? No. It is enough for release-aware tracking and confirmed category pages, but not for final row-level recommendations.

Why does the page repeat dates and source names? Because the site is covering games that are unreleased or near release. The checked date is part of the answer.

When does this page change? Change it when Steam, the official site, a dated developer post, or public gameplay evidence provides a claim that alters a player decision.