Current Known Bugs list
by mtgrares
Moderators: timmermac, Blacksmith, KrazyTheFox, Agetian, friarsol, CCGHQ Admins
Re: Current Known Bugs list
by gos » 27 Oct 2011, 13:04
I have Iona, Shield of Emeria on the battlefield since last turn, with red chosen. My opponent just cast a Skirk Shaman! 

- gos
- Posts: 4369
- Joined: 03 Mar 2011, 15:21
- Location: Reykjavík, Iceland
- Has thanked: 231 times
- Been thanked: 232 times
Re: Current Known Bugs list
by Sloth » 27 Oct 2011, 13:28
Iona has been turned to script since the last beta.gos wrote:I have Iona, Shield of Emeria on the battlefield since last turn, with red chosen. My opponent just cast a Skirk Shaman!
-
Sloth - Programmer
- Posts: 3498
- Joined: 23 Jun 2009, 19:40
- Has thanked: 125 times
- Been thanked: 507 times
Re: Current Known Bugs list
by SoulStorm » 27 Oct 2011, 22:05
As of revision 11503 enter the battlefield triggers aren't working. Specifically, none of the legendary eldrazi enter the battlefield triggers are working.
Thanks
By the way, I tried to use the in game bug report tool, but it didn't work. Is it still a work in progress?
Thanks
By the way, I tried to use the in game bug report tool, but it didn't work. Is it still a work in progress?
Re: Current Known Bugs list
by gos » 27 Oct 2011, 22:41
The AI cast Agony Warp. I had 4 Squadron Hawk s on the battlefield, the AI had no creatures. One of my Squadron Hawk s received -3/-0 until the end of turn, but none received -0/-3. This happened twice in a row.
- gos
- Posts: 4369
- Joined: 03 Mar 2011, 15:21
- Location: Reykjavík, Iceland
- Has thanked: 231 times
- Been thanked: 232 times
Re: Current Known Bugs list
by goonjamin » 28 Oct 2011, 01:39
Slayer of the Wicked - The ability is may destroy target ... When I played this card I was forced to target one of my own cards as the AI had no valid targets and I did not see a way to cancel?
Re: Current Known Bugs list
by friarsol » 28 Oct 2011, 03:05
The targeting is required, but the actual trigger resolution is optional.goonjamin wrote:Slayer of the Wicked - The ability is may destroy target ... When I played this card I was forced to target one of my own cards as the AI had no valid targets and I did not see a way to cancel?
410.4. When a triggered ability goes on the stack, the controller of the ability makes any choices that would be required while playing an activated ability, following the same procedure (see rule 409, “Playing Spells and Activated Abilities”). If a choice is required when the triggered ability goes on the stack but no legal choices can be made for it, or if a rule or a continuous effect otherwise makes the ability illegal, the ability is simply removed from the stack.
410.5. Some triggered abilities’ effects are optional (they contain “may,” as in “At the beginning of your upkeep, you may draw a card”). These abilities go on the stack when they trigger, regardless of whether their controller intends to exercise the ability’s option or not. The choice is made when the ability resolves. Likewise, triggered abilities that have an effect “unless” something is true or a player chooses to do something will go on the stack normally; the “unless” part of the ability is dealt with when the ability resolves.
- friarsol
- Global Moderator
- Posts: 7593
- Joined: 15 May 2010, 04:20
- Has thanked: 243 times
- Been thanked: 965 times
Re: Current Known Bugs list
by moomarc » 28 Oct 2011, 06:08
friarsol wrote:The targeting is required, but the actual trigger resolution is optional.goonjamin wrote:Slayer of the Wicked - The ability is may destroy target ... When I played this card I was forced to target one of my own cards as the AI had no valid targets and I did not see a way to cancel?
410.4. When a triggered ability goes on the stack, the controller of the ability makes any choices that would be required while playing an activated ability, following the same procedure (see rule 409, “Playing Spells and Activated Abilities”). If a choice is required when the triggered ability goes on the stack but no legal choices can be made for it, or if a rule or a continuous effect otherwise makes the ability illegal, the ability is simply removed from the stack.
410.5. Some triggered abilities’ effects are optional (they contain “may,” as in “At the beginning of your upkeep, you may draw a card”). These abilities go on the stack when they trigger, regardless of whether their controller intends to exercise the ability’s option or not. The choice is made when the ability resolves. Likewise, triggered abilities that have an effect “unless” something is true or a player chooses to do something will go on the stack normally; the “unless” part of the ability is dealt with when the ability resolves.
Aside from the "may destroy target" cards, this also affects "may exile target", "may return target" and I'm sure there's more that I haven't thought of or don't use the exact string so don't show up with the deck editor filter.
Edit: Sorry, just double-checked and saw that the optional resolution of the trigger is already implemented. I've reverted the Slayer of the Wicked. Should I also remove the OptionalDecider from the other cards so that the targeting can't just be cancelled?
Edit 2: Did a final test after reverting back to original script and it turns out that the ability resolves without the player having a choice if optional decider is removed. So as things stand you can either have the optional decider for resolution but also allow the user to simply cancel the original targeting, or you have neither. The code needs to be adjusted to enforce the targeting but make the resolution optional. So I'm re-adding the optional decider to Slayer of the Wicked for now.
](./images/smilies/eusa_wall.gif)
-Marc
-
moomarc - Pixel Commander
- Posts: 2091
- Joined: 04 Jun 2010, 15:22
- Location: Johannesburg, South Africa
- Has thanked: 371 times
- Been thanked: 372 times
Re: Current Known Bugs list
by friarsol » 28 Oct 2011, 12:49
Ahh that seems wrong then. You should always be forced to pick a mode and pick targets if the right amount are available. That's fine for now until that gets fixed up.moomarc wrote:Edit 2: Did a final test after reverting back to original script and it turns out that the ability resolves without the player having a choice if optional decider is removed. So as things stand you can either have the optional decider for resolution but also allow the user to simply cancel the original targeting, or you have neither. The code needs to be adjusted to enforce the targeting but make the resolution optional. So I'm re-adding the optional decider to Slayer of the Wicked for now.
- friarsol
- Global Moderator
- Posts: 7593
- Joined: 15 May 2010, 04:20
- Has thanked: 243 times
- Been thanked: 965 times
Re: Current Known Bugs list
by SoulStorm » 28 Oct 2011, 14:19
Ok, the bug with the Legendary Eldrazi seems to be the SpellCast trigger, as ChangeZone triggers work fine. And to be clear, I'm talking about casting them, not cheating them into play in case someone thought I may have misread a rule.
Re: Current Known Bugs list
by Sloth » 28 Oct 2011, 15:09
Fixed! Thanks SoulStorm.SoulStorm wrote:Ok, the bug with the Legendary Eldrazi seems to be the SpellCast trigger, as ChangeZone triggers work fine. And to be clear, I'm talking about casting them, not cheating them into play in case someone thought I may have misread a rule.
-
Sloth - Programmer
- Posts: 3498
- Joined: 23 Jun 2009, 19:40
- Has thanked: 125 times
- Been thanked: 507 times
Re: Current Known Bugs list
by Evilelvis » 28 Oct 2011, 15:58
Hey, I just downloaded Forge for the first time, and I must say I'm impressed with the general quality 
I discovered a bug related to the card Earthquake - I had 4 mana (1R 2B 1G, one of the Bs was from Leaden Myr) and tried to cast it, I get asked to "Pay Mana Cost: R". Then I click the Mana Pool and I get the following exception:

