In order to combat SPAM on the forums, all users are required to have a minimum of 2 posts before they can submit links in any post or thread.
Discussion in 'UHall' started by Tina Small, Feb 7, 2013.
Yeah this a strange little bug. Had it a few times. Recall just stops working for a few minutes.
Also saw some others complaining about the same thing in guild chat.
I noticed it on Atlantic shard.
Yep, it's an annoyance, kinda like a dead zone for a few minutes.
Same thing on Great Lakes these past few weeks. Kal Ort Por and then the sound of crickets.
If Lord Blackthorn can't get the trains to run on time, how does he expect to run a whole kingdom?
Happening to me too on great lakes with lag spikes mixed in too...
Sent from my Galaxy Note 2
Same on Ches. Very odd. It's happened before, but I'm not sure why it happens unless there is some sort of subserver lag issue.
the same and also many more instances of casting targeted spells and getting no cursor (also no mana used and no message about block)
For me it is game lock up after recall or complete crash. EC user. Not happened enough to pin down from leaving an area or doing a certain action to soon before recalling. Had the same cast time and motion and nothing to target with or mana used. Becoming one those in game "old timers" theese things not really an issue. Perfer to putz around in game theese days with nothing new interest me or gets the heart racing.
Had this happen too on Napa lately...hit recall...wait for it.....wait for it....nothing.
Sometimes I crash once I do recall...mostly I don't. Noticed it more the last few weeks.
I will be looking into this issue.
Now that I'm testing the EC I'm getting this as well, thought it was my computer tho.. Odd
My husband and I play on Chessy and we have both had this happen in the past couple of weeks.
I have had this happen when I had multiple spellbooks in my pack and only one was full! I would move the other spell books to a different bag and put the full one back in my main bag and then it would work?
Having the same problem on Baja, Legends, Atl, Pac.
The classic client also seems to lock up for a bit when logging in a lot of the times. Has this happened much to anybody else? Doesn't prevent me from getting into the game, just doesn't respond for 1/2 a minute or less.
Yes Airhaun this has been happening to me a LOT lately, takes forever to log in on PAC, CC, time of day or night doesn't seem to matter. Doesn't do it EVERY time, just mostly.
oh yea, getting this often, recall , recall , recall nada, hit hide and eventually recall kicks in, once I get into the none moving recall which in my idoc hunt indicates is daily I just stop and await the eventual movement to somewhere.
Yay for Cloud computing! Not... oh and the vet rewards gump take awhile to pop up too sometimes. All started after the "server upgrades".
the game as a whole has been slow for me for months. i just assume its been since they virtualized everything and have the servers hosted.
step step pause
step step step pause
Ditto, takes forever to login to the shard selection screen, recalls are sloooooow, my ping has tripled and 40%-80% packet loss is pretty much the norm now. Time to call it quits I think :/
I admit I skipped over the threads BUT...
I have had a similar problem like this in the past except after I tried recalling about 3 times (they all went through) upon the second time I tried I tried going to another place, no places were blocked and it sen tme to the third place rather then the very first and I was able to run around for a good what, 10 seconds before it even took me to the place I recalled to?
Sorry I didnt read the rest of the posts so maybe someone already said this but, its not a recall or gate spell problem but a subserver problem. This happened on about 3-4 weeks ago, for about 30 min to an hour was not possible to change subserver so recall, gate didnt worked if the destination rune was on a different subserver. House teleporters didnt worked to houses located on different subservers and just to prove it was a subserver thingy, I marked a rune and recalled to that rune. It worked of course, since the destination was just next to me, in the same subserver. After that 30 min - 1 hour LS crashed and we had a revert of 1-2 hours aprox.
I have found the issue to be loosely associated with lag.
Nor is it new.
It comes and goes, mostly associated with a new period of lag.