Next beta release

[Chris H.]

I might try a twice a month schedule for a while and see how things turn out. We have had a lot of new work coming in during the last several months. A lot of this work is building upon Rob's keyword system and the existing code base. At some point this should start to slow down.

The weekly trunk build is another option and a script for this could make things easier as it would not need a change log, as we have the Commit log messages available on the google site for people to read.

As far as stability goes, we seem to have both good times and bad. I think that we also need to be careful and not create the impression that we can release frequent jar-fixes for the beta release unless it is necessary.

[Huggybaby]

At some point this should start to slow down.

I don't think it will slow down Chris. Look at other projects like MAME, DOSBox, Ur-Quan Masters...most projects don't seem to have an upper limit on how much development they can take. There's always something to be done, like figure out why the Quest doesn't run on my machine.

[Chris H.]

I don't think it will slow down Chris. Look at other projects like MAME, DOSBox, Ur-Quan Masters...most projects don't seem to have an upper limit on how much development they can take. There's always something to be done, like figure out why the Quest doesn't run on my machine.

`
I meant to further qualify my statement. We have had over 400 cards added in the last two weeks. I think that this portion will slow down somewhat.

There will always be bugs, new features, new AI decks, improved AI, etc to keep people busy.

[Rob Cashwalker]

Chris, we're almost approaching half of all printed cards... granted, there may be a handful we may never handle.. but surely there will be plenty of cards being added for a while to come.

[Sloth]

Sorry to come up with this now, but i'm experiencing a lot of crashes lately.

The computer wants to play a spell, taps its mana sources and then a message appears in the top left saying that an error may have occured. Starting a game after that causes my Moxen not to appear on the battlefield when cast (they just vanish).

Does any else experience this too or know what's going on?

[Chris H.]

Sorry to come up with this now, but i'm experiencing a lot of crashes lately.

The computer wants to play a spell, taps its mana sources and then a message appears in the top left saying that an error may have occured. Starting a game after that causes my Moxen not to appear on the battlefield when cast (they just vanish).

Does any else experience this too or know what's going on?

`
I just played two games with the 10-02 rev2481 and for the most part things seem to work correctly. I did have an error exception. I cast a Karmic Guide and choose a Chrome Steed to return from my graveyard to the battlefield. I got this 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


For input string: "+2"


Version:
Forge -- official beta: $Date: 2010-09-14 08:34:27 -0400 (Tue, 14 Sep 2010) $, SVN revision: $Revision: 2039 $

OS: Mac OS X Version: 10.6.4 Architecture: x86_64

Java Version: 1.6.0_20 Vendor: Apple Inc.

Detailed error trace:
java.lang.NumberFormatException: For input string: "+2"
   at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
   at java.lang.Integer.parseInt(Integer.java:449)
   at java.lang.Integer.valueOf(Integer.java:554)
   at forge.GameActionUtil$24.addKeyword(GameActionUtil.java:11255)
   at forge.GameActionUtil$24.addKeyword(GameActionUtil.java:11246)
   at forge.GameActionUtil$24.execute(GameActionUtil.java:11220)
   at forge.GameAction.checkStateEffects(GameAction.java:665)
   at forge.GameAction.CheckWheneverKeyword(GameAction.java:914)
   at forge.PlayerZone_ComesIntoPlay.add(PlayerZone_ComesIntoPlay.java:69)
   at forge.CardFactory_Creatures$177.resolve(CardFactory_Creatures.java:3702)
   at forge.Input_StackNotEmpty.selectButtonOK(Input_StackNotEmpty.java:46)
   at forge.GuiInput.selectButtonOK(GuiInput.java:36)
   at forge.GuiDisplay3.okButtonActionPerformed(GuiDisplay3.java:999)
   at forge.GuiDisplay3.access$3(GuiDisplay3.java:998)
   at forge.GuiDisplay3$26.actionPerformed(GuiDisplay3.java:793)
   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:6348)
   at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
   at java.awt.Component.processEvent(Component.java:6113)
   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:4618)
   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)


[Sloth]

I just played two games with the 10-02 rev2481 and for the most part things seem to work correctly. I did have an error exception. I cast a Karmic Guide and choose a Chrome Steed to return from my graveyard to the battlefield. I got this exception:

Ah, I see! The problem is the syntax of the stPump keyword: The Boni of Chrome Steed should be 2/2 instead of +2/+2.

[Chris H.]

Ah, I see! The problem is the syntax of the stPump keyword: The Boni of Chrome Steed should be 2/2 instead of +2/+2.

`
I was in a rush to add some more SoM cards and I did not study the keyword.

I fixed the four new Metalcraft cards that were recently added: Auriok Sunchaser, Chrome Steed, Ezuri's Brigade and Ghalma's Warden.

[slapshot5]

The computer wants to play a spell, taps its mana sources and then a message appears in the top left saying that an error may have occured. Starting a game after that causes my Moxen not to appear on the battlefield when cast (they just vanish).

Does any else experience this too or know what's going on?

I just experienced this for the first time. I think I'm synced to r2517. I had an Angry Mob out and a Patrol Signaler. I wasn't paying too close of attention.

-slapshot5