Current Known Bugs list

[silly freak]

just change the declaration

Code: Select all

int value;

on line 150 to

Code: Select all

Integer value;

Then it should be fine.

[Resonantg]

If 2 copies of Volrath's Stronghold come into play, both it leave play instantly.

They should do that, it is a legendary land, there cannot be 2 in play at the same time.

Ah HAH! I did not know that. My bad.

New bugs found (Possibly reported beforehand)

1. Black Lotus - If during casting you make a mistake in casting, and you have to hit cancel, you lose the mana as it does not go to your mana pool, and since it's sacrificed, it cannot be redone. Isn't it the case that if you have to cancel mid casting, the sacrificed card should come back till you reconfigure? Or is this an error on IRL gameplay, sort of a 'sucks to be you' penalty?

2. Fastbond and Exploration do not let you lay extra land.

3. Blocking of fliers with instants on ground based cards. You cannot target a card during the 'declare blockers' phase with an instant (as you should be able to, IIRC). Example, I want to have my Relentless Rats block an Azure Drake. So when it is declared an attacker, I cannot use an instant to allow my Relentless Rats to fly, thereby making them eligible to block the Azure Drake. Once you are past the "declare blocker" phase, you cannot use the instant to make any card able to block. May I suggest being able to play instants and interrupts during the computer's 'declare attacker' phase, or allow it to happen during my 'declare blockers' phase? Another option would be to allow non-fliers to 'block' but would not stop the attack if they did not have the ability to fly.

4. AFAIK, isn't summoning sickness over when my turn is done and therefore allow my newly summoned creatures the ability to block?

Those are the most recent issues I've spotted. The 3rd is possibly the most annoying because it's caused me to not be able to use a basic strategy of the game, aka surprise blockers with cards like silk web or jump or any other 'till the end of turn' surprises.

Just doing my part to help.

[DennisBergkamp]

1. Ah yes, currently abilities that go to the manapool directly can't be canceled. Same deal with Black Lotus.

2. Currently, the only way to use Exploration / Fastbond is to click on them, then select a land to play from the list.

3. This should be fixed in the next version
EDIT: there will be 2 extra phases: one before attackers are declared (during which cards like Benalish Trapper can be used to tap potential attackers), and one right after attackers are declared (where creatures with flash can be played as a surprise block, or where a creature can gain flying, etc. etc.) .

4. I'm not sure I follow... even cards that still have summoning sickness should be able to block (they just can't attack or use tap abilities). What happened exactly?

[Resonantg]

4. I'm not sure I follow... even cards that still have summoning sickness should be able to block (they just can't attack or use tap abilities). What happened exactly?

--Okay. best explanation. When I summon a creature, it has summoning sickness which affects it's ability to attack and use it's abilities till the end of my turn. When completed, summoning sickness goes away with the first untap phase after my turn. THat means I should at that point be able to use a Winter's Orb (although we don't have one yet) to tap a card at the untap phase, if I so chose. (why I would do this before the Draw phase, I've no idea). Maybe this is just an old school thing from those of us who played back when Ice Age was new and what not, but tapping creatures was a huge defense. Many a time I remember an opponent say I'm going to cast a spell, and I'd tap a a critical piece of land or tap his big creature so he couldn't kill me off.

Currently with MtG Forge, a creature has summoning sickness until MY next untap phase. Maybe it was a rules change in later years, and if so, I've nothing I can say other than boy that was dumb of them.

So, hope this clarifies.

[Mr.Chaos]

4. I'm not sure I follow... even cards that still have summoning sickness should be able to block (they just can't attack or use tap abilities). What happened exactly?

--Okay. best explanation. When I summon a creature, it has summoning sickness which affects it's ability to attack and use it's abilities till the end of my turn. When completed, summoning sickness goes away with the first untap phase after my turn. THat means I should at that point be able to use a Winter's Orb (although we don't have one yet) to tap a card at the untap phase, if I so chose. (why I would do this before the Draw phase, I've no idea). Maybe this is just an old school thing from those of us who played back when Ice Age was new and what not, but tapping creatures was a huge defense. Many a time I remember an opponent say I'm going to cast a spell, and I'd tap a a critical piece of land or tap his big creature so he couldn't kill me off.

Currently with MtG Forge, a creature has summoning sickness until MY next untap phase. Maybe it was a rules change in later years, and if so, I've nothing I can say other than boy that was dumb of them.

So, hope this clarifies.

Summoning sickness lasts until the beginning of YOUR next turn.
So if you play a creature on your turn, it has summonoing sickness until your next turn begins.
Therefor, you cannot use it for anything other than blocking during your opponent's turn(s).
To my knowledge, this is, and always has been, the way summoning sickness works.

MTG Forge handles summoning sickness correctly.

Non-creature artifacts have no summoning sickness and can be used immidiately, unless they come into play tapped or have specific rules written on them.

[apthaven]

To add on to what has been said, giving something haste irregardless of the timing, gets rid of summoning sickness for as long as that creature has it.

[Marek14]

4. I'm not sure I follow... even cards that still have summoning sickness should be able to block (they just can't attack or use tap abilities). What happened exactly?

