Anomaly Jobs has a tiered access structure. By changing who has access to various commands, you can selectively allow players like builders into the system so they can work. The access locks are on the Job Database <JD> object. Bucket access locks are stored at the bucket level.

 HAS_ACCESS : Returns 1 if a player can access the +jobs system.
 COMPLETE_ACCESS : Returns 1 if a player can /complete jobs.
 APPROVE_ACCESS : Returns 1 if a player can /approve jobs.
 DENY_ACCESS : Returns 1 if a player can /deny jobs.
 CREATE_ACCESS : Returns 1 if a player can use the /create command.
 ADD_ACCESS : Returns 1 if a player can use the /add command.
 GIVE_ACCESS : Returns 1 if a player can use +bucket/access.
 EDIT_ACCESS : Returns 1 if a player can use the /edit command.
 STATS_ACCESS : Returns 1 if a player can pull reports on the system.
 LOG_ACCESS : Returns 1 if a player can /log a job.
 MAIL_ACCESS : Returns 1 if a player can /query and /mail.

A player must pass HAS_ACCESS before the other locks are applied.

Access to buckets are set at the bucket level. See +help jobs/bucket config.

 +buckets

This command will display a list of information about all of the buckets that you have access to. For wizards, this information is very detailed. Here's the meaning of the more esoteric bucket info:

 Flags : VHPMLS (Viewing Hidden Published Myjobs Locked Summary) 
 #Jobs : How many jobs are in the bucket. 
 Pct : Percentage of jobs in the system in this bucket. 
 A : Post to this BBS on /approve. 
 C : Post to this BBS on /complete. 
 D : Post to this BBS on /deny. 
 Due : Auto-overdue in this many hours
 ARTS : Average resolution times.

 +bucket/info <bucket>

This command displays detailed information on <bucket>. Much of this reflects the '+buckets' command, only in an expanded form, except for the following:

 Provides : This lists special attributes that are passed down to the job. If a
 job has summary information, it will show up here.

 Settings : These are user-defined summary settings, settable with the command
 '+job/sumset'.

 Players : This is a list of connected players who presently have access to
 that bucket.

 +bucket/monitor <bucket>

Invoking +bucket/monitor allows you to toggle whether or not you see a bucket when you type '+jobs'. Any jobs in those buckets still show up in other list views such as '+jobs/new'.

 +bucket/create <bucket>=<description>

This command creates <bucket> with the <description> you provide. You must set a lock for the bucket on the Job Database <JD>, as it defaults to 1 (anyone who can pass the main lock can access it). /create is Wizard-only.

Example lock (for a bucket named VAMP):

 &ACCESS <DB#>=[switch(get(/RACE),VAMPIRE,1,0)]

You can find the bucket's DB# with +bucket/info.

 +bucket/access <player>=<bucket>

This command toggles access to <bucket> to the named <player>. This allows them to bypass the default bucket locks. They must still pass the main lock to access. You can change who can alter access with the GIVE_ACCESS on the Job Database <JD> object. It defaults to wizard only.

 +bucket/delete <bucket>

This permanently removes <bucket>. The bucket must have no jobs inside of it for it to be successful. Wizard only.

 +bucket/info <bucket>

Using the /info switch, you can get the configuration information on <bucket>.

 +bucket/info <bucket>

Using the /info switch, you can get the configuration information on <bucket>.

To change your basic configuration settings:

 +bucket/set <bucket>/<setting>=<value>

Valid bucket <settings>:

 DESC : Change the bucket's description. These should be kept
 relatively short.

 HIDDEN : Determines whether or not a bucket is visible when the player
 types +jobs. Valid <values> are 'yes' and 'no'.

 LOCKED : If a bucket is locked, all jobs within cannot be modified.
 However, jobs in locked buckets can be transferred out into
 non-locked buckets.

 LOGFILE : Identifies the file to log to (if logging is enabled). Valid
 <value> is a <filename> (the rest is handled automatically).
 The following file then must already exist on the server:
 game/logs/M-<filename>.log

 MYJOBS : Determines whether or not +myjobs can access the bucket. Valid
 <values> are 'yes' and 'no'.

 POST_APPROVE : Determines what BBS# a bucket will post to when a job is
 completed with '+job/approve'.

 POST_COMPLETE : Determines what BBS# a bucket will post to when a job is
 completed with '+job/complete'.

 POST_DENY : Determines what BBS# a bucket will post to when a job is
 completed with '+job/deny'.

 TURNAROUND : Determines how many hours to add to the due date of a job
 automatically upon creation.

