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
/weather
38
10
Implemented
Inspect or change current-zone weather settings.
Implementation: Implemented.
Syntax
/weather <command> [parameters]
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
command
text
Weather action; see source-derived selectors below.
1
parameter
number or text
Action-specific value.
2
extra_parameter
number or text
Additional action-specific value.
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):
Local database snapshot, October 6, 2026: /weather requires status 10 (handler 38). 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
The syntax forms above are the source-based invocation examples. Replace identifiers with values valid for your world; client callback fields are supplied by the game client.
No upstream Markdown file exists for this registration in the retrieved revision.
/weather enable
Enable weather when the value is 1.
Implementation: Implemented.
Syntax
/weather enable <0|1>
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
action
text
Literal enable action; retained in the root handler.
1
0|1
action dependent
First syntax form: <0|1>. Square brackets mean optional.
Behavior and restrictions
Changes the current zone weather state; this handler does not save database zone settings. Missing parameters print usage.
Permissions
Internal action: inherits the /weather registration requirement of status 10. No separate database subcommand row exists for this action.
The dispatcher checks the resolved registration status before invoking the handler. In-handler guild, group, ownership, client-version and target checks still apply.
Examples
The syntax forms above are the source-based invocation examples. Replace identifiers with values valid for your world; client callback fields are supplied by the game client.
No upstream Markdown file exists for this registration in the retrieved revision.
/weather type
Set weather type.
Implementation: Implemented.
Syntax
/weather type <0..3>
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
action
text
Literal type action; retained in the root handler.
1
0..3
action dependent
First syntax form: <0..3>. Square brackets mean optional.
Behavior and restrictions
Changes the current zone weather state; this handler does not save database zone settings. Missing parameters print usage.
Permissions
Internal action: inherits the /weather registration requirement of status 10. No separate database subcommand row exists for this action.
The dispatcher checks the resolved registration status before invoking the handler. In-handler guild, group, ownership, client-version and target checks still apply.
Examples
The syntax forms above are the source-based invocation examples. Replace identifiers with values valid for your world; client callback fields are supplied by the game client.
No upstream Markdown file exists for this registration in the retrieved revision.
/weather frequency
Set update frequency.
Implementation: Implemented.
Syntax
/weather frequency <seconds>
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
action
text
Literal frequency action; retained in the root handler.
1
seconds
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
Changes the current zone weather state; this handler does not save database zone settings. Missing parameters print usage.
Permissions
Internal action: inherits the /weather registration requirement of status 10. No separate database subcommand row exists for this action.
The dispatcher checks the resolved registration status before invoking the handler. In-handler guild, group, ownership, client-version and target checks still apply.
Examples
The syntax forms above are the source-based invocation examples. Replace identifiers with values valid for your world; client callback fields are supplied by the game client.
No upstream Markdown file exists for this registration in the retrieved revision.
/weather range
Set severity range.
Implementation: Implemented.
Syntax
/weather range <minimum> <maximum>
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
action
text
Literal range action; retained in the root handler.
1
minimum
action dependent
First syntax form: . Square brackets mean optional.
2
maximum
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
Changes the current zone weather state; this handler does not save database zone settings. Missing parameters print usage.
Permissions
Internal action: inherits the /weather registration requirement of status 10. No separate database subcommand row exists for this action.
The dispatcher checks the resolved registration status before invoking the handler. In-handler guild, group, ownership, client-version and target checks still apply.
Examples
The syntax forms above are the source-based invocation examples. Replace identifiers with values valid for your world; client callback fields are supplied by the game client.
No upstream Markdown file exists for this registration in the retrieved revision.
/weather current
Set current severity.
Implementation: Implemented.
Syntax
/weather current <severity>
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
action
text
Literal current action; retained in the root handler.
1
severity
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
Changes the current zone weather state; this handler does not save database zone settings. Missing parameters print usage.
Permissions
Internal action: inherits the /weather registration requirement of status 10. No separate database subcommand row exists for this action.
The dispatcher checks the resolved registration status before invoking the handler. In-handler guild, group, ownership, client-version and target checks still apply.
Examples
The syntax forms above are the source-based invocation examples. Replace identifiers with values valid for your world; client callback fields are supplied by the game client.
No upstream Markdown file exists for this registration in the retrieved revision.
/weather pattern
Set pattern.
Implementation: Implemented.
Syntax
/weather pattern <0..2>
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
action
text
Literal pattern action; retained in the root handler.
1
0..2
action dependent
First syntax form: <0..2>. Square brackets mean optional.
Behavior and restrictions
Changes the current zone weather state; this handler does not save database zone settings. Missing parameters print usage.
Permissions
Internal action: inherits the /weather registration requirement of status 10. No separate database subcommand row exists for this action.
The dispatcher checks the resolved registration status before invoking the handler. In-handler guild, group, ownership, client-version and target checks still apply.
Examples
The syntax forms above are the source-based invocation examples. Replace identifiers with values valid for your world; client callback fields are supplied by the game client.
No upstream Markdown file exists for this registration in the retrieved revision.
/weather chance
Set weather chance.
Implementation: Implemented.
Syntax
/weather chance <0..100>
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
action
text
Literal chance action; retained in the root handler.
1
0..100
action dependent
First syntax form: <0..100>. Square brackets mean optional.
Behavior and restrictions
Changes the current zone weather state; this handler does not save database zone settings. Missing parameters print usage.
Permissions
Internal action: inherits the /weather registration requirement of status 10. No separate database subcommand row exists for this action.
The dispatcher checks the resolved registration status before invoking the handler. In-handler guild, group, ownership, client-version and target checks still apply.
Examples
The syntax forms above are the source-based invocation examples. Replace identifiers with values valid for your world; client callback fields are supplied by the game client.
No upstream Markdown file exists for this registration in the retrieved revision.
/weather amount
Set change amount (integer range guard 0..1).
Implementation: Implemented.
Syntax
/weather amount <number>
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
action
text
Literal amount action; retained in the root handler.
1
number
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
Changes the current zone weather state; this handler does not save database zone settings. Missing parameters print usage.
Permissions
Internal action: inherits the /weather registration requirement of status 10. No separate database subcommand row exists for this action.
The dispatcher checks the resolved registration status before invoking the handler. In-handler guild, group, ownership, client-version and target checks still apply.
Examples
The syntax forms above are the source-based invocation examples. Replace identifiers with values valid for your world; client callback fields are supplied by the game client.
No upstream Markdown file exists for this registration in the retrieved revision.
/weather offset
Set dynamic offset (integer range guard 0..1).
Implementation: Implemented.
Syntax
/weather offset <number>
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
action
text
Literal offset action; retained in the root handler.
1
number
action dependent
First syntax form: . Square brackets mean optional.
Behavior and restrictions
Changes the current zone weather state; this handler does not save database zone settings. Missing parameters print usage.
Permissions
Internal action: inherits the /weather registration requirement of status 10. No separate database subcommand row exists for this action.
The dispatcher checks the resolved registration status before invoking the handler. In-handler guild, group, ownership, client-version and target checks still apply.
Examples
The syntax forms above are the source-based invocation examples. Replace identifiers with values valid for your world; client callback fields are supplied by the game client.
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.