Core Features

A game running with the kit installed: a column of HUD buttons down the left, a row along the bottom, a cash counter, the Codes panel open in the middle and the music player at the top right — **A HUD, on the first Play**Buttons down the side, a cash counter, and panels that open one at a time so opening a second closes the first. Every pack you add puts its own button on the same rail instead of building a second one.

The Menus list in the plugin, fourteen menus with the button that opens each one, two of them marked as opened from code — **Fourteen menus, named in a list**Shop, Pets, Rebirth, Upgrades, Teleport, Codes, Rewards, Trade, Spin, Settings and the rest. Rename one, delete one, add one. The list also says which are opened by other packs from code rather than by a button.

One HUD button open in the plugin, showing its name, the menu it opens, its image, a Show in HUD toggle and its tooltip text — **A button is six fields**What it is called, what it opens, its icon, whether it shows at all, and what the tooltip says. That is the whole of adding a button to the HUD.

Setup

1Drag the .rbxm into Studio

2Hit Install in the plugin

3Name your menus and buttons. Press Play.

Developer API

Your own button actions

-- CustomHandlers, a module inside the pack.
-- Updates never overwrite this file.
return {
    Rebirth = function(button)
        -- Runs when a button whose Action attribute
        -- says "Rebirth" is clicked.
        print(button.Name, "was pressed")
    end,
}

Set a button's Action attribute to the name of an entry and the click arrives here. Opening and closing panels, prompting a game pass or a developer product, and inviting friends are already handled, so a handler of your own is only for the parts that are actually yours.

Customisation

Buttons, and which of them show

The HUD Buttons list in the plugin, twelve buttons with their icons and the menu each one opens

Twelve buttons ship, each with its icon and the menu it opens. Show in HUD hides one without deleting it, which is how you keep a menu your own code opens while taking its button off the screen.

Labels that show the player's numbers

Tag a label UI_DataBind, give it a DataPath like Stats.Cash, and it shows that value and keeps following it for the rest of the session. Prefix and Suffix add the currency symbol, and Format chooses between 52500, 52,500 and 52.5K. A counter on your HUD is a label plus three attributes, with no script behind it.

How a panel opens

An Animation attribute on the panel picks how it arrives, Bounce or SpinReveal. The same attribute on anything inside a panel makes it move instead: rotate, bob, or cycle through colours.

The small things that make it feel finished

Buttons grow slightly under the cursor and show a tooltip that follows it. Clicks and hovers play a sound. Text boxes tick as they are typed into. All of it is on by default and all of it is an attribute you can turn off, one element at a time.

Works great with

Sound System & Music Player — Sound System

None of these are required, and none of them need wiring. A pack you install brings its own panel and its own HUD button, and they take their place in the rail alongside the ones already there.

Documentation

Every tag, every attribute, the plugin panels and the version history live at rblxessentials.com/docs.

Updates

📋 Version history and changelogs for all packs are available at rblxessentials.com/docs#changelog.

General UI Kit

Core Features

Setup

Developer API

Customisation

Works great with

Documentation

Updates

The rest of the ecosystem

Plugin

Studded UI

Pet System

Datastore

Sound System

General UI Kit

General UI Kit

✨Core Features

⚙️Setup

🧩Developer API

🎨Customisation

🔗Works great with

📘Documentation

🔄Updates

The rest of the ecosystem

Plugin

Studded UI

Pet System

Datastore

Sound System

General UI Kit

Core Features

Setup

Developer API

Customisation

Works great with

Documentation

Updates