Cast n Chill Roadmap: Released and Planned Status

The cast n chill roadmap is a dated planning source, not a guarantee. The collected official roadmap lists Autumnwood Lake as released in Fall 2025 and Lake Hunkerdown as released in Winter 2026, while cabin, vibration, possible local co-op, DLC maps, weather, and console or mobile ideas require status reconciliation with newer official announcements.

Status model

Read every roadmap item through a dated status label

Released means a newer official announcement or current official page confirms that the item shipped. Planned means the official roadmap names the item without newer release confirmation. In progress or unclear means official material mentions the idea but does not establish a final state. Archived or superseded means an older roadmap description conflicts with newer official release evidence or has been replaced by a later presentation.

These labels prevent a planning page from becoming an undated promise list. Every row should retain the source date and the date on which its status was checked. When evidence changes, update the status without erasing the earlier context that explains the change.

The roadmap itself may not be the newest official source. Steam Community can surface newer official announcements, while the current store or game page can show features that an older plan still describes as future.

Roadmap release labels

Preserve Autumnwood Lake and Lake Hunkerdown as dated releases

The official roadmap lists Autumnwood Lake as released in Fall 2025 and Lake Hunkerdown as released in Winter 2026. Those are official dated status statements from the roadmap source. This page does not invent exact calendar days when the research does not supply them.

Released status should still be compared with the current game and announcement history before adding map-specific fish, locations, or features elsewhere in the wiki. A map release does not automatically verify every community row that mentions it.

Old Moose Cabin illustrates the need for reconciliation. The roadmap contains a time-sensitive Cozy Cabin entry, while the Steam Community hub exposes a newer official Old Moose Cabin update announcement. The newer announcement supports current feature context and may supersede an older future-facing label.

No invented deadlines

Keep DLC, weather, local co-op, and platform plans conditional

The roadmap research identifies DLC maps, weather, possible local co-op, vibration, and console or mobile planning with different statuses. None of those categories should receive a precise release date unless a newer official announcement names one. “Planned” does not mean funded, certified, submitted, or guaranteed.

Generic console planning must not be converted into PS5 or Xbox availability. The dedicated platform pages record that no official PS5 or Xbox release was confirmed in the collected publisher and press-kit sources. A mobile idea likewise does not identify operating systems, stores, business model, controls, or timing.

Local co-op language requires special care because the official product presentation also mentions co-op broadly. A roadmap possibility does not establish the exact current local or online implementation on each platform. Verify the current listing and build before changing the status.

Source priority

Compare older roadmap entries with newer official announcements

When two official sources disagree, prefer the source that is newer and more specific to the release state. A dated announcement that says an update shipped is stronger release evidence than an older roadmap card that says the feature is coming. Preserve both URLs and dates so the status change remains auditable.

Steam Community contains player discussions as well as official announcements. The provenance label must identify which kind of item supports the claim. A player thread asking about a bug can identify a support need but cannot prove that a roadmap feature released.

Current store copy can confirm that a feature is included in product presentation, but it may not explain release history. Use announcements for chronology, the current page for present positioning, and the roadmap for dated planning intent.

Keeping the tracker current

Use official feedback routes and record every status check

The official publisher homepage provides contact or feedback context. The research did not confirm an official Discord link, so this page does not invent one. Players should use official routes that are actually published and avoid sending account or authentication information through unverified communities.

A roadmap review should check the roadmap page, latest official Steam announcements, current game page, and relevant platform store. Record the check date even when nothing changes. An unchanged status is still a dated observation.

When a new item ships, update related pages only after the feature-specific evidence is available. A release announcement may confirm existence without supplying fish data, unlock conditions, prices, or mechanic details.

Roadmap FAQ

Understand what an official plan can and cannot promise

Auditable tracking

Record each roadmap row with source date and status date

A useful row names the feature, paraphrases the official wording, links the roadmap or announcement, records the source publication date when available, assigns one controlled status, and records when that status was last checked. Add a note when a newer announcement supersedes an older plan.

Do not merge several ideas into one row when they may ship independently. Weather, DLC maps, local co-op, vibration, console plans, and mobile plans each need their own evidence and state. A release in one category does not advance the others.

If a date passes without confirmation, change the row to unclear or archived according to the available evidence rather than inventing a delay reason. Only an official source can explain a new schedule.

A visible last-checked date keeps silence from looking like a new promise.