Kingdom Game Engine Runtime Suite

Kingdom is Tech Connector's level-authoring, asset-editing, play, and build workspace. Garden and Kingdom edit the same saved level document; Play launches an isolated runtime copy so simulation does not overwrite authoring state.

Start here

Open Tools > Kingdom (Game Engine Runtime Suite).
Open or create a level, then add actors from the toolbar or Content Browser.
Select an actor in the World Outliner or viewport and edit it with Move, Rotate, Scale, or exact Details values.
Save the level before Play when you want the runtime copy to reflect the latest authoring state.
Use Play Current Level to test, Stop to end the isolated session, and Sync Changes to refresh shared authoring data.

Learn the workspace

World Outliner shows actors in the open level and drives selection.
Level Viewport provides camera navigation, framing, selection, manipulators, snapping, duplication, deletion, undo, and redo.
Details edits the selected actor's transform, rendering state, components, and prefab overrides.
Content Browser finds project assets. Press Ctrl+Space to toggle it and Ctrl+B to reveal the selected asset.
Asset editors open dedicated tools for materials, meshes, animation, audio, world assets, UI, and build profiles.

UI feature reference

Level command bar

Edit Level in Garden opens the same authoring document in the DCC-focused workspace.
Sync Changes reconciles the shared level document after supported external edits.
Play Current Level saves or uses the saved snapshot and starts an isolated runtime copy.
Stop ends play without writing runtime transforms back into authoring state.
Package opens build-profile and target output controls.
Console shows runtime commands, messages, warnings, and errors.

World Outliner

Lists the actors in the current level and keeps selection synchronized with the viewport and Details.
Supports hierarchy, visibility, rename, duplicate, delete, and focus for supported authoring actors.
Search and type filters narrow large levels without removing actors from the document.
Source-owned DCC actors remain identifiable so ownership and editable properties are clear.

Undo / Redo operate on the shared authoring document.
Select / Move / Rotate / Scale choose the active tool.
X / Y / Z constrain supported manipulator interaction to an axis.
World / Local changes manipulator orientation.
Pivot: Object / Center Pivot chooses object pivot behavior or recenters a supported actor pivot.
Increment and snap controls set transform step size and snapping.
Camera orbit, pan, zoom, frame, and bookmarks make navigation independent of Play.

Details panel

Name renames supported level-owned actors.
Location / Rotation / Scale edit exact transform channels.
Rendering / Visible control actor display state.
Components add, remove, reorder, copy, and edit component data.
Prefab Overrides shows inherited versus instance-authored values.
Apply Actor Changes commits supported field edits to the shared level document.

Content Browser

Folder, type, collection, favorite, and text filters narrow the asset inventory.
Double-click opens the registered editor for the selected asset type.
Ctrl+B / Locate in Assets reveals a selected actor's backing asset and clears filters that hide it.
Import, create, rename, duplicate, move, delete, validate, and reference actions depend on asset maturity and ownership.
Ctrl+Space toggles the browser so the viewport can use the available height.

Asset editor shell

Properties edits authoring data; Dependencies / References shows inbound and outbound use.
Save, Undo, and Redo manage the asset document.
Compile produces supported generated data and reports errors.
Reimport updates imported source data while preserving supported editor metadata.
Validate checks required fields and references before save, play, or package.
Preview exercises the editor-specific result without claiming full runtime parity.

Status and diagnostics

The level strip shows the current path and unsaved state.
System Status reports background work, indexing, and active context.
Build, validation, import, compile, and runtime logs remain distinct so a successful step is not mistaken for the complete workflow.

Core workflows

Author a level

Add or import assets, place actors, set transforms, and configure components. Save often. Garden and Kingdom share the authoring document, so a supported level edit made in either workspace should appear in the other without creating a second level.

Test without damaging the level

Play uses a saved runtime snapshot. Runtime movement, spawning, and simulation remain isolated from the authoring document. Stop the session before resuming edits. If the runtime looks stale, save the level and launch Play again.

Edit an asset

Open an asset from Content Browser to use its dedicated editor. Review Properties, Dependencies, Validation, Preview, and Compile or Reimport where available. Registry maturity describes the intended implementation level; validate the actual runtime and target-platform result.

Package a project

Choose a Build Profile, target platform, included levels, and quality settings. Run validation before packaging and inspect the output log. A successful editor preview is not a packaging qualification.

Viewport controls

Select from the Outliner or viewport; press F to frame selection.
Use W, E, and R for Move, Rotate, and Scale.
Switch World/Local space and Object/Center pivot from the viewport toolbar.
Duplicate and Delete operate on the selected authoring actor.
Undo and Redo apply to the shared level document, not an active runtime copy.

Troubleshooting

Play does not include a change: stop, save the authoring level, and launch Play again.
An asset is missing: clear Content Browser filters, refresh inventory, and use Locate in Assets.
Garden and Kingdom differ: verify both show the same level path, then use Sync Changes.
A property is disabled: the selected asset, component, runtime state, or maturity level may not support that edit.
Packaging fails: open the validation and build logs, resolve missing references, and retry the selected profile.

Screenshots show actual Tech Connector widgets with sample labels. A screenshot or saved graph does not prove a live DCC run.