Buckets can be configured in advanced ways, using action hooks, summaries, automated triggering and parent information. This is where the true power and flexibility of the system comes to bear. However, such things should be executed by someone who is versed in code.

 +jobs : List jobs
 +jobs/[all|mine|pri] : List in <bucket>/all/yours/pri
 +jobs/compress : Compresses job list (Wiz) 
 +jobs/credits : Display credit information
 +jobs/list <bucket> : List all jobs in <bucket>.
 +jobs/overdue : List overdue jobs. 
 +jobs/reports [<report>] : Get a report
 +jobs/search <pattern> : Search jobs for <pattern>.
 +jobs/<sort|date|new> : Lists jobs by bucket/mod/new
 +jobs/stats : Gets stats on the job system.
 +jobs/who <player> : Lists jobs assigned to player.
 +job <#> : View a job
 +job/act <#> : Display actions on a job. 
 +job/add <#>=<comments> : Add comments to a job. 
 +job/approve <#>=<comment> : Approve a player request.
 +job/assign <#>=<<player>|none> : Assign a job to player
 +job/clone <#> : Clones a job.
 +job/complete <#>=<comment> : Complete a job.
 +job/create <bucket>/<title>=<comments> : Create a job manually.
 +job/delete <#> : Delete a job (Wiz)

 +job/deny <#>=<comment> : Deny a player request.
 +job/due <#>=<<date>|none> : Set job due date.
 +job/edit <#>/<entry#>=<old>/<new> : Edits a job.
 +job/esc <#>=<green|yellow|red> : Escalate a job.
 +job/last <#>=<X> : List last <X> entries in <#>.
 +job/lock <#> : Locks a job and prevents changes.
 +job/log <#> : Logs a job
 +job/mail <#>=<message> : Mails opener with <message>.
 +job/merge <source>=<destination> : Merge two jobs into <destination>
 +job/name <#>=<name> : Rename a job.
 +job/publish <#>[=<comment>] : Publishes a job or <comment>.
 +job/query <players>/<title>=<query> : Sends a query to <players>.
 +job/set <#>=<0-6> : Set progress status on a job.
 +job/source <#>=<player list> : Changes opened-by to <player list>.
 +job/summary <#> : Views a job's header & SUMMARY.
 +job/sumset <#>/<set>=<value> : Changes a job SUMMARY setting.
 +job/tag <#> : Tags a job for you.
 +job/tag <#>=<player> : Tags a job for <player>.
 +job/trans <#>=<bucket> : Transfer a job
 +job/unlock <#> : Unlocks a job.
 +job/untag <#> : Untags a job.
 +job/untag <#>=<player list> : Untags a job for <player list>.

 +buckets
 +bucket/info <bucket>
 +bucket/monitor <bucket>
 +bucket/create <bucket>=<description>
 +bucket/delete <bucket>
 +bucket/access <player>=<bucket>
 +bucket/set <bucket>/<setting>=<value>

 +job/complete <#>=<comment>
 +job/approve <#>=<comment>
 +job/deny <#>=<comment>
 +job/delete <#>

The first command allows you to complete job <#>. When /complete is used, the first comment of the job and your <comment> is posted on the public job bboard. No intermittent comments are posted to keep the buffer limit small (so that the BBS can handle it). It then deletes the job. /approve works in the same fashion, except the player who opened the job is sent an @mail, and a copy is posted to the staff-only job tracker. /deny works in the same fashion as /approve, only informs the job-opener that their request or job is denied.

The /delete is only usable by a WIZARD character. The /complete, /approve and /deny commands can all be individually locked.

Your personal jobs list can be configured. By setting a list of flags on yourself, you can get a customized display of the jobs listings.

 Flag	Displays Flag	Displays
 --------------------- ---------------------
 T	Title B	Bucket
 D	Due On A	Assigned To
 S	Status M	Modified On
 C	Creation Date O	Opened By
 #	Job DB# F	Flags

You can set these by typing, for example:
 > &JOBS me=TBDS

The default is: BTDAS

Try setting a different list and looking at it, but note that choosing all the flags, the list will look terrible unless you have a very wide screen setting, as it will spill over 80 columns. If that happens, drop some letters off of the end of your setting and try it again.

You can also turn off jobs broadcasts by:
 > &JOBS_SILENCE me=1

Erasing the attribute will return you to the default behavior.

You can filter out some mail generated by the system (such as +request receipts) by setting:

 > &JOBS_NOSPAM me=1

This will filter out 'non-important' MLETTER_* hooks. Erasing the attr will return you to the default behavior.

