Wagic/Bugs0101
From Miki
This page lists the bugs in Wagic 0.10.1. Bugs that are already fixed in the SVN version are displayed in green. Information is current as of ...
- Bugs forum: known bugs up to 12/23/09.
- Bug Tracker: bugs and fixes up to ?
- Source Code: Fixes up to r1612
Please also check the links above for additional information. For bugs in the SVN version of Wagic, please use the bug tracker
If you are looking for the list of bugs fixed by this release, check the green lines in Wagic/Bugs091
Contents |
General Game issues
- Options: (Windows/Linux) Audio volume is either 0 or 100%, other values actually put the volume at 100%.
- Buttons for "interrupt" and "go out of graveyard" conflict
- Vertical closed hand: Sometimes you can't navigate to the cards in your hand. Opening and re-closing the hand (pressing R twice) solves the issue.
PSP Specific issues
- The PSP was reported to crash whenever 75+ or more mana were produced in one turn. The user who reported this had mana display on "Both" and sound effects switched on.
MTG General Rules/abilities issues
- Mulligan is not implemented
- Game Phase issues: You can play spells in phases that shouldn't allow it.
- Blocking modifiers: when using cards like: auto=target(creature[blocking]) 4/4, you can put your creature into "block mode", give it +4/+4, then remove it from combat - and it will still have the +4/+4 modifier.
- Creatures which can't attack alone, can't block alone, or have similar limitations, can circumvent their limitation by first choosing another attacker/blocker, then legally choosing the creature with the limitation as attacker/blocker, and then removing the first creature as attacker/blocker.
- Exalted should be a triggered ability
- Regenerate does not protect from Cockatrice-type effects
- Retrace is not implemented
- Assigning Trample damage may crash the game.
- Auras/effects that add an ability/remove it don't correctly stack. For example, casting Pacifism on a blind spot giant, then having a giant coming into play will not have the expected result. Another example is if you have two goblin kings in play and one gets killed: some goblins will not have mountainwalk anymore.
- Tokens don't go to the graveyard although they should (they then should get removed from the graveyard as a state-based action). The difference is that tokens should trigger "whenever a creature goes to the graveyard ..." and similar triggers, which they currently don't.
Specific Card issues
- Bloodhall Ooze receives an additional +1/+1 counter, outside of upkeep, if it has been on the battlefield for at least one turn, and a green or black creature gets summoned. This only affects the first Bloodhall Ooze (if you have several) and only affects it once.
- Bravado gives incorrect bonus if cast on an opponent's creature (but works correctly if cast on one's own creature, which you usually want to do with this card).
- Clone and similar cards cause an endless loop when the AI tries to cast them.
- Consume Spirit can use non-black mana.
- Cursed Land (RV) may trigger in the wrong player's turn.
- Drain Life can use non-black mana.
- Fallowsage (LRW) allows endless card drawing and loops the AI.
- Kjeldoran Frostbeast (ICE) functions like a Basilisk or Cockatrice in Wagic. This is not entirely correct, it should only destroy creatures that it's actually blocking (or being blocked by) at end of combat.
- Pillory of the Sleepless (GPT) may trigger in the wrong player's turn.
- Shield of the Ages (ICE) doesn't prevent any damage.
- Siege-Gang Commander works, but the sequence of commands is redundant. You have to (1) tap the necessary mana, (2) click on Siege-Gang commander, (3) specify a target, (4) click on a goblin to sacrifice, (5) specify the target again. The same is true for similar cards, like Golgari Rotwurm.
- Casting Spirit Link on an opponent's creature causes the opponent to gain life rather than me.
- Stern Marshal (POR): Ability can be activated anytime in your turn.
- Sylvan Basilisk (10E) destroys creatures blocked by it, and receives damage from creatures blocking it.
Legend
In green : Bugs that should be fixed in next release
In blue: Bugs that couldn't be reproduced in current development version. This could mean that another bugfix fixed them without us noticing it, or that the bug never existed, or that the bug is a side effect of something else that cannot be tested easily. In that case, if you have that bug and know a way to reproduce it, please shout. :)
