Overview
Who calls, who sees the call, and how it is closed.
One command opens the interface for everybody:
/dispatchA player whose job matches a service gets the list of open calls. Everybody else gets the form to make one. The same command, two views, decided on the server.
The three states
Waiting --accept--> On Going --resolve--> ResolvedThe owner of a call is whoever accepted it, and only they can resolve it. A responder who disconnects hands the call back to the pool, so a dropped connection never leaves a call reading that somebody is on the way.
Resolved is not gone. The call stays in the list for resolvedVisibleSeconds, then it disappears from the interface while the history row stays in the database.
Where to go next
| Services | mapping your jobs to the services in the form |
| Calls | cooldown, notifications, and calling from another resource |
Install, framework and database are under Setup.
Access
Config.Command = {
enabled = true,
name = "dispatch",
restricted = false,
}Left at false, the job decides who gets the list. Set to true it becomes an ACE restricted command, for a server that wants the interface behind a permission as well.