Disallowing to pretype CMDs in SOC part.

[BeaTen.]

Your Name: BeatEn
Your suggestion: Disallow to pretype /taze /cuff /search /uncuff in a SWAT test.
Reason: Most of the people get ~3 seconds in SOC part these days just by doing nothing but pretyping CMD(s). I know pretyping is very useful but when you actually get accepted and team with SWATs, you will realise that you can't always pretype, you have to be fast and type in the spot. When they get tested and we see the results, the SOC is like 3 seconds but it actually isn't true. I remember when I was getting tested in 2014 (or 15, ger was a commander back then), he was testing me and he didn't allow me to pretype and I don't know why is it allowed to pretype in SWAT test. If you still want to keep it in SWAT test, then keep it too, but add another part where applicant needs to type CMDs on the spot.

[CXdur]

I wasn't allowed to pretype in my tests either, but we need to keep in mind that it is nearly impossible for us to know if they pretyped or not and this would be very hard to enforce.

[BeaTen.]

I wasn't allowed to pretype in my tests either, but we need to keep in mind that it is nearly impossible for us to know if they pretyped or not and this would be very hard to enforce.

If (while testing) you stay near the applicant, he won't be able to pretype /taze or /cuff but he would be able to pretype /search and /uncuff but it would be pretty useless since first you have to taze and cuff then search and uncuff so you can partially determine if he is pretyping or not. He may copy /taze or /cuff but copying should not be a problem.

[CXdur]

I wasn't allowed to pretype in my tests either, but we need to keep in mind that it is nearly impossible for us to know if they pretyped or not and this would be very hard to enforce.

If (while testing) you stay near the applicant, he won't be able to pretype /taze or /cuff but he would be able to pretype /search and /uncuff but it would be pretty useless since first you have to taze and cuff then search and uncuff so you can partially determine if he is pretyping or not. He may copy /taze or /cuff but copying should not be a problem.

Yeah, you are still able to pretype. At least my SAMP client remembers my text when I close the chat.

[BeaTen.]

I wasn't allowed to pretype in my tests either, but we need to keep in mind that it is nearly impossible for us to know if they pretyped or not and this would be very hard to enforce.

If (while testing) you stay near the applicant, he won't be able to pretype /taze or /cuff but he would be able to pretype /search and /uncuff but it would be pretty useless since first you have to taze and cuff then search and uncuff so you can partially determine if he is pretyping or not. He may copy /taze or /cuff but copying should not be a problem.

Yeah, you are still able to pretype. At least my SAMP client remembers my text when I close the chat.

It's not only your SAMP client, it's everyone's SAMP client, but it still would be much better since applicant's would not be allowed to pretype the whole thing, what they do is (what I think what they do), pretype taze cuff search and copy and paste uncuff..

[CXdur]

It would still be very hard to enforce though.

I'll link Wajeeh this topic and let him make the final call.

[Wajeeh]

Yes you can easily pre-type all 4 commands (/taze /cuff /search and /uncuff), but mostly people limit themselves to 3/4 commands.
Considering that the Warrant Officers stay close to the applicants, they will still be able to pre type 2/4 commands as CXdur said.
Thus we can never ensure the fairness in speed of commands test, we can however limit them to 2/4 commands.
I will inform the WO's and prevention of pre typing all the commands will be enforced, thanks!