I discovered a bug related to the card Earthquake - I had 4 mana (1R 2B 1G, one of the Bs was from Leaden Myr) and tried to cast it, I get asked to "Pay Mana Cost: R". Then I click the Mana Pool and I get the following exception:
- Code: Select all
This is a Crash Report. An error has occurred. Please save this message to a file.
Please follow the instructions at this address to submit this Crash Report, plus what you were doing at the time:
http://tinyurl.com/3zzrnyb
Reporting bugs in Forge is very important. We thank you for your time.
For input string: "X"
Version:
Forge version 1.1.6, build ID 11247
OS: Windows 7 Version: 6.1 Architecture: x86
Java Version: 1.6.0_24 Vendor: Sun Microsystems Inc.
Detailed error trace:
java.lang.NumberFormatException: For input string: "X"
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at forge.card.mana.ManaPool.getManaFrom(ManaPool.java:433)
at forge.card.mana.ManaPool.subtractOne(ManaPool.java:750)
at forge.card.mana.ManaPool.subtractMultiple(ManaPool.java:666)
at forge.card.mana.ManaPool.subtractMana(ManaPool.java:690)
at forge.gui.input.Input_PayManaCostUtil.activateManaAbility(Input_PayManaCostUtil.java:43)
at forge.card.cost.CostMana$2.selectCard(CostMana.java:234)
at forge.GuiInput.selectCard(GuiInput.java:83)
at forge.GuiDisplay4$18.mousePressed(GuiDisplay4.java:578)
at java.awt.AWTEventMulticaster.mousePressed(Unknown Source)
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.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$000(Unknown Source)
at java.awt.EventQueue$1.run(Unknown Source)
at java.awt.EventQueue$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source)
at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue$2.run(Unknown Source)
at java.awt.EventQueue$2.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(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)
- Evilelvis
- Posts: 3
- Joined: 09 Jul 2010, 13:52
- Has thanked: 0 time
- Been thanked: 0 time
Re: Current Known Bugs list
by moomarc » 28 Oct 2011, 16:26
There was a bug with paying 'X' costs when there was already mixed mana in the mana pool, but as far as I can tell this has been fixed now. So grab the latest nightly build or wait for the next beta which will likely be out end of next week. In the meantime you should just pay for X costs after playing the spell instead of adding the mana to your pool beforehand.Evilelvis wrote:Hey, I just downloaded Forge for the first time, and I must say I'm impressed with the general quality
I discovered a bug related to the card Earthquake - I had 4 mana (1R 2B 1G, one of the Bs was from Leaden Myr) and tried to cast it, I get asked to "Pay Mana Cost: R". Then I click the Mana Pool and I get the following exception:

-Marc
-
moomarc - Pixel Commander
- Posts: 2091
- Joined: 04 Jun 2010, 15:22
- Location: Johannesburg, South Africa
- Has thanked: 371 times
- Been thanked: 372 times
Re: Current Known Bugs list
by gos » 28 Oct 2011, 18:43
My opponent had Bloodgift Demon in play with 1 life. On his upkeep, he chose to lose 1 life, and lost.
- gos
- Posts: 4369
- Joined: 03 Mar 2011, 15:21
- Location: Reykjavík, Iceland
- Has thanked: 231 times
- Been thanked: 232 times
Re: Current Known Bugs list
by Accountancy » 29 Oct 2011, 03:48
If you start using Grim Lavamancer's ability, then cancel it before exiling a second card, the first card stays exiled.
- Accountancy
- Posts: 230
- Joined: 14 Aug 2009, 12:39
- Has thanked: 22 times
- Been thanked: 2 times
Who is online
Users browsing this forum: No registered users and 39 guests