♣ A Baker's dozen in the Prophets of the New Republic and Fallen Heroes. ♣
Abaigeal(TrBd25), Ailiae(TrDrd2), Ambyre(Rgr25), Amilia(Pl20), Einin(TrRgr25), Emili(TrFgt25), Heathier(TrClc22), Kynah(TrMnk25), Meallach(Brb25), Misbehaven(TrArt22), Myara(Rog22), Rosewood(TrBd25) and Sgail(TrWiz20) little somethings with flavour 'n favour
♣ A Baker's dozen in the Prophets of the New Republic and Fallen Heroes. ♣
Abaigeal(TrBd25), Ailiae(TrDrd2), Ambyre(Rgr25), Amilia(Pl20), Einin(TrRgr25), Emili(TrFgt25), Heathier(TrClc22), Kynah(TrMnk25), Meallach(Brb25), Misbehaven(TrArt22), Myara(Rog22), Rosewood(TrBd25) and Sgail(TrWiz20) little somethings with flavour 'n favour
-Qetsil / Sickcat / Dorktastic / Belir / Peachfuzz / Fysh / Sometime / Segment / Skwash / Pyg / Swetn / Smurfingly, And 2 nameless others
All Thelanis, all the time...FER SHIZZLE!
North Trail officer.
Ex-Static Rewards and Unique Loot Search Tool editor.
Ex-DDOViewer user, <sarcasm>thanks Turbine!</sarcasm>
Ex-VIP for 3+ years, ex-player
Oh please, like they have NEVER heard of a bad, bug ridden release before.
I'm not Turbine apologist, but formost I want to know who to blame. I hate collateral damage and if isn't a DDO dev to blame, but a code management person who is at fault, that is who I'm going to gun for.
Right when I rolled my first ever Sneak Rogue, too....
![]()
I mean how hard is it to test this ****!?
I used to work in a Quality department for a software company in the New England area, we had a Code and a CG section and each section had a series of automated test programs that basically put the program through every conceivable situation. The results were compared with the stored correct results and if it were different an error showed up on the daily reports then you could back track who's update caused the problem by regressing the build version. Granted a full set of tests took about a week but certain high risk tests were run daily. Also anytime a bug made it through internal testing (indicating we did not have a test for that situation) a new routine was created to test for said bug and added to the routine. Test were also run on several platforms and configurations of course.
Turbine seems to have a policy of "hey you guys go boot up the latest version, run around a bit and see if it looks ok".
Just fell through a wall in Garrison's. Ran around in the dark until getting zoned back to bind point.
Well hey, at least it compiles and doesn't have any segmentation faults!![]()
Thelanis: Takhysys, Tenauch, Vitriolus, Kalav, Leprous
We're looking into this issue atm so thank you to everyone who has provided details in their bug reports! This is going to be a complex fix because it is related to the physics engine upgrade, so as soon as we have more information we'll post the downtime messaging.
I should also note while parsing through discussion in here that: personal attacks against staff or other players will not be tolerated. Bugs are annoying, but they do not grant license to break the forum rules. Please keep this in mind as you discuss.