In {#55ff55}taxi{/}, {#aa55ff}paramedic{/}, {#9d520b}firefighter{/}, {#ff55aa}sex worker{/}, and {#aaaaaa}mechanic{/} jobs, the code currently only responsible for `/customers` could start acting more as a system of assignment.
I will use the paramedic job as an example, but keep in mind this really applies to all service jobs. **The main principle will be that whoever accepts the call first should get to service the requester.**
Once a paramedic formally acknowledges a service call in the menu, all other paramedics will be prohibited from either formally responding to or servicing that player with a message such as {#ff5555}Another paramedic is already en route to the location.{/}
(An exception could perhaps be made for "first responders", i.e. paramedics who are within ~500m range from the requesting player.
The algorithm would then work some way like this:
1. A paramedic closer to the player than the originally responding one also takes that request;
2. The requester is sent a textdraw informing them of this & asking if they'd like to accept the first responder's help;
3. Should the requester confirm, the original responder is then notified with a message like {#aa55ff}[PARAMEDIC-NAME] is already at the scene and ready to respond.{/})
The restriction will be lifted should the request be canceled by the caller, e.g. because the paramedic is taking too long to come, has left the server, or some such. Automatic (XP / job XP) penalties should apply to paramedics who systematically take the call but fail to respond & provoke player cancellations.
Alternatively, if several paramedics have acknowledged the call, there should at least be a warning that would go like, {#aa55ff}[PARAMEDIC-NAME] is also responding to this call. They are [DISTANCE] away from the caller.{/} This will allow paramedics to calculate their time more precisely instead of coming, without prior notice, to a frustrating sight of the requester being serviced by some guy who was two feet away.
Originally posted in [topic 25141](https://mikescnr.com/forum/index.php/topic,25141.0.html)