Thanks for the informative reply..
Quote:
Originally Posted by Derubael
[You must be logged in to view images. Log in or Register.]
There's two potential problems here:
1) If Guild R1 helped from Guild R2 to down a mob, Guild R3, R4, R5, R6 and Rx would need to agree that this was ok. I understand that you guys have a rotation worked out, but since there are so many guilds involved in Class R, and CSR doesn't recognize the authority of said rotation, all the guilds would need to agree this was OK, not just the two involved in killing the mob. Given the amount of cooperation and communication within Class R, I don't see this being a huge issue. It still means we have to track down each guild and get with their leadership to verify it was acceptable.
|
Correct -- but if no one petitions, you SHOULDN'T have to check. It would just be noted on the raid page who is locked out. Azure Guard was (2), Trak was killed, and now Azure Guard is (2) again... so obviously they helped.
Us R guys have our forum and we all sleep with each other. There wouldn't be any problems. There is also a huge difference between:
Situation A) BDA solo-killing Trak when they are locked out (not approved by R)
Situation B) Azure Guard sending 5 guys to help Europa kill Trak (approved by R, but not by GMs since we are locked out)
Class R guilds would know the difference between the situations, but the GMs would not unless some petitioned.
Quote:
Originally Posted by Derubael
[You must be logged in to view images. Log in or Register.]
2) The bigger problem is that the lockout system is hard-coded into the game. The system allows for a couple 'oopsies' on an encounter log to account for close FTE battles, but this limit is probably lower than what you would like to help another guilds raid. If more than that is added to the encounter, your guild gets put on lockout, we get a flagged warning in-game, and Rogean would have to go in and manually change the board. Basically whether we want them to or not, loud alarms start blaring, staff batphones go off, Sirken and I have to stop everything to come rage at our computer screens, and then we have to call Rogean to whip out his sonic screwdriver and fix the board.
|
Enough said! I was hoping this WASN'T the case and even if 'alarms went off', you would just be able to ignore them (or simply turn off the alarms).
Quote:
Originally Posted by Derubael
[You must be logged in to view images. Log in or Register.]
And finally, after that wall of text, any changes to the raid rules themselves requires a Rogean seal of approval, so you guys would need to all work out, agree on whatever, and then submit it to him for the final OK.
|
As I mentioned, we definitely do NOT want a change in the raid rules here. This isn't that big of a deal.
I was unaware of the manual work involved, and was hoping it would not be the case here... that 'the code' would handle it accordingly.. and you guys could just ignore the alarms and move on in life.
So -- no biggie. We are shaking things up in Class R a bit and are teaming up a lot more. As of now, we are having to dance around the Lockouts, so this was merely a suggestion that would make things easier/more fun for R.
We appreciate the work that has been done, and will continue to respect the 'lockout rule' until further notice!
Thanks again,
Phiren
Azure Guard