One window, your server’s pages

1. Choose the frame and format

In the hub, open In-game interfaces. Choose a side menu, top menu or prebuilt interface. Select Window, then Appearance: Window format offers 16:9 or Square; Window size (%) ranges from 60 to 100. These settings apply to every page.

The frame and content follow the chosen dimensions. Contained images keep their proportions; changing format does not stretch a page screenshot. Still check long text and smaller sizes in the preview.

2. Add pages

Choose Add a page: the Content and Plugins tabs separate the available page types. Add rules, news, a FAQ or a Blank page. Select a page for its Content, Appearance and Navigation tabs. Its options include Move page up, Move page down and Set as opening page.

Blank page keeps your custom elements. In its Content tab, Edit in the CUI editor opens that same page to add text, images, buttons or component kits. Return to window keeps those edits.

3. Choose how to open it

Select Window, then Opening → Configure opening. Each command can target a specific page and have its own groups or permissions. Automatic opening waits until the player is ready after joining; reloading the plugin does not reopen the window for players already online. Business actions keep their separate authorization checks.

4. Save, download or send

The local copy stays in this browser. Save keeps the window in your account; My windows lets you resume it. These projects can be reused across servers: choosing a server neither moves nor installs them.

Download offers Editable project for continued editing, or Server installation · ZIP with the package, instructions and linked plugin configurations. Follow INSTALL.txt: back up the existing registry and merge additions by ID. Do not replace the server’s other interfaces with registry-additions.json.

Send is a separate action preceded by a file check. If the window contains linked configurations, the current workflow requires sending the complete saved project from My projects. Transfer and activation are reported separately: a download or transfer alone does not confirm activation.

Pages linked to plugins

A linked page uses an exact plugin configuration. A Starter Pack can coexist with other uses in the same Kits catalogue. Adding or removing the page does not delete kits. Third-party plugins keep their menus and commands; PimpMyCUI does not replace them implicitly.

Go further in the editor

Advanced editor opens the exact same window. Move layers or add components, then return to the window. Advanced edits that the simplified controls cannot represent are retained and never silently replaced.

Data and preview

Preview lets you try supported navigation and interactions using examples. Native data offered by a component and data supplied by a plugin differ from fixed text. Permissions, command conflicts and live data still need checking on the server.

Plugin version and videos

In the window options, Installation shows window requirements and the observed runtime state when a server is available. A loaded plugin does not prove compatibility: check the package’s minimum version and declared capabilities. The four lesson videos retain the standalone workflow and labels recorded in October 2026; they do not show every Window/Page control described here.