[fixed/closed]Quicksand can't be activated when...

[Gargaroz]

Well, until you'll get back and look more precisely into int, the current matters is : which bug we'll leave in the upcoming patch.
I vote for the one reported by Orion, as the ones introduced by its fix seems a more serious one.
But before making the final cut, I'll wait some more feedbacks.

[Aswan jaguar]

Certainly the bug we have now is more serious and more cards and plays are affected but it can be fixed if people manage to put stops to "fast effects assign attackers" and "fast effects assign blockers" then you can activate any of these cards without a problem.
The only problem is that:
1a- We have to make a BIG NOTE in the patch forum in the update post to inform people what they have to do to overcome the problem so we don't here about such bugs.And hope that people will read it as we know some people hate to read instructions and will just download and try.

NOTE :
1- The first time you load the game and play the first duel as soon as the duel begins you have to put a STOP to BOTH attack phases (so that will give you the chance to put stops "fast effects assign attackers" and "fast effects assign blockers") as it will open the attack phase menu when you come to that step.
2- Then as soon as you put the stops in the fast effects you can remove the stop from the attack phases so it doesn't stop there if there are no creatures to attack,for players attack phase this works great for AI's phase it will not stop on "fast effects assign attackers" step though only to "fast effects assign blockers".

[Gargaroz]

Well, apparently reverting to previous EXE version also re-introduced a problem with the "name legacies" (Isochron Scepter, Meddling Mage and such), so we'll definitely keep the land bug. AJ, I'll add your notes in the upcoming release

[Aswan jaguar]

Just note that I found that in fact you only need to put stops 1 time then the program remembers your choices even if you close it,so I will change my previous note to that.So not so much off a problem with this bug.

[Korath]

Patch reverted and the original problem fixed more narrowly in ee91a88.