There are two methods by which you can track new job activity. The new method is similar to Myrddin's BBS (ie, once you read a job, it is no longer 'new' to you). The old method (new activity since your last log out is new until you log out again) is the default.

To use the new method:

 > &JOBSN me=1

Erasing the attribute will return you to the default behavior.

See also: +help jobs/access and +help job/bucket-config.

 +jobs/credits

This command will list the current version, release date, and license information for Anomaly Jobs.

These commands help you sort through various +jobs.

 +jobs
 +jobs/all
 +jobs/list <bucket>
 +jobs/mine
 +jobs/pri
 +jobs/search <pattern>
 +jobs/new

The first command displays a list of all +jobs for buckets that you have access to, not including any jobs in hidden buckets. The second command displays a list of all jobs in all buckets that you have access to, including hidden buckets. The /list switch gets a list of all jobs in <bucket>, provided that you have access to <bucket>. Using the /mine switch, you can get a list of all jobs assigned to you. Using the /pri switch, you can get a list of jobs by priority. You can /search through jobs for <pattern> and get a list of all jobs containing it. Using /new you can list all jobs that have new activity.

 +jobs/sort
 +jobs/date
 +jobs/stats
 +jobs/overdue
 +jobs/who <player>

Using the /sort switch, you can get a list of jobs sorted by bucket. The list isn't very pretty, however. Using the /date switch, you can get a list of jobs sorted by when the job was last modified, with recent modifications at the bottom of the list. Using the /stats switch, you can get a list of basic statistics on the jobs system. With the /overdue switch, you can list all jobs that are in overdue status. The /who switch allows you to get a list of jobs that have been assigned to <player>.

 +job <#>
 +job/new <#>
 +job/add <#>=<comments>
 +job/trans <#>=<bucket>
 +job/esc <#>=<green|yellow|red>
 +job/assign <#>=<player>
 +job/merge <source>=<destination>

The first command allows you to view an individual job. You can only see added comments with this command. The /new switch allows you to see just the comments that have been added to <#> since your last log out. The /add switch adds <comments> to job <#>. The /trans switch transfers job <#> to <bucket>. The next command alters job <#>'s escalation code to <green> or <yellow> or <red>. The next command assigns job <#> to <player>. The next command merges two jobs together. Job <source> is copied into Job <destination>.

 +job/mail <#>=<message>

The /mail switch sends the list of players in Opened-By a <message> via @mail and gives instructions to the player on how to respond.

 +job/set <#>=<0-6>
 +job/due <#>=<<date>|none>
 +job/act <#>
 +job/name <#>=<title>

The first command changes job <#>'s status from <0> to <6>. The second command allows you to set a due date for job <#>. The <date> string can be in one of two formats: 'Jan 13 10:00:00 2003' or '01/13/03'. Using /act will allow you to view all job actions performed on a job - escalations, sets, merges, all information will be displayed, with when the action was performed and by whom. Using /name allows you to change the <title> of Job <#>.

The /set value codes are: 0=ON HOLD, 1=NEW, 2=UNDERWAY, 3=1/4 COMPLETE, 4=1/2 COMPLETE, 5=3/4 COMPLETE, 6=COMPLETE.

 +job/lock <#>
 +job/unlock <#>

When a job is locked, it cannot be modified in any way until unlocked. It can, however, be transferred to another bucket. This behavior is allowed in case administrators wish to impose a lockdown on a whole bucket.

 +job/edit <#>/<Entry #>=<Old>/<New>

This command edits <Entry #> on Job <#>, replacing <Old> with <New>.

 +jobs/compress

This is a wizard-only command. When job ID numbers become too large (say, in the thousands), it is prudent to compress your job list to make the numbers more manageable. When you compress the jobs, it renumbers all open jobs, one through X, and resets the next available job number.

 +job/log <#>

 Log a job to the server. The log file must previously exist on the server. The log file must previously exist: /game/logs/M-joblog.log

 +jobs/reports [<report>]

Without <report>, the command will display a list of available reports. If <report> is specified, the <report> is displayed. There are a variety of reports, available in a variety of formats.

 +job/tag <#>
 +job/tag <#>=<player list>

The /tag command tags a job for you to watch. Tagged jobs will show up on your +jobs/mine list (or <player>'s list), even if it is not assigned to you.

 +job/untag <#>
 +job/untag <#>=<player list>

This will untag a job from the watch list, for yourself in the first instance and for <player list> in the second.

If you tag a job to a player that does not have access to the jobs system, then the job will show up in +myjobs, and they will have FULL ACCESS to that job (IE, they will be able to read all entries, and they will be able to add to that job), no matter if the job is in a public bucket or not.