--Okay. best explanation. When I summon a creature, it has summoning sickness which affects it's ability to attack and use it's abilities till the end of my turn. When completed, summoning sickness goes away with the first untap phase after my turn. THat means I should at that point be able to use a Winter's Orb (although we don't have one yet) to tap a card at the untap phase, if I so chose. (why I would do this before the Draw phase, I've no idea). Maybe this is just an old school thing from those of us who played back when Ice Age was new and what not, but tapping creatures was a huge defense. Many a time I remember an opponent say I'm going to cast a spell, and I'd tap a a critical piece of land or tap his big creature so he couldn't kill me off.

Currently with MtG Forge, a creature has summoning sickness until MY next untap phase. Maybe it was a rules change in later years, and if so, I've nothing I can say other than boy that was dumb of them.

So, hope this clarifies.

Summoning sickness lasts until the beginning of YOUR next turn.
So if you play a creature on your turn, it has summonoing sickness until your next turn begins.
Therefor, you cannot use it for anything other than blocking during your opponent's turn(s).
To my knowledge, this is, and always has been, the way summoning sickness works.

MTG Forge handles summoning sickness correctly.

Non-creature artifacts have no summoning sickness and can be used immidiately, unless they come into play tapped or have specific rules written on them.

Also, Winter Orb doesn't tap things... it prevents them from untapping. Perhaps you meant Icy Manipulator? But that has nothing to do with summoning sickness...

If your opponent says that he's casting a spell, it's too late to tap some lands so he didn't have enough mana to cast it. But a creature can be tapped any time up to "beginning of combat" step if you want to stop it from attacking, and any time up to "declaring attackers" step if you want to stop it from blocking.

Tapped blockers still deal damage, btw (one of the changes in 6th edition), so tapping a creature after it's declared as a blocker is usually worthless.

[Resonantg]

Cool. My bad again. I guess me and the guys I've played with (even a few local tournaments years ago) had been playing summoning sickness wrong.

Thanks for the clarification.

[Resonantg]

Perhaps you meant Icy Manipulator?

THAT'S the one! :c)

<<<Mistake riddled idiot last night.

Some interesting rule changes too.

[indicatie]

Perhaps you meant Icy Manipulator?

THAT'S the one! :c)

<<<Mistake riddled idiot last night.

Some interesting rule changes too.

Have you read the Magic 2010 rules changes? Now THAT's a change!
Mana-burn? Gone!
Choosing how a blocked creature deals damage? Gone!
Using fast-effects when combat damage is on the stack? Gone!

Good luck adjusting to the new world order....

[Rob Cashwalker]

Well that was just mean.... Rip the man's heart out why don't ya?

The rules changes did not come up a single time this past friday when I attended FNM for the first time since 2010 released.

Oh, and you can use "fast effects" before combat damage, it just doesn't use the stack, which is actually closer to how Magic worked back in the day, before there was a stack.

[Marek14]

Oh, and you can use "fast effects" before combat damage, it just doesn't use the stack, which is actually closer to how Magic worked back in the day, before there was a stack.

Huh??? What do you mean? The ordering of blockers, the damage assignment or something else?

[Niv-Mizzet]

What he means is that under M10 rules, combat damage no longer uses the stack. You can still cast spells or use abilities at almost all of the same times: before attacks are declared, before blockers are declared, before damage is assigned, and after damage is assigned. The only thing that's different is you can no longer play effect between combat damage being assigned, and its actually being dealt, like under 6th Ed rules.

For the most part all this does is make creatures that sacrifice for an effect weaker. A Mogg Fanatic used to be able to kill a 2/2 blocker since it could put its 1 combat damage on the stack and sac for another damage before that damage was dealt. Now you can only do one or the other, since combat damage happens instantly, and you can't respond to it.

[Marek14]

What he means is that under M10 rules, combat damage no longer uses the stack. You can still cast spells or use abilities at almost all of the same times: before attacks are declared, before blockers are declared, before damage is assigned, and after damage is assigned. The only thing that's different is you can no longer play effect between combat damage being assigned, and its actually being dealt, like under 6th Ed rules.

For the most part all this does is make creatures that sacrifice for an effect weaker. A Mogg Fanatic used to be able to kill a 2/2 blocker since it could put its 1 combat damage on the stack and sac for another damage before that damage was dealt. Now you can only do one or the other, since combat damage happens instantly, and you can't respond to it.

Ah - I thought he was saying the effects don't use the stack

[indicatie]

This is what happened when a tried to play a hybrid card (Gilder Bairn) from my mana pool with UU1 in it...

Code: Select all

An error has occured. You can copy/paste this message or save it to a file.
Please report this, plus what you tried to do, to:
   http://www.slightlymagic.net/forum/viewforum.php?f=26
If you don't want to register an account, you can mail it directly to
   mtgrares@yahoo.com

G/Uisn't an indexable single character.

Detailed error trace:
java.lang.IllegalArgumentException: G/Uisn't an indexable single character.
   at ManaPool.cIndex(ManaPool.java:13)
   at ManaPool.subtractOne(ManaPool.java:239)
   at ManaPool.subtractMana(ManaPool.java:222)
   at Input_PayManaCostUtil.tapCard(Input_PayManaCostUtil.java:10)
   at Input_PayManaCost.selectCard(Input_PayManaCost.java:43)
   at GuiInput.selectCard(GuiInput.java:35)
   at GuiDisplay3$8.mousePressed(GuiDisplay3.java:309)
   at java.awt.Component.processMouseEvent(Unknown Source)
   at javax.swing.JComponent.processMouseEvent(Unknown Source)
   at java.awt.Component.processEvent(Unknown Source)
   at java.awt.Container.processEvent(Unknown Source)
   at java.awt.Component.dispatchEventImpl(Unknown Source)
   at java.awt.Container.dispatchEventImpl(Unknown Source)
   at java.awt.Component.dispatchEvent(Unknown Source)
   at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
   at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
   at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
   at java.awt.Container.dispatchEventImpl(Unknown Source)
   at java.awt.Window.dispatchEventImpl(Unknown Source)
   at java.awt.Component.dispatchEvent(Unknown Source)
   at java.awt.EventQueue.dispatchEvent(Unknown Source)
   at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
   at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
   at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
   at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
   at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
   at java.awt.EventDispatchThread.run(Unknown Source)