Quartz UI pages
Private preview · 0.57.0-devView Markdown
On this page

Quartz UI overview and availability

Quartz UI renders project-owned HTML, CSS and JavaScript inside Unreal Engine and connects the page to native game code through explicit state, event and request contracts. A retained UI shell belongs to an exact local player. Blueprint and C++ publish presentation data; native game code remains responsible for gameplay decisions.

Quartz UI is a private preview. The installation guide is for developers who already have authorized repository access. The inspected descriptor calls the plugin QuartzUI, version 0.57.0-dev, with IsBetaVersion=true. Use the public name Quartz UI in prose and keep exact identifiers in paths and code. No public download, purchase, license-key or activation procedure is established by this guide.

Start with installation and first rendered UI, then consult the source-defined integration surfaces below. Read debugging before using DevTools and version notes before comparing results from different checkouts.

What the first run demonstrates

The private standalone host opens an engine Entry map and automatically renders the included reference menu during Play In Editor (PIE). Expected controls include PLAY MULTIPLAYER, SERVERS and SHOP. The native log reports protocol and application readiness. The page is served from https://reference.quartzui.test/index.html through the plugin resource loader; it is not a public website or a DNS setup step.

The reference is a frozen compatibility fixture with prebuilt web assets. It demonstrates rendering and bridge startup. It does not provide a multiplayer backend, inventory service or a game’s gameplay providers. An optional demo request can report bridge.endpoint-not-found even while this fixture renders successfully.

Choose the right integration surface

NeedSource-defined surface
One retained game UI per local playerUQuartzUISubsystem shell, UQuartzUIBlueprintLibrary, FQuartzUI
Values, notifications and named actionsSimple Blueprint nodes and the exact-player C++ facade
Typed project data and commandsUQuartzUIProvider, provider sets, project contracts and UQuartzUITypedEndpoint
An embedded or additional viewUQuartzUIWidget / UQuartzUIView; advanced ownership and lifecycle work
Web state and requestsResources/Client/quartzui.mjs
React state subscriptionResources/Client/react.mjs; the consuming app supplies React

A successful browser preview alone does not establish Unreal input, bridge readiness or packaged operation. The installation recipe uses earlier independent host execution evidence. A subsequent independent documentation review verified source and reused-checkout integrity; it did not repeat the Editor build or render.

Availability and evidence boundary

The reference-host baseline is 91fd772c282098157c4e7cded0263844f076e9fb, pinned to plugin 933db5171161ac5966e3b9bca3fd3a965f5399cc. Earlier independent testing passed its build, resource audit, reference rendering and readiness, but native DevTools attachment failed. Plugin e7ab5dcc0069ade3393cc0e033e4541a78eaae3b is a separate repair candidate with scoped selector evidence; this documentation does not present it as the reference host’s pin or a release.

The independent documentation review found that the custom integration snippets lack a complete app-registration, frontend-build and observable native-action fixture. They have not been compiled or executed together in Unreal. The reference menu remains the documented first-render target. Packaging, clean-machine provisioning and broader platform/engine support are unverified; see version notes.