I am the Guild leader of Wife Aggro (Rank 24), and I have encountered and issue where none of my members have been able to claim or release a Keep. I also have an Alt that is having this issue, I have gone as far as I can in troubleshooting this issue on my own. I have submitted bug reports as well as tickets to CSR's only to be ignored or have my requests dismissed. I have sent at the request of Telephone support an email describing this issues and my plight with your CSR's. I am making one final attempt to resolve this issue before I give up on the game completely!

James

Can we have a list of things that CSR's can help us with?

That way we dont sit for days waiting for a response thats never going to come.

My current guild <Ordo Malleus>, an Order guild on Vortex, has a player that is currently experiencing this standard bearer bug. His main is <Baror> =BW. The bug happened when he tried to claim a keep the same time another guild did. In our Guild Profile it showed us as claiming it, but on the map the keep showed the other guild having possession. That is where the bug instigated from for us. Hope that was at all useful

thanks for the official response (on the forums at least) James. i've had an open active appeal for 2 weeks or more on this issue but have not had any response from csr. it got to a point where i was thinking that there could not possibly be any future in an online game where the csr's/gm's would not even respond to acknowledge that the problem was being looked at (and i know of at least 1 rant/thread where the op has claimed to have quit the game with his whole guild).

might i suggest that in such future situations (and hopefully these are few and far in between) that a standard reply from a csr (even the clinched "we're looking into it ...") would be useful to let players who have such problems know that the dev's are looking at the problem and there is nothing that the csr can do at the moment.

for the record, i am a banner carrier (assign/unassign rights) in guild. claimed a keep with banner then logged shortly after. when i relogged, keep was either released or lost and then taken over again. but i could not equip banner after that, the banner rights icon is still against my character but when i (or any other officer) tries to unassign it says that i am not a banner carrier; when i (or someone else) tries to assign it says i am already a banner carrier. i try to leave the guild and am told that i cannot leave the guild when my banner has been used to claim a keep (when there is no keep claimed by my guild).

---

James wrote:

currently CSR's are unable to assist with Guild Standard bearer issues, we anticipate to have these issues resolved with the release of 1.2.1 which is coming soon.

 

---

Currently, CSR's are unable to do anything... EVER... and i anticipate that they will stay this way...

I have no idea why this worked this morning, but one of our "standard bugged" members was able to leave the guild via the "Leave" button on the Guild Roster tab. I re-invited him and was able to assign/unassign him standards again as normal.

Others have tried this and got the cannot leave while holding a keep error, but for some reason it worked for him. No idea what was different. 

We currently have six of our guild standards bugged on people, and I am going to make them all try to guild quit again to see what happens.

Message Edited by James on 04-09-2009 04:32 PM

---

Ok how about you answer our questions instead of giving us these canned answers! You don't understand my frustration or you would be doing something more, like troubleshooting the issue(which means asking questions regarding the issue so you can better understand our dilemma) just staying you are working on it sounds more like "were aware of your issue but are unwilling to do anything about it please submit you request again at a later date and we will be glad to ignore you in the future!" 

I don't mean to rant but its become the only way I get a response from anyone at mythic!

Not sure if this has been answered in another post, but I was able to fix this glitch by unassigning, then re-assigning the bugged guildmember's standard bearer status. After doing this, I had no problem deploying standards again.