Slash commands

/settime

Set the world date/time and notify clients.

Implemented · Source comparison: October 6, 2026.

Reviewed October 6, 2026. This page covers the root, registered subcommands and documented internal actions.

Registration permissions

Registration Handler Required status (local DB, Oct 6) Implementation
/settime 58 10 Implemented

Set the world date/time and notify clients.

Implementation: Implemented.

Syntax

/settime <hour:minute> [month] [day] [year]

Arguments

Position is zero-based in sep, after a registered database subcommand has been removed. Internal action tokens remain at position 0. Angle brackets are required; square brackets are optional. Alternative forms may change field meanings.

Position Argument Accepted value / type Meaning
0 time text Hour and minute separated by a colon.
1 month integer Optional month.
2 day integer Optional day.
3 year integer Optional year.

Behavior and restrictions

The active handler performs the operation described above after the registration permission check.

Current argument/client/target checks (exact source excerpts; branch-dependent):

if(sep->arg[1] && sep->IsNumber(1))
if(sep->arg[2] && sep->IsNumber(2))
if(sep->arg[3] && sep->IsNumber(3))

Permissions

Local database snapshot, October 6, 2026: /settime requires status 10 (handler 58). Other worlds may configure different values.

The dispatcher checks the resolved registration status before invoking the handler. In-handler guild, group, ownership, client-version and target checks still apply.

Examples

/settime 8:30

Source-checked forms; not executed against a live world.

Source evidence

Dispatch: COMMAND_SETTIME (handler 58).

  • WorldServer/Commands/Commands.cpp:4054 — COMMAND_SETTIME.

Reviewed local revision: 9efddf962ffee075d0db2059d3914c36b0acbdf3; working-tree file checksums identify the exact reviewed bytes. Reviewed dispatch/helper evidence · Reconciliation report.

No upstream Markdown file exists for this registration in the retrieved revision.

Permissions are from a read-only snapshot of the configured local world database on October 6, 2026; deployed worlds may differ. Argument and behavior evidence comes from the reviewed WorldServer checkout. Examples were checked against source and were not executed in a live world.