Wall Sight bug 13.2

[Schmoe]

Getting fixed today - hotfix happening from 2 till 5 PM EST.


Is it wrong that I am wondering what will break when they put in the fix, or is it a Pavlovian response at this point?

[sweez]

Wonder if anyone tried aggroing all the mobs in Blown to bits to one spot and then just blowing them all up hehe

[Qezuzu]

I'm sorry, are we playing the same game? Please let me know what server you are on where there is no "Known Issues" list. Heck, I'd settle for a list but no major issues...

Nothing on the Known Issues List is even comparable in game-breakingness than this wall thing. Trivial things like ladder catching, "you are not facing", etc are, to me, inconsequential. I can respond to and fix them myself nearly automatically (protip: the "you are not facing" caster bug is fixed by trying to cast the spell again, even when it says it's on cooldown). Other things, like certain weapon effects not doing the correct damage, or run speed not being properly increased as displayed, are unnoticeable unless you specifically try to find them. Bugs that only marginally affect aspects of the games I can almost entirely ignore.

At least, that's how I feel about them. I can understand other people getting upset over them.

I'm glad it's getting fixed today. It shows that Turbine can at least prioritize not having an almost non-functional game over working on new content.

[Postumus]

They will fix it, they always do sooner or later...

In fact it seems Sooneth: http://forums.ddo.com/showthread.php...55#post4434255

Well I will give Turbine credit for trying to fix the stuff they have been breaking fairly quickly. They fixed the charm bug in just a few days. The fixed the TR bug in under a week. I'm sure they'll fix this fairly soon.

I think I'm just going to take a 3-5 days off after every update from here on out so when I play stuff is actually WAI.

In good news, I did test out a few quests yesterday and the Sharn series seems to be fairly unaffected by the wall bug. No problems in Bookbinder or Dirty Laundry which were the two I thought would be the worst. So... yeah... woohoo?

[delsoboss]

/shameless bragging post on

Solo-stealthed EClaw!

S*** it up wall-hackers scorpions!

(http://forums.ddo.com/showpost.php?p...&postcount=201)

/shameless bragging post off

Glad it's being fixed soon.

[Postumus]

Ok, here is a list (not comprehensive) of major bugs since U13. When I say major bug I usually that has rendered some content or basic feature either unplayable or difficult to workaround. Basically, these bugs are all embarrassing and, taken all at once show a rather striking lack of basic QA.

Major bugs since U13
1)Birthday cake rewards broken, required a patch and reimbursement of cakes. Mainly an ominous and embarrassing start to Turbine's birthday celebration.

2) Epic scrolls stopped dropping for a couple weeks, having a major effect on endgame content.

3) Abbott tiles broken by an unintended "fix" to a problem that didn't exist and was never tested.

4) Bound to account bags bugged to become bound to character bags if any BTC item is placed within them. This bug has caused a major disruption of the inventory system.

5) U13.2 wall glitch has rendered large amounts of content unplayable, and is the most gamebreaking bug to hit in a very long time.

This list is just since the most recent major update. This doesn't include the bound ingredient bag glitch that let characters trade bound ingredients, or the duping glitch from the Cannith Challenges patch (U12), which were also major issues. In short, the development of this game, the patch rollout, and QA is nothing short of a professional embarrassment, and doesn't build confidence in this team's ability to release a major expansion. I, for one, have not preordered, and will not until I see how many basic game features quit functioning when the content rolled out.

You missed the charm bug and the TR bug. At least both of those were fixed fairly quickly.

[Postumus]

INow, it'd be easy to blame sloppy coding here but if code potentially affecting seemingly unrelated systems is the definition for bad code then there is no such thing as good code.

QE likely was told there is a new script fixing an issue with doors and so they tested doors. Doors worked just fine and they passed it.

This type of speculation is just that: speculation. Same thing with the arguments like 'it's not the dev's/QA's fault, MANAGEMENT forced them to push it.' Honestly I don't even think this is reasonable speculation in my experience. Every system I've ever worked with gets 'broken' to some degree when it is upgraded or changed. It could be a report, a UI, data mapping, permissions, whatever, but that is what a testing team is for, and good project managers make sure there is adequate testing.

I've never had 'management' force me to put something out that I knew was broken to meet an internal deadline. Maybe it's just that I've had the good fortune to work for companies that expect excellence, but if we caught bugs that affected user functionality in a serious way, we delayed the roll out. If we caught bugs that affected users in a minor way (and dealing with end users there really is no 'minor' bug - as you see by the posts on the forums) then we made sure we communicated this to the users along with the work around before they found it on their own.

It sucks for things like these to happen. They shouldn't happen and this one is particularly bad. They happen because things are rushed. They are rushed because they try keep a seven year old game competitive with games of developers who are in the comfortable situation to spend years developing it from the ground up.

