From Maker to Drakima Arcade

A Gynara release includes browser code, gameplay rules, content and website configuration. Publishing keeps those pieces tied to one reviewed identity.

A repeatable release process reduces mismatched code, content and caches and makes a failure traceable to one reviewed artifact.

Preparation and publication are separate

Maker's Build & Export → Publish to Arcade invokes the website-owned publishing workflow. Preparation validates content, builds the portable libraries and protected browser player, checks their exact module identities, installs deduplicated assets and verifies that the matching website runtime can admit the release.

Publication then selects the prepared release for the local website. A preparation receipt records what was checked. A changed source generation, conflicting operation or mismatched runtime must be resolved before that receipt is used.

Content hashes identify bytes; they are not an unlimited security guarantee. Publication also depends on trusted configuration, account checks and the release owner's validation.

Current Campaign 1 development policy

Only Campaign 1 is currently published for new Gynara attempts. Every development export clears prior Gynara progress and replaces the available game version. Accounts, purchases, wallets and other games are preserved. This is a development policy for the mini-campaign product, not a recommendation to erase unrelated data or future production records.

Players start fresh through Start Campaign. Flight retry remains available within the session. Earlier documentation about four simultaneously available campaigns or a Continue menu describes previous releases.

Standalone exports are a different destination

Maker can also package Windows and standalone browser builds for local review. A ZIP or a working local browser preview does not publish the protected Arcade installation. The website release path must coordinate its server-side rules and private content delivery as well.

Why this matters for future campaigns

Stable publication reduces manual copying and makes failures traceable to a specific prepared release. Campaign 2 should reuse that process while receiving its own content, access policy, performance measurements and owner acceptance. Authored content is not automatically published content.

Read the browser player, Maker, and documentation maintenance.

Implementation evidence: DrakimaCore scripts/Publish-GynaraArcade.ps1, tools/DrakimaCore.ArcadeCurrentTool, and the private release-admission owners; TheGynaraLegend docs/current/arcade-publishing.md and its Build & Export integration. Staff operating instructions are maintained separately from this public explanation.

Further reading: Maintained handbook chapter.