Updates

Capote roadmap after 1.0

Truco shipped. Here is what is done, what is still a maybe, and where to send feedback.

Last updated:

Capote Roadmap — After Version 1.0

Luski Game Studio has published a roadmap for Capote’s Early Access period and the post-launch window. This page tracks every confirmed item, with the status as of the most recent patch.

Roadmap status

Shipped in version 1.0 (August 20, 2026)

Still open after 1.0

  • Additional special cards. The current eleven may still grow. No dated 1.0 list of four new saboteurs was published as a locked patch note.
  • Betejack expansion. New items and bosses remain a post-launch interest, not a dated 1.0 checklist item in launch coverage.
  • Custom rules expansion. Extra toggles may still arrive; Classic already shipped a large custom-rules pass in King of the Bar.

Confirmed for post-launch

  • Free updates. All new special cards and balance changes will remain free.
  • Paid DLC. Cosmetic bundles with new voice lines and outfits. No gameplay-locked content.
  • Cloud sync improvements. Faster cross-device matchmaking and Betejack run sharing.

Stretch goals (not confirmed)

  • Tournament mode for 32-player brackets.
  • Replay system with shareable seed codes.
  • Workshop support for community special cards.

The developer has stated stretch goals will be evaluated based on community feedback after the 1.0 launch.

Timeline

  • Q4 2025 (October 23, 2025): Early Access launch
  • Q4 2025 (December 2025): King of the Bar update — voice chat fixes, custom rules, lip sync
  • Q2 2026 (estimated): Truco mode + two new characters
  • Q3 2026 (August 20, 2026): Version 1.0 — Truco, beach bar, pool, YouTube player. Early Access ended.
  • Post-launch: Paid cosmetic DLC, additional modes

These windows are subject to change based on Early Access feedback.

How the roadmap affects content

How to give feedback

The developer reads every post in:

  • The official Discord feedback channel
  • The Steam Community Hub discussion forums
  • The developer Instagram DMs
  • The Capote subreddit (community-managed)

If you want a specific feature added, the Discord feedback channel is the fastest path to the team.

What is not changing

  • The core bidding mechanic and capotado rule are locked. They will not change in any announced patch.
  • The price of the base game will not increase.
  • Achievements earned during Early Access will carry over to 1.0.

How the roadmap is shared

The roadmap is updated quarterly through the official Steam Community Hub and the developer Discord. Every confirmed feature lands here within 24 hours. Stretch goals are evaluated after the 1.0 launch based on community feedback.

What is confirmed versus proposed

Confirmed items have official press or developer statements. Stretch goals are aspirational and may or may not ship. The wiki keeps stretch goals clearly labelled so you can tell the difference.

How to influence the roadmap

The fastest path is the developer Discord feedback channel. Steam Community Hub discussions are second. The developer reads both and ships the most-requested features first. Wishlisting the game and turning on email alerts surfaces every new announcement.

Estimated release order

Based on the developer comments and the published patch cadence, the expected release order through 1.0 is: Truco mode, two new Truco characters, additional special cards, Betejack expansion, and finally the cosmetic DLC store. The order is not guaranteed but reflects what the team has shipped first in every previous patch cycle.

Cross-region play

Cross-region matchmaking is currently enabled for Casual queues. Ranked Truco, when it ships, will initially restrict matchmaking to your home region. The developer has stated that broader cross-region support is on the post-launch roadmap. The wiki will update the Modes Hub when the region rules are confirmed.

Why the wiki tracks confirmed and stretch items separately

Stretch goals are community-driven requests that the team is interested in but has not committed to. Listing them separately prevents disappointment when a feature does not ship in 1.0. The wiki will move a stretch item into the confirmed list the moment the developer mentions it in any official channel.