I agree that this shouldn't happen, and certainly not with every... single... update. I don't necessarliy agree that people are being rushed. I don't know. There may have been an internal drop dead date for this patch (more speculation) but it isn't like the user base was clamoring for anything more than the bag fix.

The 'tickling' of the engine should have been tested exhaustively before releasing it to live. Throwing it up unannounced for a couple of days over smack in the middle of Crystal Cove was wishful thinking at best.

[MRMechMan]

Did hard new invasion. Was very memorable and fun.

I am very disappointed to hear that a fix is going live so soon. I was looking to have some more fun playing in broken quests.

Please don't let this fix go live, unless it breaks something that causes equal amounts of entertainment for me.

I suggest the floors.

[Eladiun]

Getting fixed today - hotfix happening from 2 till 5 PM EST.


Is it wrong that I am wondering what will break when they put in the fix, or is it a Pavlovian response at this point?

I'm betting on doors.

[Ew_vastano]

of course the fix is going in soon any bug that helps players is fixed within 24 hrs any bug the hurts players well that can w8 till after the exp is finished

[Ew_vastano]

The 'tickling' of the engine should have been tested exhaustively before releasing it to live. Throwing it up unannounced for a couple of days over smack in the middle of Crystal Cove was wishful thinking at best.

the devs at turbine testing something and not allowing bugs go live now that would be something totaly new and unheard of

[HAL]

Nothing on the Known Issues List is even comparable in game-breakingness than this wall thing.

I stand corrected - most of the major issues in this game don't make it onto the Known Issues list...

[Razorwing007]

We were running bastion last night on casual for flag only. Same moment we stepped in we got red alert and all the way up mobs were shooting cometfall on us from higher floors.

[Barium]

of course the fix is going in soon any bug that helps players is fixed within 24 hrs any bug the hurts players well that can w8 till after the exp is finished

As much as I hate to admit it, Ew_vastano is right on this one. Scrolls falling from the sky in non-epics? Instant quest closure. All your ingredients stuck on one character because the bag is semi-perma-bound to you? A month later. (didn't happen to me btw)

Equal emphasis should be placed on player beneficial as well as player adverse issues occuring in the DDO realm. Also, a simple "Our bad, guys" taking responsibility for the problem would go a huge distance for most of the doom and gloomers.

With that said, issues come up, foreseen or not, that are between simple and extremely complex to fix. Something as seeming simple to the player base as a bag becoming bound when it shouldn't could very possibly be wrapped up in several other mechanics. Thus, fixing one requires fixing the rest as well and ensuring your fix doesn't cause ripples to other aspects. So give 'em a break. They know whose fault it is, we know whose fault it is, but that doesn't get it fixed any quicker.

[Postumus]

With that said, issues come up, foreseen or not, that are between simple and extremely complex to fix. Something as seeming simple to the player base as a bag becoming bound when it shouldn't could very possibly be wrapped up in several other mechanics. Thus, fixing one requires fixing the rest as well and ensuring your fix doesn't cause ripples to other aspects. So give 'em a break. They know whose fault it is, we know whose fault it is, but that doesn't get it fixed any quicker.

So what you're saying is DDO is kind of like having that loveable old dog that can't control its bladder any more? The price of continuing to love the dog is dealing pee on your carpet every once in a while.

[danotmano1998]

We were running bastion last night on casual for flag only. Same moment we stepped in we got red alert and all the way up mobs were shooting cometfall on us from higher floors.

They're just preparing the sequel to:
Adventures in DDO - Die Hard.
(Pre U13.2)

NOW Upgraded to:

Adventures in DDO - Die HARDER!

[Ivan_Milic]

You wanted it harder,you got it.

[muncholuncho]

We did an elite Crucible last night and never made it through the maze after we got the I and K switch we went to drop the crest's in place and were decimated by casters from above at one point we had at least 10 cometfalls in about 30 secs add this to sleet storm 700 million mephits 3000 other spells and we were doomed all we could do was stand there and die was so lagged out we couldn't even move. I was on a Fvspallymonk build and couldn't heal or even loh was quite entertaining. I was half drunk so I just lol'd and went and played Torment.

[Postumus]

We did an elite Crucible last night and never made it through the maze after we got the I and K switch we went to drop the crest's in place and were decimated by casters from above at one point we had at least 10 cometfalls in about 30 secs add this to sleet storm 700 million mephits 3000 other spells and we were doomed all we could do was stand there and die was so lagged out we couldn't even move. I was on a Fvspallymonk build and couldn't heal or even loh was quite entertaining.

That's one way to take the focus off of the swim portion.

Player1: "Crucible? Oh man I HATE swimming through those spikes!"

Player2: "The swim? LOL! We'll be lucky to get past the maze."

[Izwor91]

There is bug with ladders.
If you jump on one, you can't catch it properly and animation is bugged.
(repeating action where you catch ladder)