Docs Reference

Early Access

What the Early Access tag means in practice, what still moves under you, and how to report a problem.

Celas Studio carries an Early Access tag (visible on the splash screen and in Help ▸ About) with the notice: "This is an Early Access build. Features are in active development and may change before the 1.0 release." It is a build stage, not a licence tier, and it does not affect what you can do with the app.

What is still moving

Most of the app behaves the way this manual describes it. A few pieces exist in the build but are not fully wired up yet, and it is worth knowing about them rather than assuming they are broken on your machine specifically:

  • There is no in-app update checker. New builds reach you through Steam, the only place Celas Studio is sold, never a check from inside Celas Studio itself.
  • Preferences ▸ General has a "Send anonymous crash reports" checkbox, but sending is always the manual Send Report step in the post-crash dialog. The checkbox does not switch on automatic sending.

Project files across versions

A project file carries an internal format version alongside your artwork, so the app can tell its own files apart from anything else. Early Access is still moving quickly enough that this manual makes no promise about opening today's project files in a future release. Keep your own copies of anything you care about, the same advice this manual gives everywhere else during Early Access.

Reporting a problem

If the app crashes, it saves a report on its own: see Crash reports and privacy for exactly what that contains and how to send it. That crash dialog, on the next launch, is the built-in way to get a problem in front of the people building the app.

Help ▸ Documentation opens this manual from inside the app. Beyond the crash dialog, there is no separate in-app feedback or bug-report form in Early Access. For anything else, use the Steam store page: its discussion boards are where questions and reports land.