- Joined
- Jul 4, 2022
- Messages
- 33
- Reaction score
- 38
- Points
- 18
Suggestion Title: RTPC - Raptor - Callsigns (again I know soz)
Division: MET - RTPC
While it seems to be a constant debate around Raptor / Roads crime team and callsigns, the discussion around it borderline seems constant now and with more and more people agreeing to the idea with different ways of doing it.
Typically the main discussion has been around a baseline "Raptor" callsign implemented into game which people seem to not like, which is understandable with it being a bigger word and so forth. Discussion of OC50+ still being used while still just calling up as Raptor 10+ or whatever over radio and so forth.
However, as noticed by numerous colleagues within Raptor and as noted by Kube "and the fact controllers never read 50+ because its so high
been times sat doing nothing for 3 hours and watching the same 5 OC10-20 callsigns being called up for every CAD job". This ignited the debate we've had many of a time again within our team area, but to a surprise many people suggested ideas that are already being used in the server and would actually fit rather well with everybody in the team agreeing.
As known CTSFO use the in-game callsign as 'CT' while pronouncing it as 'Scorpion' over the radio and so forth, as suggested by ArinZima "Maybe something like RT or RA for the callsign, and then call it Raptor, like CT with Scorpion". The RA/RT callsign whichever may be used shows a clear distinction of roles and capabilities of the unit calling up while pronouncing it as Raptor, which can be seen to work with CTSFO very well.
The efficiency of callsigns when you require a specific unit quickly especially for controls sake e.g. scorpion and raptor helps massively as just alone from there displays abundance of information about the unit calling up, and shows the in some ways experience / skillset gap which is sometimes required for more fiery / high risk jobs.
Division: MET - RTPC
While it seems to be a constant debate around Raptor / Roads crime team and callsigns, the discussion around it borderline seems constant now and with more and more people agreeing to the idea with different ways of doing it.
Typically the main discussion has been around a baseline "Raptor" callsign implemented into game which people seem to not like, which is understandable with it being a bigger word and so forth. Discussion of OC50+ still being used while still just calling up as Raptor 10+ or whatever over radio and so forth.
However, as noticed by numerous colleagues within Raptor and as noted by Kube "and the fact controllers never read 50+ because its so high
been times sat doing nothing for 3 hours and watching the same 5 OC10-20 callsigns being called up for every CAD job". This ignited the debate we've had many of a time again within our team area, but to a surprise many people suggested ideas that are already being used in the server and would actually fit rather well with everybody in the team agreeing.As known CTSFO use the in-game callsign as 'CT' while pronouncing it as 'Scorpion' over the radio and so forth, as suggested by ArinZima "Maybe something like RT or RA for the callsign, and then call it Raptor, like CT with Scorpion". The RA/RT callsign whichever may be used shows a clear distinction of roles and capabilities of the unit calling up while pronouncing it as Raptor, which can be seen to work with CTSFO very well.
The efficiency of callsigns when you require a specific unit quickly especially for controls sake e.g. scorpion and raptor helps massively as just alone from there displays abundance of information about the unit calling up, and shows the in some ways experience / skillset gap which is sometimes required for more fiery / high risk jobs.
