MASS4 

A GPU accelerated immediate mode GUI system built on SkiaSharp. Provides high-performance rendering with modern graphics APIs support.

Shared metadata for forms, editor tools, stable type identity and service discovery. No GUI, Gaya or Turian dependency.

A ready-to-use set of default Guinevere controls: buttons, inputs, tabs, tree, menu bar, flyout, popup, docking and more, built on the Guinevere core engine.

Drives a Guinevere UI from code or from a JSON script: injected pointer and keyboard input replayed against a real frame loop, for tests, debugging and headless automation.

Vulkan via SilkNET integration for Guinevere

OpenGL via OpenTK integration for Guinevere

A GUI-free form model: reflects plain C# objects into sections of editable fields, collections and actions, driven by MASS4.Attributes. Persistence, null rules and failure reporting are supplied by the... More information

OpenGL via SilkNET integration for Guinevere

OpenGL via Raylib integration for Guinevere

Draws Autoformers models with Excalibur controls: labelled rows, collections, nested objects and scoped, disposable drawer registries. Styled through inherited Guinevere control tokens.

PanGui-compatible .pss stylesheets for Guinevere: selectors, nesting, inheritance, layered tokens, reloadable theme files and a cached resolver behind gui.StyledNode and gui.ResolveStyle.

SVG icons for Guinevere through Svg.Skia: decoded once into reusable vector pictures that scale crisply at any size, drawn with gui.Icon and usable as src in .pss icon themes.

Reader and writer for Open Asset Package (.oap) 1.1, a random-access, streamable asset container.

Managed KTX2 reader and writer for GPU-ready textures: RGBA8, BC1-7, ASTC and ETC2, no supercompression, no native dependency.

Brick manifests, sources, resolution, lock files, registries and the machine-wide brick store shared by Gaya hosts, Turian and the asset store. No UI; shared presentation metadata comes from MASS4.Attributes.

Gameplay and editor metadata for Turian components and assets, with no engine dependency.

UI-independent metadata for Gaya settings and contributions.

The Turian engine runtime API that game code and bricks compile against, with its component source generator.

The Gaya plugin contract: IPlugin, the plugin context and the panel, command, menu, key-binding and chrome registries a plugin contributes through. The only assembly a Gaya plugin needs to reference.

Opaque stable identities, rename maps and identity registries shared by the MASS4 engine, graphs and data assets.