Re: Room disruption
As Fun Event Manager I see a potential problems I would like SysOps and Refs to address and offer solutions ..
Given I don't know all the 'rules' and/or procedures, this problem I have may already be addressed. However, there does not seem to be anything that *I* can do about said problem accept what action I have taken on my own.
The problem is thus:
1) Players disrupting an event by making coms announcements as if they were the authority at hand .. ie Event Manager.
2) Players disrupting the room and the event by use of toall.txt where they have programmed commands that appear to be authority.
In case 1 we have non event manager barking orders for players to switch to one side or another, warning other players of infractions, etc and so forth. It is my feeling that ONLY the Event Managers should make any such coms transmissions. What I have done in all cases is respond with " XXXX, leave the event management to me please
Case #2 is the worst offensive IMHO. This is serious room disruption when a player boardcaset messages such as the following:
CO READY?
START YOUR ENGINES
SCRAMBLE SCRAMBLE SCRAMBLE
STOP SHOOTING - ROUND OVER!
The above is a real no, no anyone that knows how to recored and broadcast same knows better. This is not a case of a new player .. these are experienced players that know better.
I really do NOT want this topic to address any specific player by name. Already the worst offenders have been spoken to by their squad leaders. In the case of new pilots or pilots that are not on a squad, some how I need to be able to address them with a warning on file that 'sticks'. Warnings is all that I really need at this time. A Warning .. that broadcast to all pilots with the offending pilots name attached makes it clear this is NOT just some private room for horsing around. This is an OFFICAL USSAC event and room disruption won't be tolerated. I would suggest that after so many warnings, the name of the pilot would be turned over to sysops for further actions (if any).
These events, especially LTS move so quickly that it is hard for an Event Manager to put all on hold to ascertain if there is a sysops or Ref present that has also seen the infraction, then try and contact them privately to take some action.
A workable solution would be for attending Event Managers , sysops and refs to be present on USAAC Team Speak for that one hour where the Event Manger could immediately, by voice, request authoritative assistance.
Squad Leaders: You could also help with said problem if you would use your squad forms/email systems to inform all pilots that such action/abuse/disruptions could lead to some type of discipline that could affect them system wide.
Your assistance with this complaint/concern is required and appreciated.