Live Configuration
Configure in game, not in Studio¶
Virtually everything in HD Admin except command code can be configured live in game from the panel: roles, game settings, personal settings, bans and running tasks. Changes save automatically and sync to every running server, typically within seconds. There's no republishing and no shutting down servers.
The few things that still need Studio are the ones made of code: command modules, custom arguments, theme modules, tools and the static ban list.
Game settings¶
Game settings apply to your whole game and are edited from the Settings page by roles with the mayEditSettingsGame permission (see Roles). Every change is validated on the server before it lands, then saved and synced like everything else.
They cover things like the defaults every player starts with (prefix, theme, primary colour, sounds) and join requirements such as kicking accounts younger than a minimum age. A few deeper entries are only read from the Studio Settings module, like ChartsNotice (tells your staff when your game joins the HD Admin Charts), Partitions (only raise this if your game may exceed 100,000 live servers) and DataGroupName.
Warning
Changing DataGroupName resets all saved HD Admin data. Only touch it if that's exactly what you want.
Personal settings¶
Each player gets their own You settings: theme, primary colour, font, content scale, menu height, prefix, and sound volume and pitch. Choices save to the player's profile and follow them between servers. Editing them requires the mayEditSettingsYou permission, which the default Player role grants to everyone.
You can lock any of these game-wide using the CanChangeYouSettings switches on the Settings page, such as CanChangeYouSettingsTheme or CanChangeYouSettingsPrefix. While a switch is off, everyone uses the game default for that setting.
Info
Locking a setting doesn't delete anything. Each player's saved choice is kept and restores the moment you re-enable the switch.
Themes¶
HD Admin ships with 23 themes, from Dark and Light through to Cyberpunk, Horror and Tycoon. To add your own, drop a ModuleScript inside the loader's Config > Themes folder. There's no registration step. It appears in the theme picker automatically.
A theme only overrides what it declares and falls back to the base theme (Dark) for everything else:
-- A ModuleScript inside HD Admin/Config/Themes
return {
Settings = {
LayoutOrder = 250, -- position in the theme picker
ShowInYouSettings = true, -- set false to hide it from the picker
LockPrimaryColor = true, -- players can't recolour this theme
LockFont = true, -- also available: LockContentScale
},
Color = {
Primary = Color3.fromRGB(255, 230, 0),
Base = Color3.fromRGB(8, 8, 14),
},
Font = {
Body = "rbxasset://fonts/families/Oswald.json",
Heading = "rbxasset://fonts/families/Oswald.json",
},
}
Studio defaults¶
The Config instance inside the HD Admin model holds your Studio defaults:
Roles: the default role modulesCommands: your custom commands (see Commands)Settings: the default game and player settingsThemes: theme modulesBans: the static ban listArgs: custom command argumentsTools: gear for the tool commands
In-game edits are stored as changes on top of these defaults, never as replacements. The two Use Studio Defaults switches, UseDefaultRoles and UseDefaultGameSettings, revert your game to the Config files without deleting anything. Flip one back off and your live edits return.
Static bans¶
For bans you want to keep in Studio (or version control), add entries to Config > Bans keyed by UserId. reason is required and everything else is optional:
return {
[123456789] = {
reason = "Example",
},
[12345] = {
type = "expire",
bannedBy = 222333,
expiresAt = 1767225600,
reason = "Example",
},
}
type can be "perm" (the default) or "expire" with a Unix time expiresAt. Static bans never call Roblox's BanService. Bans issued in game appear on the Moderation page instead.