HytalePlayerNameColors

by Mad
for Hytale
Allows players to customize their chat name colors using the /color command. Colors persist across sessions and are automatically applied when players connect.
communityTakaro v0.4.10

Components Overview

1
config
1
commands
2
hooks
0
Cron Jobs
0
functions
1
permissions

New Module: HytalePlayerNameColors

NEW
January 23, 2026
Updated to version latest. Added 1 command: Set Name Color. Added 2 hooks: Load Player Name Color (player-connected), Connected Color (player-connected). New permission: COLOR.

Configuration

Configure this module using the schemas below. The JSON schema defines the data structure, while the UI schema customizes how the configuration form is displayed.

Configuration Schema

No configuration properties defined. This module uses default settings.

UI Schema

No UI schema defined. Configuration form will use default rendering.

About Configuration Schemas

The Configuration Schema defines the structure and validation rules for module settings. The UI Schema customizes how the configuration form is displayed in the Takaro interface, including field ordering, labels, and input types.

Commands (1)

These commands can be executed by players in-game. Each command has a trigger word, optional arguments, and executes JavaScript code on the server.

Set Name Color

/colorTrigger Command

Description

Set your chat name color. Use a color name (gold, red, blue, green, purple, orange, white, cyan, magenta, yellow, pink, lime, aqua, gray) or a hex code (e.g., ff0000)

Arguments (1)

color
stringPosition 0
Help: Color name (gold, red, blue) or hex code (ff0000)
Default: None

Function Implementation

Set Name Color Function

JAVASCRIPT

Usage Example

Player types: /color <color>

About Module Commands

Commands allow players to interact with your module through chat. Each command has a trigger word that players type (prefixed with /), optional arguments for parameters, and a JavaScript function that executes when the command is used. Arguments are automatically validated and passed to the function.

Hooks (2)

These hooks respond to various game events automatically. Each hook executes JavaScript code when its specific event type occurs, allowing modules to react to player actions, system changes, and more.

Real-time Events

2 hooks

Load Player Name Color

player-connectedEvent Type
Description
Loads and applies the player's saved name color when they connect to the server
Pattern Match
.*

This hook only triggers when the event data matches this regular expression pattern.

Function Implementation

Load Player Name Color Hook Function

JAVASCRIPT
Event Details
Event Type:player-connected
Trigger:Pattern Match Required
Category:Real-time Events

Connected Color

player-connectedEvent Type
Description
as;odlgikfj
Function Implementation

Connected Color Hook Function

JAVASCRIPT
Event Details
Event Type:player-connected
Trigger:Automatic
Category:Real-time Events

About Module Hooks

Hooks allow your module to respond automatically to game events like player actions, server status changes, and chat messages. Each hook has an event type that determines when it triggers, optional regex patterns for filtering specific events, and a JavaScript function that executes when the conditions are met. Hooks are grouped by category for better organization.

Permissions (1)

These permissions control who can access different features of this module. Administrators can assign these permissions to roles, allowing fine-grained access control.

General Permissions

1 permission

Color

COLORPermission Key
Description

Allows player to set the color of their name

Permission Details
Full Key:COLOR
Can Have Count:No
Category:General

About Module Permissions

Permissions control access to module features and functionality. Each permission has a unique key for identification, a friendly name for display, and a description explaining what it allows. Some permissions are countable, meaning they can have numeric values or limits assigned. Administrators assign these permissions to user roles to control who can use different module features.