volvov2
Dalayan Adventurer
As it currently stands, raids get bugged quite easily, and leaving them is even harder.
Typically, guilds form a raid in any given zone, then massing via clicky AE port or Wizard AE port to the raid zone they are heading for. This works great and keeps the raid together (usually). However, if a person is late, already in the zone or otherwise doesn't get into the raid in the 'raid meet' zone, and a wipe occurs, going to the raid meet zone is worthless because that person (while still in a group) will not appear in raid and will miss the port entirely.
Another part is when a person leaves the raid, if a wipe or sometimes even just a relog occurs, the person will reappear in the raid (not in the group). Forcing everyone to reform the raid.
Finally the last part, which is my biggest pet peeve, if ONE person doesn't raiddisband in each zone hes been to after a raid ends, he can cause everyone to reappear in the previous raid days later, or worse, 2 or 3 raids ago. This can cause group bugs to occur, among other things, and can be extremely hard to stop happening.
However, I have noticed that a zone crash/reboot or a server reboot, will clear whatever database the raid is stored in, so that means its flushable, I'd like to see a new /cmd raidflush or a /cmd raidremove. /cmd raidflush would imitate a zone reboot and wipe out the raid database currently in that zone, preferably only usable by the "Raidleader" (whoever did the raid invites). /cmd raidremove would simply remove the persons name from the raid database window, preventing them from sneaking back into a raid after a wipe or whatever, hopefully made serverwide.
I know this topic has been posted about at least 2 other times, both of which were mostly ignored, so I'm trying one last time, I don't think they should be hard to develop, given how the raiddatabase is flushed after a reboot, so it should be relatively easy. Thanks for reading!
Typically, guilds form a raid in any given zone, then massing via clicky AE port or Wizard AE port to the raid zone they are heading for. This works great and keeps the raid together (usually). However, if a person is late, already in the zone or otherwise doesn't get into the raid in the 'raid meet' zone, and a wipe occurs, going to the raid meet zone is worthless because that person (while still in a group) will not appear in raid and will miss the port entirely.
Another part is when a person leaves the raid, if a wipe or sometimes even just a relog occurs, the person will reappear in the raid (not in the group). Forcing everyone to reform the raid.
Finally the last part, which is my biggest pet peeve, if ONE person doesn't raiddisband in each zone hes been to after a raid ends, he can cause everyone to reappear in the previous raid days later, or worse, 2 or 3 raids ago. This can cause group bugs to occur, among other things, and can be extremely hard to stop happening.
However, I have noticed that a zone crash/reboot or a server reboot, will clear whatever database the raid is stored in, so that means its flushable, I'd like to see a new /cmd raidflush or a /cmd raidremove. /cmd raidflush would imitate a zone reboot and wipe out the raid database currently in that zone, preferably only usable by the "Raidleader" (whoever did the raid invites). /cmd raidremove would simply remove the persons name from the raid database window, preventing them from sneaking back into a raid after a wipe or whatever, hopefully made serverwide.
I know this topic has been posted about at least 2 other times, both of which were mostly ignored, so I'm trying one last time, I don't think they should be hard to develop, given how the raiddatabase is flushed after a reboot, so it should be relatively easy. Thanks for reading!