FB39 Bug/others

Vyndria - Sanctuary
Vyndria - Sanctuary Posts: 3 Arc User
edited January 2009 in Support Desk
Ok since update, door in FB39 was moved from being in front of the Reverexes to over in front of the tunnel that leads to the Mosssprites, etc...and no way around it or through the door. Was unable to get to the Mosssprites without going through all the other mobs.

Also, since the update, oddly the mobs seem stronger? I ask this simply because for some odd reason now my veno keeps dying on mobs lower lvl than her...and my friend is a lvl 50 Barbarian who has been soloing the FB19's for some time now...without a cleric....and suddenly he's dying in there too.

Come on...something's wrong with that picture. A lvl 50 Barbarian, who has been soloing FB19's without a cleric for awhile now and suddenly he starts dying in two hits?

Oh yeah and your lag is not any better...it gotten worse since the last three updates. No it is not my pc...I have done cleanups, virus checks etc...everything is fine on my end.

When I voice chat...everything is fine until either myself or the one I am talking to goes into West Arch. Then our voice chat messes up, making one of us sound like a robot, or cuts out...making it difficult to understand what is being said. But as soon as I or the other person (depending on who was in West Arch) leaves West Arch, our voice chat is fine again.

Last night it happened again, I had to port to Orchid Temple...then fly over to where the Swordmaster is...with the Skelevizen Warlocks in Shining Tidewood. Still didn't work...so I logged out and came back...and soon as I loaded in...my game disappears completely and a "Report A Bug" box replaced it. Which I did send in.

Then I tried logging back in after sending the bug report in....soon as I seen my girl on top of the house.....same thing happens and the game is gone...with the form for the "Report A Bug" appearing again. This time I shut game down, did a cleanup, restarted my pc...then logged back in. It was laggy still but worked until I logged out 20 minutes later.

So now you have a bug report to look at...and it wasn't something on my end.
This discussion has been closed.