There are two reasons why the lockout system specifically needs to be enforced regardless of whether or not the other guilds in Class R would like to waive a petition:
1) Class R, being the "entry class" by its very nature has no limit to the number of potential participants on each target. By that I mean RandomnewguildX decides they want to kill a Trakanon - they are most likely going to go after a Class R Trak. Was <Insert New Guild Name Here> sitting outside the entrance to Seb getting ready to mobilize on Trakanon while AG and Europa engaged? No, probably not, but they could have been mobilizing somewhere, and there's no way to know what would have happened if Europa had needed to tag that dragon alone. We need to keep the Class itself open to the entire server when it comes to killing Class R mobs.
2) The lockout system is in place specifically because being in Class R is supposed to put you at a disadvantage - Class Restricted - we had really wanted to encourage some class mobility (even though we knew this would probably never happen) and clearly make "the more difficult class" the "more profitable class" due to its competitive and challenging nature. We had briefly considered making lockout violations something that could be waived if the other guilds agreed but quickly decided against it. That would quickly dissolve the lockout system entirely once everyone started making agreements with each other over who gets what, and then the entire system becomes less accessible for new guilds and removes a large part of the motivation for moving to Class C.
That is why the lockout system specifically gets enforced and can't be waived. In regards to the board being down/malfunctioning, AG could have easily checked with the staff before or even after the kill if they were worried that maybe they were crossing a lockout. I would rather have a guild come ask us how many times mob X has been killed since their lockout started when the board is down than to have them kill targets they aren't supposed to be killing.
|