Why DrakimaCore separates the public site and Studio
PublicWeb serves members, StudioWeb owns staff authoring, and Workers runs background jobs. Shared contracts connect them without merging their permissions.
WHY & HOW // DRAKIMACORE
Engineering Knowledgebase
Explore the software behind Drakima and The Gynara Legend: characters, creative tools, a custom game engine and the journey from authoring to the web.
17Topics
17Diagrams
17Examples
START HERE // CURRENT DEVELOPER REFERENCE
Understand Drakima and The Gynara Legend
Follow the current handbook through website architecture, Legend Maker, shared game rules, artwork, audio and browser publication. Each guide identifies its implementation owners and current limits.
EDITORIAL KNOWLEDGEBASE
Published feature notes
17 topics
The Gynara game platform
How the custom engine, WPF Maker, desktop game and WebAssembly player share rules.
Making a campaign in Legend Maker
Rooms, typed events, sprite slots, optional route generation and campaign composition.
Campaign 1: challenge and readable combat
How attack commitment, shields, missiles and impact feedback support deliberate play.
From artwork and speech to game assets
Stable identities, sprite preparation, separate audio roles and reviewed asset provenance.
A shared C# game in the browser
WebAssembly, media ownership, direct intro entry and protected Arcade sessions.
From Maker to Drakima Arcade
Checked artifacts, pinned releases and the current mini-campaign publication policy.
The technologies behind the Gynara universe
C#, ASP.NET Core, PostgreSQL, browser modules and local AI each have a defined role in bringing Drakima's characters and creative work together.
How Akari finds answers about Drakima
Site-wide Akari uses the current page and approved audience-filtered sources. Her guide workflow remains separate from private Gynoid identities.
How each Gynoid keeps her voice through a complete reply
All ChatterBox surfaces use the shared synthesis provider, retaining the selected character reference and language while rendering complete speech.
How scripted stories and AI conversations fit together
Authored scenes control the story route. Optional AI moments respond within the established scene before returning to the retained story.
How Drakima VN Maker organizes authoring
VN Maker connects project identity, story, scenes, presentation, playtesting and publication while preserving exact retained releases.
How content reaches the public website
Canonical editors own catalog records. Explicit review, publication and audience checks decide what members and Akari can discover.
Why credits and ownership are separate
Permanent content access, hosted AI usage and generated speech have separate records. Stable operation keys keep retries from charging twice.
How private rooms combine conversation and reactions
Account-owned rooms combine the selected character identity, complete conversation history, authored reactions, scenery and optional speech.
How Gynoids discuss music videos and their lore
Published video descriptions connect cast, lore and linked lyrics so tagged Gynoids can discuss the actual work with members.
Drakima Arcade: mini campaigns and account access
Campaign 1 starts fresh, enters its intro directly and offers session-only flight retry. Account ownership stays separate from gameplay progress.
No topics match the current filters.
Research and earlier designs (1)
These notes describe proposals or earlier designs. They do not establish how the current website works.
- From software characters toward physical Gynoids Experimental
