I have just discovered that The support created by Teferi, MOT’s 3rd ability does not consider matching loyalty gems as a match.
Now, that was a surprise! Since the data push “effects may cease to trigger” so it is difficult to know when something is a new bug, an old or WAD.
Having gone through the zendesk there is nothing that clearly define this simple mechanism in MTGPQ. Therefore, shall we make a joint effort in creating a common description of what constitutes the meaning of the game term “Match”?
1st version.
Match - to line up any 3 or more gems on the gem board. Any effect that refers to a match will trigger when making (a specific coloured) match.
2nd version.
Match - when a player switch position of two gems on the gem board, in order to create one or more lines of at least 3 gems on the gem board. Any effect that refers to a match will trigger when making a match.
@critman - fair enough. That was my best description since English is not my primary language. The important part of defining fundamentals is to remember that this is the whole foundation which the rest of the game is founded on. So it had to be precise.
The funny thing is that the devs are using fundamental definitions, but they haven’t written them down, (The players can’t see them anyways) which I conclude is the main reason for the huge amount of bug they produce. Not out of malice or incompetence, simply due to assuming slightly different than the next developer.
@TomB - Good example. Which is illustrates my point above about slightly different assumptions by each developer.
So maybe HW is doing it correctly and Teferi, MOT is also doing it correctly, sadly due to missing terms, both effects use the same term to describe different things. No wonder the players and the devs can’t understand the correct behaviour from one card/PW to the next.
I find the gem matching secondary on the top node of ATV to be another example of the inconsistency of swapping rules, since it seems like it only counts gems you swap directly and not the stuff that matches during cascades, or gem changing from land supports, etc.
Hi everyoneSorry about the delay in answering this!
I was investigating what was the case to see how to proceed.
I will provide an explanation about “what constitutes a match” according to what happened lately that caused these misunderstandings.
We apologize for the delay in bringing this here!
I’m working on this with one of our Game Designers and we don’t want to let anything pass by unnoticed.
Also, he’s always super busy so we are trying to gather around as much as we can, but it’s not always possible!
But thank you so much for the interest, and for your patience!
Marcela.
I notice we never got an answer. Not sure how it’s SUPPOSED to work, but if anyone’s confused, matches only count in DvK if you match the gems yourself. Cascades don’t count. Matches made during gem conversion don’t count. It’s asinine. But that’s what it is.
You’re right, @Narcoticsagent , they did answer the question but it seems like it’s still not working right since they said A match can happen either by a swap, a cascade or by converting gems, and that’s clearly still not happening…
@TomB - thank you for inserting the answer from the Q&A, that was on my todo list for today.
Completely true that the DvK objective is still not counting correctly, but now we know that is a bug, which we didn’t the last time we encountered this problem, so I think that is good we now know that it is a bug.
Now we just have to report yet another bug on the bug forum. Sigh!
