SVN Bug Reports

[friarsol]

And I just submitted a fix for the issue.

[Chris H.]

OK, with your bug fix I ran the test deck with rev 6206. No error when I Terror the AI's Reveillark if the graveyard is empty.

On another test I Terror the AI's Devoted Hero and afterwards Terror the AI's Reveillark. The Reveillark LtB ability causes a new error exception:

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
   mtgerror@yahoo.com


null


Version:
Forge -- official beta: $Date: 2011-01-06 11:34:48 -0500 (Thu, 06 Jan 2011) $, SVN revision: $Revision: 4891 $

OS: Mac OS X Version: 10.6.6 Architecture: x86_64

Java Version: 1.6.0_22 Vendor: Apple Inc.

Detailed error trace:
java.lang.NullPointerException
   at forge.AbilityFactory_ChangeZone.changeKnownOriginCanPlayAI(AbilityFactory_ChangeZone.java:676)
   at forge.AbilityFactory_ChangeZone.changeZoneCanPlayAI(AbilityFactory_ChangeZone.java:124)
   at forge.AbilityFactory_ChangeZone.access$0(AbilityFactory_ChangeZone.java:116)
   at forge.AbilityFactory_ChangeZone$1.doTrigger(AbilityFactory_ChangeZone.java:35)
   at forge.TriggerHandler$1.doTrigger(TriggerHandler.java:321)
   at forge.TriggerHandler.runSingleTrigger(TriggerHandler.java:803)
   at forge.TriggerHandler.runTrigger(TriggerHandler.java:192)
   at forge.GameAction.moveTo(GameAction.java:77)
   at forge.GameAction.moveToGraveyard(GameAction.java:165)
   at forge.GameAction.sacrificeDestroy(GameAction.java:2068)
   at forge.GameAction.destroyNoRegeneration(GameAction.java:674)
   at forge.AbilityFactory_Destroy.destroyResolve(AbilityFactory_Destroy.java:353)
   at forge.AbilityFactory_Destroy$2.resolve(AbilityFactory_Destroy.java:60)
   at forge.MagicStack.resolveStack(MagicStack.java:666)
   at forge.Phase.passPriority(Phase.java:514)
   at forge.ComputerAI_General.stackResponse(ComputerAI_General.java:286)
   at forge.ComputerAI_General.stack_not_empty(ComputerAI_General.java:241)
   at forge.ComputerAI_Input.think(ComputerAI_Input.java:43)
   at forge.ComputerAI_Input.showMessage(ComputerAI_Input.java:31)
   at forge.GuiInput.setInput(GuiInput.java:27)
   at forge.GuiInput.update(GuiInput.java:21)
   at java.util.Observable.notifyObservers(Observable.java:142)
   at java.util.Observable.notifyObservers(Observable.java:98)
   at forge.MyObservable.updateObservers(MyObservable.java:9)
   at forge.InputControl.resetInput(InputControl.java:52)
   at forge.Phase.passPriority(Phase.java:505)
   at forge.Input_PassPriority.selectButtonOK(Input_PassPriority.java:35)
   at forge.GuiInput.selectButtonOK(GuiInput.java:35)
   at forge.GuiDisplay3.okButtonActionPerformed(GuiDisplay3.java:962)
   at forge.GuiDisplay3.access$3(GuiDisplay3.java:961)
   at forge.GuiDisplay3$26.actionPerformed(GuiDisplay3.java:756)
   at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2028)
   at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2351)
   at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
   at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
   at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
   at java.awt.Component.processMouseEvent(Component.java:6352)
   at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
   at java.awt.Component.processEvent(Component.java:6117)
   at java.awt.Container.processEvent(Container.java:2085)
   at java.awt.Component.dispatchEventImpl(Component.java:4714)
   at java.awt.Container.dispatchEventImpl(Container.java:2143)
   at java.awt.Component.dispatchEvent(Component.java:4544)
   at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4621)
   at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4282)
   at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4212)
   at java.awt.Container.dispatchEventImpl(Container.java:2129)
   at java.awt.Window.dispatchEventImpl(Window.java:2478)
   at java.awt.Component.dispatchEvent(Component.java:4544)
   at java.awt.EventQueue.dispatchEvent(EventQueue.java:635)
   at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:296)
   at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:211)
   at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:201)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:196)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:188)
   at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)


[Fnoed]

For now, you can get it to compile by using this batch file to start the build.

Just adding the two jar files is not enough to fix the script. I get the same error as Corwin.

Added the two jar files to the MANIFEST in r6207. The build process generates a working forge now (using my updated batchfile to build).

[timmermac]

Checking it now... Will edit post with results. This will be r6208

Edit: So far, everything is functioning as expected. Just about to play my first match.

Edit2: Has the name for the fully-upgraded wolf pet picture changed?

[Fnoed]

Edit2: Has the name for the fully-upgraded wolf pet picture changed?

Typo in the naming, try with r6211.

[timmermac]

Edit2: Has the name for the fully-upgraded wolf pet picture changed?

Typo in the naming, try with r6211.

I checked out the change in the code, it should be G 2 2 Wolf Pet Flanking.

[Fnoed]

Edit2: Has the name for the fully-upgraded wolf pet picture changed?

Typo in the naming, try with r6211.

I checked out the change in the code, it should be G 2 2 Wolf Pet Flanking.

Fixed in r6213.

[friarsol]

OK, with your bug fix I ran the test deck with rev 6206. No error when I Terror the AI's Reveillark if the graveyard is empty.

On another test I Terror the AI's Devoted Hero and afterwards Terror the AI's Reveillark. The Reveillark LtB ability causes a new error exception:

Similar problem as before. Should have just fixed it this way to begin with. Let me know if there is any other quirks with this.

[friarsol]

Fixed in r6213.

Hehe. It looks like the level 2 Wolf Pet is now 2/1, but the old Wolf Pet was a 1/2. So the image isn't right (or the Pet is incorrect)

[Sloth]

Added the two jar files to the MANIFEST in r6207. The build process generates a working forge now (using my updated batchfile to build).

Quest mode starts now, but I'm unable to close the quest window.

[timmermac]

r6214 downloaded

[Chris H.]

OK, with your bug fix I ran the test deck with rev 6206. No error when I Terror the AI's Reveillark if the graveyard is empty.

On another test I Terror the AI's Devoted Hero and afterwards Terror the AI's Reveillark. The Reveillark LtB ability causes a new error exception:

Similar problem as before. Should have just fixed it this way to begin with. Let me know if there is any other quirks with this.

`
I re-ran the test with rev 6213 and it works, great.

Thank you for your help and for the bug fix. We have not had too many bugs in the cards or in the code with the AF project. I am glad to see it moving forward and for the most part it just works.

[friarsol]

Added the two jar files to the MANIFEST in r6207. The build process generates a working forge now (using my updated batchfile to build).

Quest mode starts now, but I'm unable to close the quest window.

Does the Return to Main Menu button work? We probably should link the Window Close button to do the same thing.

[timmermac]

Added the two jar files to the MANIFEST in r6207. The build process generates a working forge now (using my updated batchfile to build).

Quest mode starts now, but I'm unable to close the quest window.

There's a button that says Return To Main Menu that you can click on.

Edit: hehehe. Sol and I got that at the same time.

[friarsol]

Thank you for your help and for the bug fix. We have not had too many bugs in the cards or in the code with the AF project. I am glad to see it moving forward and for the most part it just works.

Yea it's definitely worked fairly consistently which is definitely a big plus. I'm a bit surprised we haven't noticed more in ChangeZone considering how large it is in relation to the other AFs.