![]() |
|
#1
|
|||
|
![]() Sorry, wrong account x2
| ||
|
#3
|
|||
|
![]() Detoxx your suggestion is dumb. Nilbog said Dain shouldn't be spawning from failed Ring Wars so don't need some stupid compromise when it's being removed.
__________________
Green
Tofusin - Monk <Force of Will> Manowarr - Druid Blue Tofusin - 60 Monk <BDA> Shiroe - 60 Enchanter Manowarr - 60 Druid | ||
|
#4
|
|||
|
![]() It is 100% coincidence that zone only desyncs when guilds outside of FAT are attempting Dain guys. Don't be silly. FAT would never do shady shit for pixels.
| ||
|
#5
|
|||
|
![]() we had the zone desync when dain was at 40% so remove the tinfoil hats. You guys got it to what 90%?
| ||
|
#6
|
||||
|
![]() Quote:
I think a courteous thing to do is move your raid force away from the force who had the FTE. Sound reasonable? If there is a built-in issue with code or whatever that does this when a force of XXX number is close to each other in zone, then maybe Sirken or Staff can make a new rule saying: If 2 or more guilds are going after "raid target", and 1 guild gets FTE, then other raid forces in the area need to move away from the FTE guild to avoid possible desync. If other guilds don't comply they will face consequences. Yes?
__________________
Rebbon - BDA
Happy Epic Mage | |||
|
#7
|
|||
|
![]() I looked at the BDA circlejerk front page but couldn't find any mention of it.
| ||
|
#8
|
|||
|
![]() Don't make me pull over
__________________
go go go
| ||
|
#9
|
|||
|
![]() They had 130 people for dain? More with less!
Its nice to see so many players just playing the game not caring about loot though. That would be a long line to wait in. | ||
|
#10
|
|||
|
![]() I was like hey Sirk, mind crashing the zone? BDA and Rampage are here and we don't feel like working hard tonight. He was like yeah sure, plug pulled. So he yanked the plug on the zone when we had Dain at 40% forcing us to log back in and recover for another FTE and kill down from 100%. Thanks Sirk. Worked out just like we planned it.
| ||
|
![]() |
|
|