OSCORP HEROIC - MAY 8-14

1…910121415…76

Comments

  • Unknown
    Unknown
    As an early starter that uses conventional methods rather than grinding points flat out. I, as well as many others, are now at a huge disadvantage. It's going to be a massive amount of time spent over the course of the tournament to get within the top 100 for the new Daken token, and this will come to further disadvantage me and players in a similar position in further competitions.

    For anybody wondering whether to join yet or not, I would suggest to wait a little while, to ensure you don't join against players that are on 8-9k points having taken advantage of the boosted nodes.
  • Unknown
    Unknown
    If they don't restart this, let us join new brackets if we want, or otherwise fix it, I will uninstall, no question. This is ridiculous.
  • IceIX
    IceIX ADMINISTRATORS Posts: 4,322 Site Admin
    elusive wrote:
    Dang it, IceIX, come back and fix this! It's like you disappeared as soon as this happened (though I'm sure it's just a coincidence, don't take me too seriously).

    *note that I finished all of the nodes at least once before the hit and aren't too far behind the top people, but it's still unfair for everyone else.
    Sorry, didn't mean to disappear. Researching. Stay tuned.
  • Unknown
    Unknown
    I really hope some sort of rubberbanding happens for this first bracket cause its ****, otherwise you might as well just reset the event. Please!
  • elusive
    elusive Posts: 261 Mover and Shaker
    IceIX wrote:
    elusive wrote:
    Dang it, IceIX, come back and fix this! It's like you disappeared as soon as this happened (though I'm sure it's just a coincidence, don't take me too seriously).

    *note that I finished all of the nodes at least once before the hit and aren't too far behind the top people, but it's still unfair for everyone else.
    Sorry, didn't mean to disappear. Researching. Stay tuned.

    Wow, you responded to my post. *faints*

    But seriously, thanks for the quasi-update.
  • daveomite
    daveomite Posts: 1,331 Chairperson of the Boards
    Yeah...what was obtainable is not really looking like it is at all now. Too far behind, but no way to catch up with only 50-200 point nodes
  • NorthernPolarity
    NorthernPolarity Posts: 3,531 Chairperson of the Boards
    edited May 2014
    The correct solution to this problem would probably just be to revert back to the old point/rubberbanding values, and increase the progression award thresholds to compensate. I'm guessing this happened because they were predicting total points based off of how many points each subevent was expected to give out, and since they doubled the length of the sub, they had to half the points given out so that they wouldn't overshoot the progression award thresholds. The problem of simply reverting back to old point/rubberbanding values is that progression rewards would be trivial to get, but they can just modify those values to fix this issue. Unless the system somehow is automated to do this, in which case I have no idea whats going on.
  • Unknown
    Unknown
    On another note, How did they decide which players to lock out? I would think IM35, Wolverine (Astonishing x-men), Any of the Spidey's, and any of the Caps would quaily as Heroic.
  • mags1587
    mags1587 Posts: 1,020 Chairperson of the Boards
    Fantastic. Last heroic my scaling was so absurd I could barely play, and this heroic I get caught up in this points disaster. Heroics suck.
  • Unknown
    Unknown
    IceIX wrote:
    elusive wrote:
    Dang it, IceIX, come back and fix this! It's like you disappeared as soon as this happened (though I'm sure it's just a coincidence, don't take me too seriously).

    *note that I finished all of the nodes at least once before the hit and aren't too far behind the top people, but it's still unfair for everyone else.
    Sorry, didn't mean to disappear. Researching. Stay tuned.


    I am jsut glad to hear its being looked into icon_e_smile.gif
  • Unknown
    Unknown
    NorthernPolarity wrote:
    The correct solution to this problem would probably just be to revert back to the old point/rubberbanding values, and increase the progression award thresholds to compensate. I'm guessing this happened because they were predicting total points based off of how many points each subevent was expected to give out, and since they doubled the length of the sub, they had to half the points given out so that they wouldn't overshoot the progression award thresholds, which resulted in screwing everyone over.


    I think they're probably better off just starting it over tomorrow.

    If they reset the point values to their higher versions, you'll also get people who in an attempt to catch up, ground down their lower point values. Then you up them. So they missed them when they were high, ground them when they were low, and now everyone else who waited, gets them high again.

    Restarting seems like a great idea. No one probably got any really great progression rewards yet, those are usually much higher. Sure a bunch of people already hit the token, and they'll get that again. OR - this is probably tougher, reset the event and start it tomorrow, but you can't get progressions you've already earned in the "beta" version of the event today.
  • Unknown
    Unknown
    wathombe wrote:
    If they don't restart this, let us join new brackets if we want, or otherwise fix it, I will uninstall, no question. This is ridiculous.
    Leaving your alliance down a vet seems rather selfish. Unless your entire alliance is thinking about quitting over this

    Easiest solution imo is restarting the event but letting those that already started keep their earned ISO/rewards and even their progression reward progress (except those points don't go toward their ranking).
  • Unknown
    Unknown
    Just piling on because i don't know what else to do. icon_redface.gif

    Ugh. I'm in the same boat and have have no chance to catch up with my bracket leader. tinykitty

    Please fix this.

    marc
  • NorthernPolarity
    NorthernPolarity Posts: 3,531 Chairperson of the Boards
    j12601 wrote:
    NorthernPolarity wrote:
    The correct solution to this problem would probably just be to revert back to the old point/rubberbanding values, and increase the progression award thresholds to compensate. I'm guessing this happened because they were predicting total points based off of how many points each subevent was expected to give out, and since they doubled the length of the sub, they had to half the points given out so that they wouldn't overshoot the progression award thresholds, which resulted in screwing everyone over.


    I think they're probably better off just starting it over tomorrow.

    If they reset the point values to their higher versions, you'll also get people who in an attempt to catch up, ground down their lower point values. Then you up them. So they missed them when they were high, ground them when they were low, and now everyone else who waited, gets them high again.

    Restarting seems like a great idea. No one probably got any really great progression rewards yet, those are usually much higher. Sure a bunch of people already hit the token, and they'll get that again. OR - this is probably tougher, reset the event and start it tomorrow, but you can't get progressions you've already earned in the "beta" version of the event today.

    But the thing is that the subevent is going to last for 2 days, which means that there will be a node refresh for these guys. Once a node refresh hits, rubberbanding lets these guys catch back up and grind the high point values again. You can argue that they wasted time grinding these nodes during this time, but grinding nodes before the end of the subevent has always been a waste of time, so I think this solution would disrupt everyone the least while still fixing the issue at hand.
  • Unknown
    Unknown
    Seeing that the event just started and they've already screwed it up they might as well just reset the entire thing now with not-too-much harm done. Better than pissing off everyone else who now has no way back into the tournament.
  • Unknown
    Unknown
    IceIX wrote:
    Sorry, didn't mean to disappear. Researching. Stay tuned.
    It's almost 3am around here, with another workday coming up shortly. Is it safe to catch a few hours of sleep without missing out on anything important? I'd hate to leave a nose sized impression on my office desk once the coffee wears off. icon_e_wink.gif
  • Unknown
    Unknown
    NorthernPolarity wrote:
    j12601 wrote:
    NorthernPolarity wrote:
    The correct solution to this problem would probably just be to revert back to the old point/rubberbanding values, and increase the progression award thresholds to compensate. I'm guessing this happened because they were predicting total points based off of how many points each subevent was expected to give out, and since they doubled the length of the sub, they had to half the points given out so that they wouldn't overshoot the progression award thresholds, which resulted in screwing everyone over.


    I think they're probably better off just starting it over tomorrow.

    If they reset the point values to their higher versions, you'll also get people who in an attempt to catch up, ground down their lower point values. Then you up them. So they missed them when they were high, ground them when they were low, and now everyone else who waited, gets them high again.

    Restarting seems like a great idea. No one probably got any really great progression rewards yet, those are usually much higher. Sure a bunch of people already hit the token, and they'll get that again. OR - this is probably tougher, reset the event and start it tomorrow, but you can't get progressions you've already earned in the "beta" version of the event today.

    But the thing is that the subevent is going to last for 2 days, which means that there will be a node refresh for these guys. Once a node refresh hits, rubberbanding lets these guys catch back up and grind the high point values again. You can argue that they wasted time grinding these nodes during this time, but grinding nodes before the end of the subevent has always been a waste of time, so I think this solution would disrupt everyone the least while still fixing the issue at hand.

    Ice already stated that rubberbanding is based on the sub leader, not the overall leader. Those who played the high point nodes have an insurmountable advantage in the overall.
    gobstopper wrote:
    wathombe wrote:
    If they don't restart this, let us join new brackets if we want, or otherwise fix it, I will uninstall, no question. This is ridiculous.
    Leaving your alliance down a vet seems rather selfish. Unless your entire alliance is thinking about quitting over this

    Easiest solution imo is restarting the event but letting those that already started keep their earned ISO/rewards and even their progression reward progress (except those points don't go toward their ranking).

    Pfft. They could replace me easily.

    Restarting would be best. Yes, please.
  • WilsonFisk
    WilsonFisk Posts: 365 Mover and Shaker
    Restarting is probably the best thing to do. Still totally sucks for anyone that already put time in. I'm 5000 points behind the leader in my bracket now. Not even a chance to make that up, probably can do no better than top 300 starting off in a hole like this!


    Hope D3 is at least planning on giving us all a good reward as lube for this debacle
  • NorthernPolarity
    NorthernPolarity Posts: 3,531 Chairperson of the Boards
    wathombe wrote:
    NorthernPolarity wrote:
    j12601 wrote:
    NorthernPolarity wrote:
    The correct solution to this problem would probably just be to revert back to the old point/rubberbanding values, and increase the progression award thresholds to compensate. I'm guessing this happened because they were predicting total points based off of how many points each subevent was expected to give out, and since they doubled the length of the sub, they had to half the points given out so that they wouldn't overshoot the progression award thresholds, which resulted in screwing everyone over.


    I think they're probably better off just starting it over tomorrow.

    If they reset the point values to their higher versions, you'll also get people who in an attempt to catch up, ground down their lower point values. Then you up them. So they missed them when they were high, ground them when they were low, and now everyone else who waited, gets them high again.

    Restarting seems like a great idea. No one probably got any really great progression rewards yet, those are usually much higher. Sure a bunch of people already hit the token, and they'll get that again. OR - this is probably tougher, reset the event and start it tomorrow, but you can't get progressions you've already earned in the "beta" version of the event today.

    But the thing is that the subevent is going to last for 2 days, which means that there will be a node refresh for these guys. Once a node refresh hits, rubberbanding lets these guys catch back up and grind the high point values again. You can argue that they wasted time grinding these nodes during this time, but grinding nodes before the end of the subevent has always been a waste of time, so I think this solution would disrupt everyone the least while still fixing the issue at hand.

    Ice already stated that rubberbanding is based on the sub leader, not the overall leader. Those who played the high point nodes have an insurmountable advantage in the overall.

    No they wouldn't. My solution is to revert the point values/rubberbanding scheme back to what it was before the fix. This means that everyone who plays the current sub will be able to rubberband back to the current sub leader who is at 8k points or whatever.
  • Unknown
    Unknown
    NorthernPolarity wrote:
    wathombe wrote:
    Ice already stated that rubberbanding is based on the sub leader, not the overall leader. Those who played the high point nodes have an insurmountable advantage in the overall.

    No they wouldn't. My solution is to revert the point values/rubberbanding scheme back to what it was before the fix. This means that everyone who plays the current sub will be able to rubberband back to the current sub leader who is at 8k points or whatever.

    That would be fine, too, but is it possible?

Categories