Okay okay okay rewrite time.
The basic idea is that pinging is used to check up on people and to notify them you're doing so. But it can also be used to find people if needed.
There are different levels of permissions. Some broad, some personal. The higher rank one has the more IDs they'll be able to inherently ping. This brings a separation in the contact list. Personal and professional. The higher the rank the more likely those personal ones will have more strings attached.
Low level drones have to be very selective with who they give their permissions to since they don't get the privilege to block anyone. But also any upper ranks could easily get their information and track them if they wanted even if they hadn't given those permissions. Official complains can be filed with the Control Brains if it's about profession misconduct. But they typically don't do anything unless a large amount of complaints are filed.
Elites get the IDs of most other elites as well as anyone that maybe under their direct command.
Invaders get their contacts cut down. Left with only a reviewed personal list(lucky for them they get to do the review) and those directly under their command.
The Tallest Guard get the IDs of almost anyone who enters the Massive and where else the Tallest may have stationed themselves. They get a proximity function creates a third list sorting based on distance. They also get the option of a silent ping.
The Enforcers get nearly same the lists as the Tallest. With a proximity and priority function. Given their duties of infiltration, investigation, and assassinations the priority function lights up IDs. Shows that they belong to the particular sectors they are working stationed at. They have the options to manually tag IDs as priority. Their pings default are silent, but can be used as standard manually. All personal contacts are thoroughly reviewed, by their Control Brain, their Captain, and themselves. On a regular basis.
The Captain gets the Tallest's IDs, they are the only ones that can't be pinged silently. The Advisor, Lords, and Captain of the Tallest's Guard being the only others who inherently get their IDs. No matter the rank the response from the Tallest's PAK will always be a rest response unless the Tallest manually give temporary permissions. Expections being if 2/3rds of these people were to try and ping the Tallest in quick succession. Then all of the Guard, Enforcers and Advisors would receive a ping from the Tallest's PAK with relevant info.
The Tallest get everything. As well as getting to see what people's actual designations are since their isn't anyone above them. Obviously. All incoming personal pings are blocked unless permission is reissued by their leaders occasionally. The person lists themselves remain unaltered. The Tallest change their default at anytime.
Standard Pings. Pull basic PAK status; normal, damaged, critical, also well as vague location; which sector they're in relative to the senders position. A more honed distance can be manually manually requested. It's still rather vague though. Far too board to reliably find someone.
Rest Pings. A standard Rest Response simply receives them without sending anything back unless special permissions have been given.
In Rest Mode the PAK itself determines the information to share. If in a damaged state and not considering whoever is pinging to be threat it can give over as much information as it wants. A distress ping can be sent to all Irkens in the area. This sends the exact coordinates of the irken. This is not something waking Irkens get access to. However if in a critical state a PAK puts all of it energy into repair and healing. It will give a single standard Rest Response and then block all others until in a more stable condition.
Silent Pings. The Receiver doesn't get notified they are being pinged. These also send back reports on the receiver. Profession, rank, height, infractions. Silent Pings on Enforcers come back with false reports! Unless they're from the Tallest or their Captain.
Failed Pings. PAKs that are damaged in a particular way or destroyed or inactive can't receive pings. The sender will be notified of a Failed Ping. Glitches may occur were a PAK may flag a false fail. Irkens experiencing this problem are required to schedule an appointment with the nearest PAK technician. These glitches occur most often in PAKs that ping on a frequent basis.
