Okay, after using the raid window twice, there is some sort of bug that involves people leaving the group, then leaving the raid, after which no one can invite them (say's they are not in a raid or you can't invite because you're not a leader blah blah blah). I'm not totally sure of the cause, or the solution, but we've fixed it by basically disbanding raids a ton, disbanding groups, and camping out. It's a real hassle and time sink, but I know other people out there have used the window more than us. So, if anyone can elaborate on what exactly causes the bugs in the first place, and how you can resolve them that would be helpful! Thanks!
How to deal with raid window bugs?
- Thread starter hooden
- Start date
Yami
Staff Emeritus
From my experience raid windows seem to be doing ALOT better than they were. But here are a couple tips to help alleviate some of the bugs.
Form all groups first before starting the raid. Then have one person invite one group wait for them to join then invite another rinse repeat. Do not invite more than one group at a time.
2nd. If someone is bugged and can't be invited/or leave the raid. Have them ctrol D to leave group spam it like 10x. Then Alt R to disband from raid then spam Ctrol D again. That has cleared any raid invite bugs from me and the guild 99% of the time. If you don't spam ctrol D after you leave group for some reason it still thinks your in the raid.
Have all members of the raid leave the raid before they camp if possible. This alleviates logging back into it later and dealing with weird crap. If they go LD and don't come back they are stuck in the group / raid. You have to have all members of that group leave group / leave raid / spam ctrol D then reform the group. Then get reinvited to the raid.
Using these we've had very little problems with the raid. Camping out does nothing by the way as the new code for linkdead/camping members of groups they don't leave, as I'm sure you've noticed.
Form all groups first before starting the raid. Then have one person invite one group wait for them to join then invite another rinse repeat. Do not invite more than one group at a time.
2nd. If someone is bugged and can't be invited/or leave the raid. Have them ctrol D to leave group spam it like 10x. Then Alt R to disband from raid then spam Ctrol D again. That has cleared any raid invite bugs from me and the guild 99% of the time. If you don't spam ctrol D after you leave group for some reason it still thinks your in the raid.
Have all members of the raid leave the raid before they camp if possible. This alleviates logging back into it later and dealing with weird crap. If they go LD and don't come back they are stuck in the group / raid. You have to have all members of that group leave group / leave raid / spam ctrol D then reform the group. Then get reinvited to the raid.
Using these we've had very little problems with the raid. Camping out does nothing by the way as the new code for linkdead/camping members of groups they don't leave, as I'm sure you've noticed.
There are two big problems I see at the minute:
Firstly, people are often 'raidbugged' and can't be invited, and they need to ctrl+d and /raiddisband a bunch of times to fix it. This can be very annoying, but it's simple enough to fix.
Secondly, and much more annoying, it seems impossible to remove someone from a raid(?). So, should a couple of people LD/leave, but not disband from the raid, but you want to replace them in the raid, but are at the 36man cap, there's nothing you can do to kick the people, so you have to reform the entire raid...
Overall though, the raidwindow's really nice, and once a few last things are ironed out, I think it'll be great.
PS. Yami's tips are spot on for 'creating' the raid. One at a time, to avoid probs, and all is good...
Firstly, people are often 'raidbugged' and can't be invited, and they need to ctrl+d and /raiddisband a bunch of times to fix it. This can be very annoying, but it's simple enough to fix.
Secondly, and much more annoying, it seems impossible to remove someone from a raid(?). So, should a couple of people LD/leave, but not disband from the raid, but you want to replace them in the raid, but are at the 36man cap, there's nothing you can do to kick the people, so you have to reform the entire raid...
Overall though, the raidwindow's really nice, and once a few last things are ironed out, I think it'll be great.
PS. Yami's tips are spot on for 'creating' the raid. One at a time, to avoid probs, and all is good...
"Secondly, and much more annoying, it seems impossible to remove someone from a raid(?). So, should a couple of people LD/leave, but not disband from the raid, but you want to replace them in the raid, but are at the 36man cap, there's nothing you can do to kick the people, so you have to reform the entire raid..."
Have the group leader target that player with the F key assigned to his or her slot. Nothing will actually target but you'll have the person. Now the leader types /dis player name. I was able to get rid of someone no longer in game by doing that. Not sure if it has to have the player name, or if you can just use your disband shortcut or not. You might also be able to click on the player in the group window and do it that way. Experiment a bit tho, and you'll be able to do it.
Have the group leader target that player with the F key assigned to his or her slot. Nothing will actually target but you'll have the person. Now the leader types /dis player name. I was able to get rid of someone no longer in game by doing that. Not sure if it has to have the player name, or if you can just use your disband shortcut or not. You might also be able to click on the player in the group window and do it that way. Experiment a bit tho, and you'll be able to do it.
BeittilBonker
Dalayan Adventurer
while this method removes a person from the group, they still remain ungrouped in the raid. and with a hardcoded 36 cap u cant replace them unless you reform the raid. what the raid-window needs is a working function to kick ppl out!Eredhel said: