Commands

There is a good deal of commands in DayJobs. I aim to reduce the number of needed commands with the future addition of Job Registrars, but until then, I'm stuck with what I've got.

Some caveats:

• Required arguments are contained in <angle-brackets>. A pair of angle brackets denotes a single, one word argument.
• Option arguments are denoted by [<bracket-contained-angles>]. Again, these are single, one word arguments.

Player Commands

There aren't many player commands, but the few that exist are important.

Command: /job change <new-job>

Places a change request ticket for an admin to review. However, if the server allows instant first job changes and your job is still the default job, you will change jobs immediately. If the server allows all job changes to be instant then your job will change immediately.

Arguments

<new-job>

The job you would like to be changed to

Optional Arguments

None

Command: /job info [<job>]

When called without the optional argument <job>, this command will give you info on your current job. If called with the optional argument, you will receive information on the job specified, if it exists.

Arguments

None

Optional Arguments

<job>

The job to display information on

Command: /job list

Lists all available jobs.

Arguments

None

Optional Arguments

None

Command: /job whois <player>

Makes a whois query on a player. At the moment, this will only return the player's job, but as more features are added, so will more output to this command.

Arguments

<player>

The player to retrieve whois data on

Optional Arguments

None

Admin Commands