OSCORP HEROIC - MAY 8-14
Comments
-
I'd liken this whole thing to running a marathon, when you're already an hour behind first place, then the judges say, "you guys are running too fast!" and change it to a 52 mile run while simultaneously chopping off one of your legs.
You can certainly make your way into first, so long as you hobble on your crutches as fast as you can with no breaks, and somehow the lead pack totally forgets that they're racing and/or mysteriously falls into a short-term coma. Hey, it's been proven possible by the tortoise and the hare, so it's got to work!
Anything is possible folks, you just gotta believe!0 -
D3 Employee #1: "We've made a huge mistake! The first sub is going to end in 10 hours!"
D3 Employee #2: "Quick, let us make an immediate drastic change with no thought to the consequences!"
#1: "We've made a huge mistake! Points are completely screwed up now!"
#2: "We should do nothing. The absolute best response when anything goes wrong is ALWAYS to do nothing."
.
.
.
.
Can someone explain what would have been so bad about the first sub ending in 10 hours?0 -
Megalawl wrote:Gonna ask this one more time since it didn't get a reply.
Wouldn't just turning the appropriate rubberbanding back on from before the boost to 400m fix everything?
I'm guessing this isn't as easy as just flipping a switch. I have a feeling that boosting the points did a reset on a number of values (including the rubberband values) that they weren't expecting. If that's the case, there might not be a way to get the previous values back.0 -
Reset....... Periods are added to hit 10 characters0
-
Phantron wrote:The main bracket missions only have to be significant relative to the subs, as in they probably have to be worth at least comparable points. The fact that there might be very little points overall is not an issue because rubberbanding will still take care of it.0
-
Another solution just reset first sub0
-
wathombe wrote:D3 Employee #1: "We've made a huge mistake! The first sub is going to end in 10 hours!"
D3 Employee #2: "Quick, let us make an immediate drastic change with no thought to the consequences!"
#1: "We've made a huge mistake! Points are completely screwed up now!"
#2: "We should do nothing. The absolute best response when anything goes wrong is ALWAYS to do nothing."
.
.
.
.
Can someone explain what would have been so bad about the first sub ending in 10 hours?0 -
Another solution reset the whole thing0
-
pandaberry6 wrote:Vairelome wrote:It would be easier to accept the "rubberbanding will fix most of the problematic situations" if we weren't seeing consistent feedback that RUBBERBANDING IS SCREWED UP NOW.
Vairelome! I have been looking for you! Golden Daken: Hot or Not?!
I'm not a huge fan of his beady/squinty eyes, but overall, the beefcake is strong in this one. I'll give him 4 out of 5 stars.
(Sorry, I've been lurking, haven't seen a lot to comment on lately. I'm rather annoyed at whichever dev controls the point-value switches, because I've had a few detailed posts showing how he doesn't have a firm grasp of his job, and the current debacle was entirely predictable on that basis. IceIX's commendable responsiveness is an improvement on d3's usual poor PR, but it would be nice if management would give him more to offer the playerbase than platitudes.)0 -
mags1587 wrote:Megalawl wrote:Gonna ask this one more time since it didn't get a reply.
Wouldn't just turning the appropriate rubberbanding back on from before the boost to 400m fix everything?
I'm guessing this isn't as easy as just flipping a switch. I have a feeling that boosting the points did a reset on a number of values (including the rubberband values) that they weren't expecting. If that's the case, there might not be a way to get the previous values back.
It took almost no time to change the rubberbanding to limit progression so I highly doubt that's the case.I imagine it would take similarly little effort to, say, put a time limit on this sub, give rewards then restart the entire event without screwing it up.
If it IS a lot of effort to sort out a decent solution then they need to learn to code properly.
I assume they don't want to deal with people complaining about HP and/or ISO thhey have spent on health packs, boosts and cover packs for the event so far if it's reset and those dollars are far more important that decent, fair game design...0 -
mags1587 wrote:Megalawl wrote:Gonna ask this one more time since it didn't get a reply.
Wouldn't just turning the appropriate rubberbanding back on from before the boost to 400m fix everything?
I'm guessing this isn't as easy as just flipping a switch. I have a feeling that boosting the points did a reset on a number of values (including the rubberband values) that they weren't expecting. If that's the case, there might not be a way to get the previous values back.
I think they did simply flip a switch to change the community goal from 200m to 400m.
The problem was someone thought the switch would only change that variable. When what happened is it shifted other variables in the event as well. At the very least the rubberbanding. Unable to tell if it changed the base node values or anything else at this point.
I doubt there are individual switches on all of them. Likely the switch was from version #1 of the event to version #2 with all the different variables.0 -
Smells like DEVOPS.0
-
bonfire01 wrote:mags1587 wrote:Megalawl wrote:Gonna ask this one more time since it didn't get a reply.
Wouldn't just turning the appropriate rubberbanding back on from before the boost to 400m fix everything?
I'm guessing this isn't as easy as just flipping a switch. I have a feeling that boosting the points did a reset on a number of values (including the rubberband values) that they weren't expecting. If that's the case, there might not be a way to get the previous values back.
It took almost no time to change the rubberbanding to limit progression so I highly doubt that's the case.I imagine it would take similarly little effort to, say, put a time limit on this sub, give rewards then restart the entire event without screwing it up.
If it IS a lot of effort to sort out a decent solution then they need to learn to code properly.
I assume they don't want to deal with people complaining about HP and/or ISO thhey have spent on health packs, boosts and cover packs for the event so far if it's reset and those dollars are far more important that decent, fair game design...0 -
If D3 can't or won't reset the whole event (and I still haven't seen any good reason from them why they can't (though I bet it has to do with money)), why can't they allow anyone who wants to to drop their overall bracket and join a new one? That would solve everything.
I recognize that, proportionally, they would then be handing out more covers, which hurts the bottom line, but guess what? YOU TINYKITTIED UP. Expecting that a mistake will cost you nothing is delusional.0 -
bonfire01 wrote:mags1587 wrote:
I'm guessing this isn't as easy as just flipping a switch.
It took almost no time to change the rubberbanding to limit progression so I highly doubt that's the case.
You forget that they were in a hurry to change it in the first place because progression rewards were about to flood the player base too quickly. Now that barely anyone's going to get progression rewards any time soon, they're not in a rush anymore.0 -
Okay, so I joined the event (waited to avoid these brackets with people having way too much point already) and it makes a lot more sense now that I can see how the structure works out.
The main bracket missions are far too low in points at the moment to make up for a 4K or so lead. If they remain unrepeatable, they'd have to go up to about 500 base points. Essentially, you'd have to overwhelm the sub points with main bracket points to balance this out if there's no repeatable nodes.
If the nodes are repeatable, you can probably reduce the base point value of the main bracket by 1/2.
Another solution is increase the total needed to unlock the bracket from 400M to 800M. Currently the progress is at 27% so it looks like it'll be completed in maybe 3 refreshes, and that isn't enough time for the rubberbanding to take care of itself. Double the amount of points needed to clear this would give more time for the rubberbanding to kick in.0 -
At this point, it seems unlikely that they'll do a reset.
And if that's true, I honestly think the best solution is to give everyone participates free 3* Daken covers.
As people have mentioned, that's basically what they did for the Hulk event. (As well as for the Ares event, although he's only a 2*.) People feel cheated. We're all after fairness, but we're all also after Daken. And I'm pretty sure that 99% of us would chill out if we were guaranteed Daken covers.0 -
I only joined early because alliance member told me first sub was almost over. Totally would have waited if I knew this **** was going to happen.0
-
Knock3r wrote:bonfire01 wrote:mags1587 wrote:
I'm guessing this isn't as easy as just flipping a switch.
It took almost no time to change the rubberbanding to limit progression so I highly doubt that's the case.
You forget that they were in a hurry to change it in the first place because progression rewards were about to flood the player base too quickly. Now that barely anyone's going to get progression rewards any time soon, they're not in a rush anymore.
I think you'll find the change to rubber banding was INTENTIONAL. It is not a by-product of another change. The top progression reward is 50k but ppl already reached 10k so were gaining points way too fast. They then increased the cap to 400m AND ALSO nerfed the hell out of the rubberbanding BUT have done nothing to redress the fact that it has disadvantaged a LOT of players.
IceX then comes along and tells us don't worry, you can grind and GRIND AND GRIND to hopefully catch up with the borked rubber banding OR you can somehow catch right up on a few main bracket nodes which will apparently make a 5k lead from subs irrelevant.....0 -
mouser wrote:The problem was someone thought the switch would only change that variable. When what happened is it shifted other variables in the event as well. At the very least the rubberbanding. Unable to tell if it changed the base node values or anything else at this point.
I do not think the rubber banding changed at all I think this is what happened.
Sub was going to finish in 9 hours. But they want it to run for about 2.5 to 3 days (I am assuming 2 subs for this event) so they needed to extend it by a factor of 6.
Now one possibility was to sub push the sub total from 200M to 1200M but that would mean everyone would get progression rewards and thats a no no.
So what happened they doubled the Sub total required and cut the mission points by 1/3 making it look like the rubber band got changed.
I started the long road of overhauling the 9K I was behind the leader. I am just glad I was not trying for number 1. Top 100 should be fine but top 20 might be a push.0
Categories
- All Categories
- 44.8K Marvel Puzzle Quest
- 1.5K MPQ News and Announcements
- 20.2K MPQ General Discussion
- 3K MPQ Tips and Guides
- 2K MPQ Character Discussion
- 171 MPQ Supports Discussion
- 2.5K MPQ Events, Tournaments, and Missions
- 2.8K MPQ Alliances
- 6.3K MPQ Suggestions and Feedback
- 6.2K MPQ Bugs and Technical Issues
- 13.6K Magic: The Gathering - Puzzle Quest
- 503 MtGPQ News & Announcements
- 5.4K MtGPQ General Discussion
- 99 MtGPQ Tips & Guides
- 421 MtGPQ Deck Strategy & Planeswalker Discussion
- 298 MtGPQ Events
- 60 MtGPQ Coalitions
- 1.2K MtGPQ Suggestions & Feedback
- 5.6K MtGPQ Bugs & Technical Issues
- 548 Other 505 Go Inc. Games
- 21 Puzzle Quest: The Legend Returns
- 5 Adventure Gnome
- 6 Word Designer: Country Home
- 381 Other Games
- 142 General Discussion
- 239 Off Topic
- 7 505 Go Inc. Forum Rules
- 7 Forum Rules and Site Announcements