🧙‍♂️ Brought to you by Peptides.gg — Use code UO20 for 20% off — GLP-1's, 90+ Peptides and more!

Will EC ghosting bug really get fixed in Pub 112?

Started by Drago · 2021-12-11 · 13 posts · General Discussions
#0
2nd times a charm? hepl
#1
Did the Dev team say somewhere that they were working on this bug again in Pub 112?

I mean, I hope they are, but I haven't seen anything about it being addressed again...
#2
no. lol
#3
they didn't say they would be fixing that.
but I have to tell you, that last publish someone thanked them for fixing it
during testing (I believe they posted it here)

After I read that, I went to TC to see if they were right.
I said in General Chat on TC that it wasn't fixed
but forgot to post here.
I only tested it once on TC at the dynamic champ spawn area
but left because "test" had potty mouth
(someone should really wash his mouth out with soap)
FYI test, my beetle has a mind of its own.
I wasn't telling it to fight the boss
I was trying to get it to fight the spawn
because I was testing to see if I could get drops while you were fighting the boss

It wasn't fixed, but the ghosting is actually worse now.
before this bug fix, I could log out and back in
And they would be off my screen.
but now I have to run a full file check a couple times before they go away.
#4
You have to log in dungeon or Same screen as the ghost yo make them vanish 
#5
For EC, we just need to re-login without closing the client. It seems to happen mostly in classic dungeon? I don’t remember seeing ghosting at Dark father gauntlet, mondain, high seas or shadowguard.
#6
Seth said:
For EC, we just need to re-login without closing the client. It seems to happen mostly in classic dungeon? I don’t remember seeing ghosting at Dark father gauntlet, mondain, high seas or shadowguard.
it happens for me in other places too
doing Medusa & at Ilshenar spawns

if I don't kill something and run a screen or two away
If it dies before I come back, then it shows them still being there.
This also happens with the minions in Trammel
There was a minion the other night staying in one spot for 2 hours before it went away.
I had actually logged out & went to another shard
when I returned to Sonoma & ran past that spot it was still there.
The only thing that took it off my screen, was when Krampus spawned near that area
(I suspect someone was slowing down in that area, to get Krampus to spawn there)
#7
Seth said:
For EC, we just need to re-login without closing the client. It seems to happen mostly in classic dungeon? I don’t remember seeing ghosting at Dark father gauntlet, mondain, high seas or shadowguard.
it happens for me in other places too
doing Medusa & at Ilshenar spawns

if I don't kill something and run a screen or two away
If it dies before I come back, then it shows them still being there.
This also happens with the minions in Trammel
There was a minion the other night staying in one spot for 2 hours before it went away.
I had actually logged out & went to another shard
when I returned to Sonoma & ran past that spot it was still there.
The only thing that took it off my screen, was when Krampus spawned near that area
(I suspect someone was slowing down in that area, to get Krampus to spawn there)

This is getting worse, let's hope Bleak find time to debug this. Or hire a helper to assist him.
#8
“They have had job advertised for many years.
But since they are short of a staff member and bugs are not being fixed perhaps they should allow us to play for free or refund us since we’re not receiving the service we’re paying for”
#9
Yoshi said:
“They have had job advertised for many years.
But since they are short of a staff member and bugs are not being fixed perhaps they should allow us to play for free or refund us since we’re not receiving the service we’re paying for”
Yeah, the game needs at least one more software technician to help fix and support Bleak, not bug reports, QA, forum complaints or excuses that there is no budget for one extra pair of hands. There is no point for Misk and us to keep adding to a long list of bugs if there is not enough manpower to close the issues. 



#10
If even one legacy bug shows in new legacy it's a failure...
#11
McDougle said:
If even one legacy bug shows in new legacy it's a failure...
Well, let's not drag that in to complicate the matter and cause this to lock. 

Legacy is a different shard, the only reason we drag it in is that it uses up "production" resource for an entirely separate "development".
#12
Seth said:
McDougle said:
If even one legacy bug shows in new legacy it's a failure...
Well, let's not drag that in to complicate the matter and cause this to lock. 

Legacy is a different shard, the only reason we drag it in is that it uses up "production" resource for an entirely separate "development".
Fair enough!
← Browse more General Discussions discussions