Awesome thanks
Nice I can quote things more then once, and just so I don’t quote this for no reason. Please if you can use a game comparison what’s at least the same genre of arpg. Also what works for one does not mean it will work with another. Also my reply to this is a simple no, the reason for this is if the game has endless scaling difficulty then I should be able to endlessly scale my build.(through effort tweaks and gear upgrades and not just simply press button (x) to do 10x dmg)
The most likely thing to have happened is that due to the server issues it was all hands on deck for all devs to fix those issues (which took about a week to stabilize). And in the meantime they weren’t even aware of the immortal bug.
They likely had someone on the team collecting bugs and reports, but it’s not likely the team did anything other than fixing the servers in that time.
So, in a normal circumstance, yes, it would be a day 1 patch.
In the wildfire that was launch day, no, they wouldn’t even be aware or have time to check those types of bugs.
That’s it. there is no time added to it. Either you are competent or incompetent. There is no inbetween in this case and not past tense. There is no at the moment incompetency you either competent or incompetent and that’s it.
While I’m very amused about the cak and forth, you made my day good sir ^^, I want you to proof your competence adding any sources where a bad descission made a compent person incompetent like getting a debuff of some sort out of the blue.
Yeah… suuuuure. I think I read something alike in the “Trust me bro!” dictonary.
It is because it is to negate somones competence. Noone would call a beginner incompetent because a beginner is leraning. I could call you incompetent in seeing reason and to come up with scientific correct stuff. That wouldn’t be nice because all I would say with this is “This guy talks out of his ass.” without saying so. So yes beeing competent is a bad thing because it tells people you fuck up in your field of competence.
Nah. In the engeneering class a dude always shouted “Proportional!” and he was right like 75% of the time. So he was competent in 75% of all cases without having a clue.
With your level of competence you have a long way to go 
Diablo 1, Diablo 2, Diablo 3, Diablo 4. Dude look for someone else to have beef with because he wasn’t for your little weather experiment and move on.
And I return to my previous comment where not everything you disagree with is incompetence. There are more words in the Englush language.
There are probably hundreds of “five minute fixes” but that doesn’t mean you assign one person to fix all of them before finishing for the day. That’s before you consider that all of those “five minute fixes” may well take significantly more than five minutes, not because of incompetence on the part of the person fixing it but on the part of the person who doesn’t actually know all the details but has decided by themselves that it’s a trivial thing.
It’s easy to decide that as an armchair developer who knows nothing about the actual thing.
There weren’t in any of the other replies that you decided were virtue signalling. And yet…
And yet I’ve never seen you “pushed to the left”, which is statistically improbable, therefore we are left with just one conclusion.
I’d probably say yourself & your belief in your own intellectual superiority compared everybody else (Unity-cursor-gate & slavery-in-general-have-a-decent-life-because-Roman-house-slaves are a good example of this). You also constantly employ the “gish gallop” debating tactic (probably not related but hey, it’s absolutely true).
Nope. Being a qualified developer in a discussion about dev-stuff isn’t a social status, or a moral stance.
Absolutely in the example I gave, though I can’t remember the precise details.
Almost like there were higher/other priorities. Funny that.
If you’re gonna stalk and hate on me do better please. I’m assuming your referring to my post in suggestions thread about adding buff/debuff to different weather based in Emerson mindset. That thread I believe is significantly handle in a more civil manner by all. And as far as I’m concerned is in a positive light. Referring to how people are talking to each other in it now not the everyone likes the suggestion mindset. And I forget my other point so 
What area/language is this, and does it just loosely translate to graduate? I ask area because as I’m sure you know just because you speak Arabic (random pick) does not mean your living in an Arabic area or even of Arabic decent. And I’ve never seen the word if I had to guess it’s Dutch German or slavonic. Am I close?
Also there’s so much here that I have no idea if anyone wanted me to answer something so if someone did please ask what u wanted me to reply again.
Macknum’s German & according to google that word translates to vocational training.
Assuming google is correct, berufsausbildung is what you would graduate from.
I’d translate it with apprenticeship in the context of what he was describing.
Yeah, that works too. Vocational training is a term that was more common in the 90s in the UK while apprenticeships are more used now (I have one sitting next to me at the moment). I think that vocational training is more used for careers which are/were traditionally less academic (eg, mechanic, plumber, electrician) though I don’t think it matters much at all anymore.
Everyone, please remember to be civil in communication.
We actually did a whole big survey and discussion with the community regarding this, and the community decided that only if a build is greatly overperforming as the result of a bug should it be fixed (nerfed) mid-season. Mid-Cycle Balance Survey Recap
For mid-season patches in general, we can only efficiently release patches part way into a season. This is because our internal codebase changes so much, that any bugfixes would need to be done in duplicate. One for the old code, one for the new code. However the real factor here is that these need to go through QA, and QA takes a fair amount of time.
This means that the the further we get into a development cycle/season, the more the codebases diverge, the more and more time a bugfix would take. Increasing to the point that it starts to significantly impact work towards a new season. Though we are looking at ways we might be able to get around this, as we understand how important bug fixes are, and how big of a topic this is for us.
No need to nerf anything, OP.
Fixing bugs with broken skills/interactions/items that are not working as intended is what is needed, that’s all.
Someone playing a stronger or as everyone says OP class than you doesn’t mean jack. But there are an absolute ton of builds capable of running very high corruption and killing UA comfortably.
Game balance is the goal everyone would like to see but it’s highly likely to not be achieved I don’t think I’ve played an ARPG where there hasn’t been “OP” classes/builds.
Fix bugs
Don’t nerf
Put that on a T shirt
Kinda?
Graduating is from a school environment.
Finsihing learning a trade… what’s the term there for when you do? You’re in a work environment already as a apprentice, but you pass apprentice stage. I actually don’t know if there is a term specifically for that.
10 times Ward hence which outperformed everything in existence survival-wise and had quite extreme offensive abilities on top?
Or the ‘I need no investment’ Erasing Strike build?
Or the ‘I do millions of DPS by standing around’ Wraithlord build which could kill every boss in seconds?
Those?
You never defined what is ‘greatly overperforming’, so it’s all relative and now you can say ‘that wasn’t overperfoming enough’ when the community asks ‘why didn’t it happen’.
I understand where you’re coming from though, it’s harsh to decide how much exactly is the point to step in. You guys went a bit beyond the stage in my opinion, and seemingly the opinion of many others. It’s a mess of a situation and hard to handle, so no worries about getting it wrong, I just hope you guys learned for the future when such a extreme example comes up again (also in the underperfoming side) to try out the alternative option and actually compare rather then leaning back and stating ‘but you guys told us so!’.
The community forgives experiments, but you guys gotta actively make a system to base your decisions on rather then trying to avoid as many as possible.
So your argument is reduced to the baseline ‘We cannot achieve it so it’s fine to do absolutely nothing’? Sounds counterproductive.
The qualifier here was as the result of a bug. These were not the results of bugs, so didn’t qualify. There was a separate selection for if it wasn’t the result of a bug, which the community didn’t support.
Nope, mostly because that’s up to the community. We listen to what you all are saying about builds and skills and weigh that extremely heavily with the data we refer to. If something feels bad, it doesn’t matter if it’s technically right.
That’s fair.
So it only applies to the first example of ‘10 times the ward amount’ because that was a bug, a decimal error.
Which was also postponed though. So that’s not quite in-line with what was stated. But outside of that I agree.
Sorry, a correction: I believe the “10 times the amount of ward” was actually one of the issues that spawned the survey conversation in the first place.
Fair, and I remember this happening.
Which brings me to a follow-up question, and that one is a loaded and quite unfair one as we cannot change the past, so I’ll state right away ‘I’m unfair here now’.
Why was this even a thing to be done? The general expectation is ‘Unless it’s a game enhancing bug which has mistakenly improved the situation bugs are to be removed’, where the first part is not something many people even take into consideration.
So why was a poll for that aspect even held? It’s a necessity and given thing that bugs have to be fixed, mid-Cycle or not, and even your biggest competitor GGG is actively doing that despite at times heavily interfering with long-term established builds, because a code error is a code error, no matter what. A bad balance is not the fundamental building block of a game, it’s above that.
My statement is ‘This topic shouldn’t even have become a poll-issue in the first place’ as that is one of the responsibilities of your company to do that in a tamely and qualitative manner, and - to be unfair again - it plays for us as customers no role for the reason or the magnitude, for us the only decision is ‘are we affected’.
The poll was held because there was a large amount of conversation in the community about it sparked by previous patches that had resulted in nerfs with bugfixes. The main argument made against it was “nerfing fun”. It was quite a divisive, and heated topic. We had originally had our own rules for what gets patched or not, but when there was the large outcry, we responded by having a discussion with the community about it.
And this is the case. If it’s a bug, it qualifies to get fixed ASAP. If it’s not a bug, such as an unintentional interaction (original bhuldar’s wrath wearbear), or something that wasn’t accounted for (ice claw ward generation) those don’t get fixed mid-cycle. The main purpose of the survey was for overperforming skills and items that were not ‘bugs’.
It was 71.9% of the voting community, withover 69,000 individuals participating, that said not to nerf overperforming skills or items mid-season when it’s not a bug - It wasn’t a small margin. It’s very well possible this is something we can revisit in the future as the community wants and needs change, but it wasn’t held that long ago. So unless something major happens, it would likely be a while before a review.
However, I believe there’s still confusion here regarding “bug” and “not bug”. Bugs, which is something not working the way it says it’s supposed to, get fixed. Not bugs, which is something that works the way it says it’s supposed to, but is overperforming, wait until the next season. This is also unrelated to the ability (or lack thereof) to release patches later into a season. Further, this is only referring to bugs and balance issues that result in nerfs mid-season. Bug fixes and balance changes that result in a buff are always qualified to go out ASAP. I recommend reading through the survey results post, and see if it helps clarify some more points for you: Mid-Cycle Balance Survey Recap
Thanks for the comprehensive answer there.
Where is the poll about paying for a game that was told to never cost any more later on after you intialy payed once? Was heated as well and largely discussed.
Yeah this is most likely the best thing to use.