Legacy Cards in Standard Format Exploit (10/1/18)
Comments
-
One of the event rules states that Standard comprises of HOU block, KLD block, and Origins. The text on these is very obviously not up-to-date.
The event has a legacy ribbon. Legacy cards are allowed. That ribbon is dependent on the event type, even if it appears to have been erroneously defined as such. Standard events don't have that ribbon, and don't allow a deck to be built as such. Exploiters got around this in multiple standard events.
The mental gymnastics here are absolutely mind blowing.
I mean, we could dump this onto the mountain of "unclear text in mtgpq", honestly9 -
octal9 said:
I mean, we could dump this onto the mountain of "unclear text in mtgpq", honestly
Now we get to argue over proper interpretations because these things are really important (even though Oktagon has clearly stated that they think text issues are low priority)5 -
Mburn7 said:Sarahschmara said:This is being handled incredibly poorly by D3Go.
I think letting people do what they were doing while they track it without telling people they are is exactly what they needed to do in order to accurately collect data regarding who was cheating and with what frequency. The game doesn’t need to be your mother and remind you cheating is bad. That’s something anyone playing the game should really know already.
I think launching it as a “surprise! Everyone who was cheating is getting punished” is exactly the right message to send. If they handled it any differently, people would think they weren’t serious, and that future actions might not be punished.0 -
wereotter said:Mburn7 said:Sarahschmara said:This is being handled incredibly poorly by D3Go.
I think letting people do what they were doing while they track it without telling people they are is exactly what they needed to do in order to accurately collect data regarding who was cheating and with what frequency. The game doesn’t need to be your mother and remind you cheating is bad. That’s something anyone playing the game should really know already.
I think launching it as a “surprise! Everyone who was cheating is getting punished” is exactly the right message to send. If they handled it any differently, people would think they weren’t serious, and that future actions might not be punished.
"Hey, we are aware there is a bug that might allow you to play legacy cards in standard. Please double check your event decks to ensure that all cards in it are legal for the event"
They don't have to threaten punishment, just make sure everyone is clearly aware that there is an issue to look out for. Then if they want to drop down punishment later nobody could complain, since we were all warned.
Instead, what happened was complete silence (in game and on the forums), and then a sudden "everyone who used the bug will be punished" with no clarification as to how they would determine who intentionally broke the rules and who did it by accident. That is what led to the debate starting, as players clamored for clarification and got none, and then started fighting over what they each think the determination should be.
We still have not received any clarification, just something saying that the punishments were already levied (again, with no in-game notification at all).
Now there is another event that may or may not have an issue, and again we are receiving absolutely no answers from either D3 or Oktagon.
To me, this is a crisis that is being handled very poorly, and I assumed everyone else felt the same way, regardless of which side of the debate they fell on.0 -
@octal9 these are not gymnastics to justify behavior. Rather my assertion is this:
The code itself must be the ultimate arbiter for what is allowed and not allowed. The only definition of exploit that makes any sense is running code that has been altered or modified in some way.
The reason I take this position is because I believe the development team must be accountable for what they produce and stand behind it.
I would argue this to be the sensible choice because there is no way to discern the intentions of the development team. This ROTGP problem is a prime example. Do they expect us to use legacy cards or not? They are so slow to communicate that we're all left to our own devices to figure it out.
The legacy cards in standard bug is another example. They called it out as a bug but did not explicitly tell us that the use of it was verboten. I ask, why is this particular bug, which gives you an advantage, any different than any other bug that gives you an advantage? I cited the Resilient Khenra bug as an example. These are not gymnastics, they are the logical arguments discussing why we must take a position that what the code allows us to do must be the intention and if they want to change it they need to patch the code not pontificate in the forums.2 -
And just to clear the air on some of this, I did not get caught "with my hand in the cookie jar." Nor am I trying to defend those who used this bug to their advantage. I do not feel they should need to be defended at all. There are things that Hibernum and Oktagon have done that have significantly warped the meta and I have been here for all of them.
I was here when Hibernum put out Runaway Carriage in an absurd form and suddenly everyone was running it. It sucked. It was definitely not what the developers intended and you can bet that people benefited from it in both placement and rewards.
If the instructions for this bug had been more widely known it would have warped the meta in the same way and it would have been a phase, it would have been patched, and it probably would have been a lot of fun.
These things that come up give this game color or flavor or whatever you want to call it. I love them! They make this game interesting and keep it from getting stale. I don't care one whit about winning a particular match or getting great rewards, though those things are nice and keep me trying hard. I care a lot more that this game continues to be around and have a vibrant community excited to play it.3 -
Hi everyone, my apologies for the late response. I've gotten confirmation that this event is intended to be a Legacy style event now.6
-
Tombstone said:Hi everyone, my apologies for the late response. I've gotten confirmation that this event is intended to be a Legacy style event now.
1 -
Unleash the Second Sun!4
-
GrizzoMtGPQ said:I was here when Hibernum put out Runaway Carriage in an absurd form and suddenly everyone was running it. It sucked. It was definitely not what the developers intended and you can bet that people benefited from it in both placement and rewards.
3 -
Thanks Tombstone, was about to play the event in standard and legacy at the same time, just to be sure! ;-)0
-
Sarahschmara said:Thank you for the information Brigby
Can you give us an idea of how widespread this was?
When you say that the rewards were removed from the players accounts, I assume you mean crystals, mana runes, and jewels but not cards (boosters). Is that correct? So the cheaters did still come out ahead?
Also, can you tell us how coalition rewards were affected by players using the exploit?
Mana Crystals, Mana Runes, and Mana Jewels were easy to remove, however cards are a bit more difficult. For the majority of offenders, the cards they received from boosters were duplicates, so we ended up removing the equivalent number of Mana Orbs instead.
As for coalition rewards, I'm afraid I don't know how that was specifically impacted.5 -
Brigby said:Sarahschmara said:Thank you for the information Brigby
Can you give us an idea of how widespread this was?
When you say that the rewards were removed from the players accounts, I assume you mean crystals, mana runes, and jewels but not cards (boosters). Is that correct? So the cheaters did still come out ahead?
Also, can you tell us how coalition rewards were affected by players using the exploit?
Mana Crystals, Mana Runes, and Mana Jewels were easy to remove, however cards are a bit more difficult. For the majority of offenders, the cards they received from boosters were duplicates, so we ended up removing the equivalent number of Mana Orbs instead.
As for coalition rewards, I'm afraid I don't know how that was specifically impacted.0
Categories
- All Categories
- 44.8K Marvel Puzzle Quest
- 1.5K MPQ News and Announcements
- 20.3K 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