ISO-8 Brotherhood Aug 19 - 28

1679111217

Comments

  • I'm not seeing anything different from the point spread compared to any past events. The difference is that while traditionally only in the top 10 range you've grinder dominated results, in this event because there's almost no possibilty of wiping out due to scaling, grinder dominates for every segment on a relative basis. That is, if you're an average guy that can only do 5 refreshes and someone else fairly average has enough time to do 7, that guy is a 'grinder' compared to you and you can't make up those 2 extra refreshes. In a normal event, the other guy ends up only being able to do 5 because the scaling stops him from grinding, but with all enemies doing base level ability damage there's almost no way you'd lose as a result of scaling. Normally scaling keeps people of the same roster strength clustered close together, since the average person can't grind away on level 150+ stuff, but in this event everyone can grind the hardest nodes easily so the separation becomes much bigger than normal while the rubberband still remains weak.
  • GrumpySmurf1002
    GrumpySmurf1002 Posts: 3,511 Chairperson of the Boards
    I joined late yesterday, had high hopes as I got a fresh bracket and no names I recognized. Went to bed in 1st. Woke up in 11th (not bad), with Ghast having passed me, plus another guy who opened a 2k lead overnight.

    Guessing I'll just dial back down on the expectations here. Go token party!
  • I made the mistake of under estimating moonie. I wanted to get rid of tiny daken in one of the nodes, so I cast magnetic flux, switched to him and made a match. Moonie stole it...

    Owwie, momma.

    The most painful nodes for my ** teams are the lieutenant/ 2× pyro. Only one I feel the need to bring 3× p/b stockpile to, but still manage to eat 1 flamethrower each time. The Rags nodes damage definitely adds up, and god how annoying.
  • HairyDave
    HairyDave Posts: 1,574
    Yeah Rags kicked the **** out of me earlier - his powers might be neutered at the moment but he can still get some ludicrous cascade action happening. He damn near killed my intact Fury in one turn with the cascade that never ended.
  • y2fitzy
    y2fitzy Posts: 255 Mover and Shaker
    I really hate that Pyro git. Thank god for Thor...
  • vudu3
    vudu3 Posts: 940 Critical Contributor
    I joined a couple of hours ago. I was the 970th person to enter my bracket. Ouch.
  • Seems like a stealth patch came down to offest the "damage bug".

    Seems like some people abused it to take a large lead in their main brackets and they are trying to limit the disaster.

    Smart money is on: "in a few days, they will open up a main SUB with ridiculous open the flood gates rubberbanding" and 8 days of this nonsenssical grinding, nerfing and boosting of point values will be for absolutely nothing.

    Thanks for being predictable D3.
  • Tonzil wrote:
    Seems like a stealth patch came down to offest the "damage bug".

    I still have the bug
  • HairyDave
    HairyDave Posts: 1,574
    papa07 wrote:
    Tonzil wrote:
    Seems like a stealth patch came down to offest the "damage bug".

    I still have the bug
    Me too.

    And thank god or I'd never have survived that last tilt at the Fury required node in India. I think Ares managed to Sunder me at least three times before I finally scraped together enough AP to get the Patchneto train rolling.

    Edit: and did we get gently nudged into sub brackets or is it purely coincidence I see a bunch of forumites in both brackets?
  • HairyDave wrote:
    papa07 wrote:
    Tonzil wrote:
    Seems like a stealth patch came down to offest the "damage bug".

    I still have the bug
    Me too.

    And thank god or I'd never have survived that last tilt at the Fury required node in India. I think Ares managed to Sunder me at least three times before I finally scraped together enough AP to get the Patchneto train rolling.

    Edit: and did we get gently nudged into sub brackets or is it purely coincidence I see a bunch of forumites in both brackets?

    I just write about it and when I need one more win to secure top50 in India, which node do I pick, lvl180 goons or lvl110 Rags/Ares? Force of habit, I take the goons, get a **** board and finish late with Rags/Ares when I remember the bug. Hope 3 people didn't pass me the last 2 minutes.
  • I don't think anyone has the bug fixed and people are just losing to the enemies doing base level damage without realizing how much their match 3 damage can do. Ragnarok still can pull 4 digit cascades off a Godlike Power and there are plenty of green AP feeders for him.
  • Phantron wrote:
    I don't think anyone has the bug fixed and people are just losing to the enemies doing base level damage without realizing how much their match 3 damage can do. Ragnarok still can pull 4 digit cascades off a Godlike Power and there are plenty of green AP feeders for him.

    Plus buffed Ares is hitting like a tank in PvP, so that could be easily confused.
  • I've pulled a combined 11 ISO tokens and only had 1 3* cover with no fury. whats up with that
  • silverrex wrote:
    I've pulled a combined 11 ISO tokens and only had 1 3* cover with no fury. whats up with that

    That's the odds. 11 covers 77.42% chance for no Fury. They just teased me with a Hulk red this time, which was an improvement over the 2* Iso-fest I had been getting
  • I had an 80+ level Juggernaut hit me with a headbutt for 125 damage in one of the unlock nodes, so I think the bug's still there.
  • Ben Grimm wrote:
    I had an 80+ level Juggernaut hit me with a headbutt for 125 damage in one of the unlock nodes, so I think the bug's still there.

    It seems like people are expecting D3 to secretly fix a serious game breaking bug and not even tell anyone about it because that's how sneaky they are.
  • Phantron wrote:
    Ben Grimm wrote:
    I had an 80+ level Juggernaut hit me with a headbutt for 125 damage in one of the unlock nodes, so I think the bug's still there.

    It seems like people are expecting D3 to secretly fix a serious game breaking bug and not even tell anyone about it because that's how sneaky they are.

    Communication has been bad enough I could see them fixing it and waiting a while to tell people because they want to make sure they've actually fixed it. They've made more major changes than this without acknowledging it for a week.
  • Phantron wrote:
    Ben Grimm wrote:
    I had an 80+ level Juggernaut hit me with a headbutt for 125 damage in one of the unlock nodes, so I think the bug's still there.

    It seems like people are expecting D3 to secretly fix a serious game breaking bug and not even tell anyone about it because that's how sneaky they are.

    If I had a bug that bad and could not fix in with a few hours I have pulled the PvE that was going on until I could fix it. They knew about it when the event was less than a day old or maybe before it had event started.
  • Spoit
    Spoit Posts: 3,441 Chairperson of the Boards
    Sumilea wrote:
    Phantron wrote:
    Ben Grimm wrote:
    I had an 80+ level Juggernaut hit me with a headbutt for 125 damage in one of the unlock nodes, so I think the bug's still there.

    It seems like people are expecting D3 to secretly fix a serious game breaking bug and not even tell anyone about it because that's how sneaky they are.

    If I had a bug that bad and could not fix in with a few hours I have pulled the PvE that was going on until I could fix it. They knew about it when the event was less than a day old or maybe before it had event started.
    Well you saw how graceful they were with the first run of the "point unlock subs" mechanic. And that was a) when they were actually around more than once a month. and b) actually noticing it within hours

    (For those who weren't here, they "had to wait a while to discuss what to do" and then the next day decided that "it had already ran too long, so they can't do anything about it")
  • Ebolamonkey84
    Ebolamonkey84 Posts: 509 Critical Contributor
    The latest update fixes the base level attack bug. I would skip until forced unless you feel like turning on hard mode.