Ares has a lightweight job tracking system. It is not as robust as Anomaly Jobs, but does provide a lot of the same basic functionality. This article gives a general overview of the jobs system. For specific command syntax, see the “Jobs” help topic in-game.
Table of Contents
Jobs and requests are actually the same system. The player-side commands are just named “requests” because it’s more intuitive than “jobs”.
You can customize the job workflow for your game, but the default flow is:
Comments on a job can be admin-only (visible only to other job admins) or responses directed to the player.
You can also loop in other players to a job by adding them as ‘participants’. When you do, the other players will see and be able to respond to the job as if it were their own request.
Anyone with the
can_acess_jobs permission has access to the jobs system. However, you can fine-tune access using roles. Anyone with the ‘admin’ role automatically has access to all job categories. For other staff roles, you’ll need to use the job category commands to assign their role to the categories you want them to access.
For example, you might add the ‘builder’ role to the BUILD category. If you create custom roles for app/plot staff, you could assign those roles to their respective job categories. They will not have access to other categories.
There are various filters to help you find jobs by state or by category. Valid filters are:
You can also use the search feature on the web portal to search all jobs–including closed and archived ones.