VizzyCode Wiki Dashboard

VizzyCode is a Windows Forms, CLI, VS Code, and Juno live-bridge toolkit for converting and editing Vizzy programs from Juno: New Origins. This vault documents architecture, workflows, conversion fidelity, validation, raw preservation, live craft data, AI context, and troubleshooting. vizzycode dashboard

Start here

Use this page to choose the correct workflow: imported XML fidelity, new .vizzy.cs authoring, live Juno bridge work, VS Code integration, or AI-assisted repair.

Keep the workflow explicit

XML -> code -> XML and code -> XML are different success criteria. Decide which one applies before editing a mission-scale file.

Fast route

For practical work, start with 13 - Recommended Workflows, then use 04 - Export Validation, 05 - Raw Preservation, and 14 - Troubleshooting as needed.

AreaNoteUse it for
Home00 - HomeDashboard, Dataview panels, quick links
Architecture01 - Project ArchitectureComponent map, project layout, build commands
Component mapComponent MapScript-by-script project documentation
Converter02 - Conversion Engine (VizzyXmlConverter)XML/code conversion, anchors, sidecar, Raw preservation
CLI03 - CLI (VizzyCode.Cli)Import, export, roundtrip, raw encode/decode
Validation04 - Export ValidationJuno-safe structural checks
Raw preservation05 - Raw PreservationRaw*, RawXml*, base64 payloads, exact XML fragments
Live bridge06 - Juno Live BridgeLocal HTTP bridge, endpoints, telemetry, snapshots
VS Code07 - VS Code ExtensionCommands, installation, generated artifacts
AI08 - AI IntegrationProvider commands, context bundles, repair prompts
Juno mod09 - Juno Mod (Mod Assets)Unity-side HTTP server and craft data
Authoring10 - Vizzy Authoring GuideSafe .vizzy.cs syntax and unsafe patterns
Blocks11 - Vizzy Blocks ReferenceVizzy block families and special cases
Examples12 - Project ExamplesImported examples and sidecar pairs
Workflows13 - Recommended WorkflowsRecommended step-by-step processes
Troubleshooting14 - TroubleshootingFailure causes and fixes
Script catalogScript CatalogDataview catalog of component notes
TagsTag CatalogDataview tag catalog
Tag taxonomyTag TaxonomyCanonical tags for Tag Wrangler
Graph guideGraph View GuideRules for keeping Graph View clean
Plugin workflowsObsidian Plugin WorkflowsAdvanced Tables, Dataview, Tag Wrangler usage
TemplateComponent TemplateComponent note template

Section Map

Core conversion

01 - Project Architecture explains the component tree. 02 - Conversion Engine (VizzyXmlConverter) explains the conversion engine, clean view, sidecars, and preservation anchors.

Daily workflow

Use 03 - CLI (VizzyCode.Cli) for repeatable commands and 13 - Recommended Workflows for checklists that avoid mixing fidelity and authoring concerns.

Validation and exactness

04 - Export Validation blocks known invalid XML shapes. 05 - Raw Preservation explains exact XML fragments and when readable raw XML is preferable to rewriting.

Live game work

06 - Juno Live Bridge and 09 - Juno Mod (Mod Assets) document the local bridge at 127.0.0.1:7842.

Recovery path

If Juno does not show a generated program, go to Juno Does Not Load The XML and follow the validation, sidecar, and source-of-truth checks.

Wiki Catalog

TABLE type AS "Type", status AS "Status", file.tags AS "Tags"
FROM "VizzyCode"
SORT file.name ASC

Open Tasks

TASK
FROM "VizzyCode"
WHERE !completed
SORT file.name ASC

Critical Concepts

ConceptShort definitionDeep dive
.vizzy.csC#-style DSL used by VizzyCode. It is not normal project C#.10 - Vizzy Authoring Guide
.vizzy.meta.jsonSidecar that stores hidden fidelity metadata for clean-view imports.02 - Conversion Engine (VizzyXmlConverter)
VZTOPBLOCKPreservation marker for a top-level imported block.02 - Conversion Engine (VizzyXmlConverter)
VZBLOCKBase64 metadata marker for a top-level imported header.02 - Conversion Engine (VizzyXmlConverter)
VZELBase64 metadata marker for an imported element.02 - Conversion Engine (VizzyXmlConverter)
RawXml*Readable escape hatch for exact XML fragments.05 - Raw Preservation
VZPOSLayout hint for top-level blocks in Juno.02 - Conversion Engine (VizzyXmlConverter)
Export validationStructural gate before saving XML.04 - Export Validation

Primary Workflow Map

flowchart TD
    A[Need to edit Vizzy] --> B{Source of truth}
    B -->|Original Juno XML| C[Imported fidelity workflow]
    B -->|New script| D[Authoring workflow]
    B -->|Running craft| E[Juno live bridge workflow]
    C --> F[[13 - Recommended Workflows#workflow-a-existing-juno-xml|Workflow A Existing Juno XML]]
    D --> G[[13 - Recommended Workflows#workflow-b-new-script-from-scratch|Workflow B New Script From Scratch]]
    E --> H[[06 - Juno Live Bridge]]
    F --> I[[04 - Export Validation]]
    G --> I
    H --> I

Quick Commands

Build desktop app

dotnet build VizzyCode.csproj -c Release

Import XML

dotnet run --project VizzyCode.Cli\VizzyCode.Cli.csproj -- import "input.xml" -o "output.vizzy.cs"

Export with validation

dotnet run --project VizzyCode.Cli\VizzyCode.Cli.csproj -- export "input.vizzy.cs" -o "output.xml"
Recommended reading order
  1. 01 - Project Architecture
  2. 10 - Vizzy Authoring Guide
  3. 11 - Vizzy Blocks Reference
  4. 02 - Conversion Engine (VizzyXmlConverter)
  5. 04 - Export Validation
  6. 05 - Raw Preservation
  7. 06 - Juno Live Bridge
  8. 08 - AI Integration
  9. 14 - Troubleshooting

Related overview notes: 01 - Project Architecture, 03 - CLI (VizzyCode.Cli), 07 - VS Code Extension, 08 - AI Integration, 13 - Recommended Workflows.