More than two weeks now. “We are working to resolve this as quickly as possible” is starting to feel unlikely …
I second this, 2 weeks for a function that doesn’t affect 1 player but when you think about it affects GUILDS meaning hundreds of people for every guild. This should be higher in the priority list. - Let’s get real.
4 Likes
deux semaines que le service ne fonctionne pas ça devrait être régler depuis longtemps qu’es-ce que vous faites.
1 Like
Plus, really, it’s a no-brainer for Blizzard to fix it. Guild transfers cost money. And guilds don’t transfer without a whole load of guild members also spending money. Those people are way more likely to spend money transferring, if they’re able to go with their guild. So having guild transfers available must SURELY be a money-spinner?
I understand that not everything can get done immediately, but from a business point of view, fixing those things that mean people can’t play at all (thus they’re not going to re-subscribe) and fixing those things that actually bring in money essentially for “free”, should surely be near the top of the list?
1 Like
How long can it take Blizz?
In another post that had this question answered there is no ETA atm. Please do not reply there as I’m merely quoting for reference.
1 Like
How long is a piece of string? Blizzard have a tendancy to be very enthusiastic about updates, when they’re working on things and have a good idea of outcome/timescale.
But they tend to stay completely silent about stuff that either they’re not working on at all, or it’s going to take a long time. The official line is something like “we don’t post updates when there are no updates, because then people see there is a new “update” and get excited about it, but then get disappointed because it’s not actually an update”.
Personally, I think the truth is more like “we don’t post updates, because if you knew how long it would take/that we weren’t working on it, you’d get very cross - and having people frustrated because of lack of news, is better than people cross because we’re not doing what they want”. For me … I’d prefer to know up front if they’re not working on something, or that it’s not going to be fixed any time soon. At least then I have something I can work with.
In this case, I certainly wouldn’t hold your breath. We’ve moved without our guild. We’ve lost all that history and essentially we can no longer honestly advertise that our guild was established 2007 … because it wasn’t, any more. We’ve lost all of those achievements and, yes, some of them will just come back pretty quickly, but others took a long time, and a lot of co-operation between guildees, to make it happen.
It’s a pity there isn’t a way for them to copy/paste the “profile” of a guild from one to another. Sure we’d lose the guild vault - but we transferred the majority of the contents with characters, and we’ll buy the slots back, but there should be something in the system to be able to scrape the achievements and data from one guild in one location, and paste them on to another - even if it means just removing them from the original.
We’re a long way from the days back when Blizzard promoted guilds as the best way to play with others. Now we’re just a distant memory, as far as they’re concerned. With our rubbish calendar, cut down settings and options, and some weird link to communities so that our roster and chat interface are both inadequate and buggy.
These days, I’m afraid, guilds have to exist despite the problems that they encounter. Which often feels like swimming against a current.
1 Like
It’s been around a month now - probably a bit longer - and there has been no news. Honestly if they’re just not going to fix it … I’d rather them say so. It’s very unfair to keep people in limbo, hanging on hoping something might happen, if there is no chance for it to happen.
I know the standard answers of “no official word”, “no ETA”, “no update” … but someone, somewhere, knows whether or not this is being worked on, and what sort of timelike they’re looking at.
I’m not expecting a specific answer, unless it’s to say “no, we’re not going to fix it”, but a rough estimate of “sometime before the end of April”, or “before Christmas”, or even “they have looked at it, but have no idea how to fix it, they’re stumped, so it could be a long time”. But usually, when I or anyone else I know, has been working on something for a month, we usually have a rough idea of how long it’s going to take.
Again, unless of course no-one IS actually working on it.
And … I know the CS monitoring the forums essentially look at their screens, which say “nope, nothing” - but if just a tad more research could be put into this, it would be great. I really don’t want this to be another “connecting low population realms” thing, where people sit around waiting several years for a promised fix that never happens.
Apart from anything else, I know that just because there’s no official word, you do tend to get other information that isn’t “official” 
1 Like
I would also like to request some sort of update on this issue.
A month is a fairly long time with no word on what is going on.
EDIT:
I found this on the US forums which was posted three hours ago.
1 Like
Well doesn’t that explain, in an absolute nutshell, how Blizzard view guilds. They were aware that guild services were not compatible (how could they not have been?), yet they still went ahead and launched the token system, regardless. Even worse … not only were they aware of it, and launched it regardless, but they didn’t bother telling us in advance. Just “hey look, spend all this money transferring”.
First we knew that we couldn’t transfer the guild, was when members were starting to buy transfer tokens and we tried to transfer the guild on the 23rd Feb. At which point when I questioned it, I was directed to support articles such as https://eu.battle.net/support/en/article/32543 … the types of articles I’d been pouring over for weeks prior, in order to know exactly how the process worked. So either I simply didn’t see it, on that one day that they posted that, or the message about them being “temporarily disabled” was added retrospectively.
But as they must have been aware of it BEFORE they launched the new token, they should have also updated that information before, too. Which they did not.
These have just been re-enabled. Not that it has been particularly well advertised.
At least they did something
True, and they were helpful getting our guild transfer sorted. Although that’s more down to the CS guys than Blizzard themselves. And they’re working with both hands and a leg tied behind their backs.