Kinda bewildered myself with this thought:

Staff loves to bitch about how certain classes when combined with certain ‘builds’ (we all know and love as the meta-max) tend to over-perform DPS wise. So they nerf certain aspects OF that DPS to put them further in-line with other classes & builds… ad infinitum…

They announce that certain builds and classes are not performing well enough, so they make up the deficit by increasing the effects and procs available to those classes….

NOW they claim there are too many effects and procs… that it’s bogging down the que and creating lag. Their solution is to cut back on the rate these effects and procs and generate… supposedly this will reduce the load on the processing que…

So now it will actually take longer to kill mobs and bosses, because we aren’t spawning the procs and effects as often as we need…. Which likely means needed de-buffs will wear off and dragging out fights even further… which just floods the cue in surges rather than a steady pace…. (provided most of the party isn’t dead by now)…

I guess  this means the next big ‘announcement’ by staff will be that to address the significant loss of over-all party damage output the reduction in procs caused… they are going to restore some of the previously reduced DPS?

I mean..  wait… wut?

ZooperDooper wrote on Apr 20^th, 2021 at 5:25pm:


This is iust a general issue with scaling. They didn't even plan for the game to scale to 20 when they released it, let alone 30.

And these clowns want to take it up to 40, that should be fun.

Farmer wrote on Apr 18^th, 2021 at 7:19pm:


You have received a warning at Dungeons & Dragons Online Forums.

Reason:
-------
Community Rules Violation: Please read the community rules and follow them.

No gatekeeping by picking forced fights.

   

Quote:


I wasn't referring to HP values, I was referring to procs.

Essentially they didn't plan ahead. If they were smart they would have sat down and looked at the game from the start "Ok, this level 1 sword does an extra 1d6 fire damage... so a good sword at end-game(currently lvl 10) might do 3d6." This is where their line of thinking stopped, so now you've got a sword at lvl 30 that does 15d6 + a shitload of other things.

Then you start getting into doubleshot/doublestrike, rapid fire, etc, etc, etc, and that's where all the overhead comes in: too damn many dice roles. If you took a typical endgame DDO character and tried to work out how many physical dice you needed per attack, i imagine it would be A LOT.

...that totally sounds like a fun project, actually.

Quote:


This is not surprising at all given the history. Remember: DDO owes much of it's server arcitecture to Asheron's Call, which predates multi-core CPUs by a lot. Waaaaaaaay back in the day, conventional wisdom was to use dual-socket servers, with 1 CPU to run the game code and a second to run the server OS(and of course you always had clusters of servers - so 1 for chat, 1 for logins, etc). At the time there was really no reason to go the extra mile and multi-thread your software because quad-socket servers were exponentially more expensive. It was easier to optimize your code or split elements out into additional hardware.

The first dual-core CPUs didn't hit the market until 2005(thus allowing for 4 CPUs on a dual-socket board). Development of DDO started, what, 2002, 2003ish? Unless you were a DEEP insider in the tech industry back then, it was pretty easy not to predict the rise of multi-core CPUs.

Shunned wrote on Apr 20^th, 2021 at 9:12pm:


I thought technically you had the possibility, but realistically it wasn't productively achievable... I think certain types of weapons had an auto deduction from the off-hand double

The arsehats have committed to a cap increase.
The arsehat have also claimed that they have hit the top end of the engines performance with procs.... Or blah blah blah spaghetti code lag, effects queue, halo effect, slot in any other bullshit term to mean they fucked it up.

So if they really want to increase the cap, this is the first of a series of nerfs they are gonna need to do so 40 can actually happen.
Lynnabels ED cluster fuck will be the next one I suspect.

The only thing that those imbecilic shit stains have managed to do is flip the same switch in my brain that made me quit smoking cigarettes cold turkey back in 2013. 

This time instead of being disgusted at the thought of giving more money to Joe Camel, I’m disgusted at the thought of giving those undeserving cucks at SSG another fucking penny.

On the bright side, I’ll have probably saved myself at least a couple thousand dollars by years end.

Prostetnic Vogon Jeltz wrote on Apr 21^st, 2021 at 5:06pm:

Well done!

Shinyshoes wrote on Apr 21^st, 2021 at 12:58am:


Yet the very first item in the loot preview has a chance of proccing spell power increases.

I was thinking about a WF build; the FU49. 17Wiz/3War, Shiradi MM/CM/PL:Wiz/Eldritch Cone/EA Sunburst/AM Arcane Blast/PM Aura/Inquis bolts (to supplement all the spells with yet more effect proc chances). Focus everything on fucking the effect queue.

Maybe a bit of RP for dmg but that'd be gravy.

Just ran my Ranger on hardcore. New bow changes suck, slow as shit on the first lifer.

noamineo wrote on Apr 20^th, 2021 at 8:12pm:


I don't think a 3d6 proc takes more computing resources than a 15d6 proc. The game isn't rolling 15 dice, it just generates a random number between 15 and 90. It's the "shitload of other things" that is (supposedly) causing the trouble.

higgildypiggildy wrote on Apr 23^rd, 2021 at 4:38pm:

Here is the dice rolling and coding department of SSG.  The least expensive to fund but most productive.