Bugs That I Have Encountered

doan113

So while playing I have found some bugs in the client version 2.9.0.26959. I will use a format that has a topic, how to recreate, expected outcome, real outcome and additional notes about the bug in question.

Edit 1: So it turns out first and second one are in the known bugs list and under investigation. However others are not.

1)
Title: Perilous Voyage is not castable when opponet's first creature has hexproof.

How to Recreate: Opponent has a hexproof creature in their first creature slot. Player has Perilous Voyage with full mana and not disabled. Perilous Voyage has red mark that states it is uncastable.

Expected Outcome: Perilous Voyage is castable and returns opponent's first creature with hexproof to their hand.

Real Outcome: Perilous Voyage is uncastable and stays in players hand. Opponent's creature remains on the battlefield.

Additional Notes: Hexproof states that spells that have "target" keyword in it cannot target the creature with hexproof. Perilous Voyage does not have the keyword "target" in it's text. Instead it states "first creature your opponent controls" which in MTG terms does not targets the creature but the player. Therefore it should be castable regardless of the hexproof tag of the first creature.


2)
Title: Mantle of Webs is not castable when player has only Vine Mare on the battlefield.

How to Recreate: Opponent has no creatures. Player has only Vine Mare (has hexproof) on the battlefield under their control. Mantle of Webs is in payer's hand with full mana and not disabled. Mantle of Webs has red mark that states uncastable.

Expected Outcome: Mantle of Webs is castable on Vine Mare and gives it +1/+3 and reach.

Real Outcome: Mantle of Webs is uncastable and stays in hand. Vine Mare does not get +1/+3 and reach.

Additional Notes: I have only encountered it with this two cards but it may have more general applications that need testing. Mantle of Webs is castable on Vine Mare if the player has a second creature that has no hexproof.


3)
Title: Reinforced Gilded Lotus supports give Ob Nixilis, Reignited additional blue mana bonus passing initial +1.

How to Recreate: Player enters a game with Ob Nixilis, Reignited. Player plays their first Gilded Lotus support. All mana bonuses increased by one. Player plays second Gilded Lotus to reinforce the initial one. Green, White, Black, Red and Loyalty mana bonuses remain same except Blue mana bonus being increased an additional +1.

Expected Outcome: Each reinforcement of Gilded Lotus does not increase the mana bonuses over the initial +1.

Real Outcome: Each reinforcement of Gilded Lotus increases Blue mana bonus with +1 while others does not get any additional +1 bonuses as intended.

Additional Notes: This effect stacks for each reinforcement of Gilded Lotus. Therefore reinforcing Gilded Lotus N times result with +N additional Blue mana bonus.



4)
Title: Hungering Hydra gets unintended +X/+X when played or directly put on the battlefield via an effect as a reinforcement it gets +X/+X of the initial Hungering Hydra on the battlefield.

How to Recreate 1: Player has a Hungering Hydra on the battlefield which is previously played with full stored mana which is 5. Player has a Hungering Hydra in their hand with full mana but not full stored mana. Hungering Hydra in player's hand is not disabled. Player plays Hungering Hydra as a reinforcement. Hungering Hydra on the battlefield gets +3/+3 due to initial stats of the creature then it gets +5/+5 where it is not the stored mana count of the played creature and is the stored mana count of the initial creature on the battlefield.

How to Recreate 2: Player has a Hungering Hydra on the battlefield which is previously played with full stored mana which is 5. Player has a spell that puts creatures from library on to the battlefield in their hand with full mana and not disabled (e.g. Vivien's Invocation). Player plays the spell to put Hungering Hydra on the battlefield as a reinforcement. Hungering Hydra on the battlefield gets +3/+3 due to initial stats of the creature then it gets +5/+5 where it is not the stored mana count of the creature that is put on to the battlefield (which is zero) and is the stored mana count of the initial creature on the battlefield.

Expected Outcome: Hungering Hydra played/put on to the battlefield as a reinforcement should increase the stats of the initial creature on the battlefield with +3/+3 as its own stats then it should increase the stats of the creature in line with the stored mana count of the played/put on the battlefield creature.

Real Outcome: Initial Hungering Hydra (played with maximum stored mana) on the battlefield gets +3/+3 for the played/put on the battlefield reinforcement due to the stats of the creature then it gets +5/+5 disregarding the stored mana count of the played/ put on the battlefield reinforcement.

Additional Notes: I could not be able to test it without full stored mana for the first Hungering Hydra.


5)
Title: Hungering Hydra cannot be played when has full mana but zero stored mana.

How to Recreate: Player has Hungering Hydra has full mana (after swap) but zero stored mana and is not disabled. Hungering Hydra has red mark that states it is uncastable.

Expected Outcome: Player can cast Hungering Hydra with zero stored mana. Resulting with 3/3 Hungering Hydra on the battlefield with out any additional buffs.

Real Outcome: Player cannot cast Hungering Hydra with zero stored mana. Hungering Hydra remains in player's hand.

Additional Notes: None.

Monkeynutts

A the devs say they have a QA team hahaha