|
|
#1 |
|
Join Date: Jun 2012
Reputation: 0
Posts: 2
|
Where are we supposed to report bugs and whatnot?
I have been enjoying many aspects of the game, but a few things are very frustrating.
1. I can't respond to some activated and/or triggered abilities. Pyre Charger, for example, gets +1/+0 as soon as Chandra pays its R mana. 2. Soul Warden's trigger doesn't seem to actually go on the stack. In fact, it seems to happen upon casting the spell. I noticed Ajani's Pridemate growing from the Soul Warden even though I Canceled the creature spell that was cast. 3. I couldn't Hydrosurge my own creature in order to make a Drake with Talrand. When I clicked the spell to cast it (while my opponent had no creatures), the game just gave me an error message that it was calculating or thinking or something, and the timer continued to pass. 4. The timing of triggers and state-based actions didn't apply properly in the following scenario: I attacked with a Knight of Meadowgrain equipped with Loxodon Warhammer, and my opponent (Chandra) blocked with Magma Phoenix. The first strike damage caused me to gain life and put me above 30. The Phoenix died, and my Serra Ascendant visually changed from 1/1 to 6/6 (as expected). In the graveyard, the Phoenix's trigger went on the stack, and when it resolved, every creature died. The Serra Ascendant had no other damage and should not have died. These are pretty frustrating and unexpected aspects of this game. It's important to know the rules of a game before playing in order to play properly. When I have to play against certain enemies multiple times just because the game doesn't support proper play, things are not okay. If there are changes to the rules of Magic for the purposes of Duels 2013, those changes should be documented and made readily available. ~ |
|
|
|
|
|
#2 |
![]() Join Date: Jan 2012
Reputation: 4
Posts: 30
|
If ya go into the settings, there are some check boxes on the last two tabs for your perusal. One of them is Auto Resolve, unchecking that will help you out (for example, Pyre Charger with have one of those timer bars for each +1/+0 added). I heard it's kind of messed up in multiplayer though, and uses different players' settings for different things (so if another multiplayer has Auto Resolve on, his Pyre Charger won't do that). Hearsay though, as I haven't looked myself.
Basically all the settings default to an easier style. It's almost like uncheck all the checked ones, and check all the unchecked ones then you're good to go haha! |
|
|
|
|
|
#3 |
![]() Join Date: Jun 2011
Reputation: 29
Posts: 807
|
Last edited by Nretep: 06-22-2012 at 01:37 AM. Reason: list end tag was missing |
|
|
|
|
|
#4 |
|
Join Date: Jun 2012
Reputation: 0
Posts: 2
|
It sounds like I need to change my settings to respond to triggers and to perform seemingly negative effects on my own stuff. Thanks for the tips about those settings!
And I'm not totally sure about the Soul Warden situation. I'll have to pay more attention next time I have counterspells against the Warden. However, the Serra Ascendant situation is not working properly. Magma Phoenix's trigger triggers from the graveyard if it came from the battlefield. This is working properly, and the game correctly shows the card in the graveyard triggering. Serra Ascendant's ability is a static ability, meaning it applies at all times without requiring a trigger or even a state-based action. The layering system should constantly update the creature's power and toughness (and presence of flying). As soon as the Knight of Meadowgrain deals its first strike damage (or even regular-strike damage), the Ascendant is a 6/6 (because the lifelink of the Knight causes damage and life-gain to occur simultaneously). Technically, the Ascendant is 6/6 before the Phoenix hits the graveyard–the Phoenix only dies from a state-based action, but the Ascendant's power and toughness are applied continuously through layers. 1. Knight deals damage, causing my life to go up and the Phoenix to have damage marked on it. (Ascendant is now 6/6 because of the life-gain.) 2. State-based actions put the Phoenix in the graveyard. 3. Phoenix triggers from the graveyard. 4. Phoenix's ability resolves, dealing 3 damage to everything. 5. State-based actions put into the graveyard creatures with enough damage marked on them. (Ascendant is fine; it's been a 6/6 for a long time now.) Note that visually, Steps 1, 2, and 3 are the same to the end user. And the client correctly showed the Ascendant as a 6/6 at that point, but for whatever reason, the Phoenix's trigger's resolution killed it. It was almost as though the game had predecided what creatures the trigger was going to kill. ~ |
|
|
|
|
|
#5 |
![]() Join Date: Jun 2011
Reputation: 29
Posts: 807
|
Sry, I mistook Ascendant with the blue card which becomes 6/6 witht he amount of cards in graveyard. And there MagmaPhoenix would win due to triggering before it lands on graveyard.
In your situation I suppose everything worked as intended (not even showing wrong informations). You gained life with a life leech effect which killed the phoenix. So Ascendant instantly became 6/6 and MagmaPhoenix resolves his ability. The ability put 3 damage on Ascendant and 3 damage on you. The 3 damage on yourself reverted Ascendants effect and turned it into 1/1 with 3 damage. |
|
|
|
![]() |
|
||||||
| Thread Tools | |
| Display Modes | |
|
|