It was literally on the PTR. Lmao. The PTR has had multiple builds this week.
False Reports are against the ToU, hope that helps!
Spreading misinformation knowingly should be a bannable offense because they were already corrected.
6 Likes
Yes, absolutely.
But instead of correcting the misinformation, OP’s just continuing to be belligerent in the comments.
Not in the sense you’re thinking of.
If you aren’t using multiple characters to flag the same post, not a violation.
2 Likes
Can you change the title now that we know that this is not the case OP :3
1 Like
Evidently not, much easier for OP to just pick fights with people in comments.
For sure, I could easily imagine Blizz doing it or at least considering it. I’ll admit my first thought from seeing the thread was “Yep sounds like Blizz, 11.1 IS SURE GUNNA SUCK THAT MUCH MORE HUH BOIS.” So like, I’m not the most mature off the cuff stick in the woods either.
Idk why delves even give hero track in the first place to be fair but I mean, I’ll take it. My days of complaining about LFR and welfare epics was a different lifetime.
1 Like
People are just strange. Delvers v. M+ v. Raiders?
Everyone just stop trying to bolster your self worth by association of a ‘side’. We all in it together and it all ends the same…buying a token. 
1 Like
I’m more than happy for Delves to drop hero loot, but I do see the concern that Ion mentioned that people who do Delves for gearing and if they go into M+ directly afterwards don’t know how mechanics really work. Doesn’t change that Delves should drop gear that go up to at a minimum normal but I’m more than quite happy with them dropping hero level gear as well (whether from the vault or some other way).
Kinda similar to LFR should drop “welfare epics” but just not “welfare gear” (since that usually is attributed to something like Heroic- or Mythic-track gear). This is just one of those weird things where people choose to go very tribalistic about it with a “with us or against us” kind of mentality.
Delves can and probably should change slightly but not to the degree where they become tedious. Which is why I figured this could’ve been another one of the “wait and see”-changes that may be really good for the game’s overall health but isn’t really that popular. As it turns out, it wasn’t - so I’m just happy that for folks who primarily do Delves they didn’t become more tedious, at least not in this way (or any other way, even though I do stand by that Delves probably need to change just ever so slightly because of how folks viewed Delves as little more than a “free gear”-distributor of sorts).
Because the thought that Blizz could implement bad and unfun stuff and display horrible misjudgement is so outlandish, isn’t it? It’s really weird how people jump to these conclusions when the devs have always shown, that they’re developing content with so much reason and sense of proportion and with a sharp eye on the PTR forums.
/s, if it wasn’t obvious, just in case.
Idk, if I see a blue post in a thread, I usually click on that little blue tab to see what they said.
Clearly some people don’t.
Good until he runs into Zeus at worlds
Fair, but then again, there are 3 warnings in game that putting boots into the catalyst won’t activate tier sets, and some people still don’t bother to read any of them.
It’s more the complete lack of due diligence. Rather than noticing that there’s a change easily explainable by 1 person pointing an SQL command at the wrong row/table that’s not in the release notes, and then trying to ask if it’s intended, jumping straight to “they’re just trying to screw you over”, then leaving the original post up after the update, so it will continue to sow discord and spread misinformation.
Why was this flagged? Also… wouldn’t 3/6/9 been a better change or 3/6/10? Asking people to do 50% more delves is a pretty big ask for the last slot.
Do you actually believe that it was a bug? That doesn’t even make sense. Explain how the code would be bugged in such a way that it would suddenly display random arbitrary numbers. They never said it was a bug, just they intend to keep it the same as season 1 as of now. My guess is they wanted to change it but then decided against it and pushed the build before they could revert the change.
I believe that if it were intentional, it would have been in the release notes.
This is actually really easy: someone ran an SQL command on the wrong row in the wrong table. They were trying to multiply everything in a different database row by 1.5.
I don’t think it is the mechanics that are the issue but rather the on ramping. When you essentially throw people into the previous iterations equivalent of a +8 mythic from the start it sort of throws them off. I have said it before, they need better on ramping into mythics. Being overpowered from delve gear for a previous seasons +2-+7 mythics isn’t a bad thing since you have a higher chance to survive while learning mechanics. Bringing the old mythic scaling back would greatly benefit the playerbase.
No it wouldn’t. It addresses precisely nothing about the issue that did occur with people heading into M+ from Delves being geared up to do +7s-+8s but without any of the prerequisite knowledge to be able to do without inadvertently griefing the group.
Adding more M+ levels would just create more dead key-ranks, just the same as before.
1 Like
Yeah, that isn’t how that works. As I said it is 100% more likely this was something they wanted to push out and then decided against than someone ran the wrong multiplication command on the wrong row of data where no other data changed. This implies they wanted to change something else in that data row but none of the other rows had a patch note about it changing either.
It does actually address it because you learn those mechanics without having to go into mythics that are greater difficulty than previous seasons. It is pretty simple. If you want to learn calculus do you just jump into it or do you start with algebra?
Or they wanted to change something in a completely different row, and setup the WHERE condition improperly.
Again, doubtful. They never said it was a bug. They said they wanted to keep it the same. Reading between the lines indicates it was an change that they decided against but was pushed out.