Forge version 1.3.14
Post MTG Forge Related Programming Questions Here
Moderators: timmermac, Agetian, friarsol, Blacksmith, KrazyTheFox, CCGHQ Admins
3 posts
• Page 1 of 1
Forge version 1.3.14
by Chris H. » 26 Apr 2013, 13:54
Tentative target release date:
We can release this once we all feel that the new DGM material is fairly stable.
We can release this once we all feel that the new DGM material is fairly stable.
-

Chris H. - Forge Moderator
- Posts: 6320
- Joined: 04 Nov 2008, 12:11
- Location: Mac OS X Yosemite
- Has thanked: 644 times
- Been thanked: 643 times
Re: Forge version 1.3.14
by Chris H. » 29 Apr 2013, 12:41
Chris H. wrote:Tentative target release date:![]()
We can release this once we all feel that the new DGM material is fairly stable.
Will Friday May 3 be a good date?
-

Chris H. - Forge Moderator
- Posts: 6320
- Joined: 04 Nov 2008, 12:11
- Location: Mac OS X Yosemite
- Has thanked: 644 times
- Been thanked: 643 times
Re: Forge version 1.3.14
by Max mtg » 29 Apr 2013, 13:08
Sure, should be good for a mantainance release.
Some issues to b concerned of:
1. Dgm boosters yeild gates in common slot (someone should write a rule to filter them out, see related thread)
2. Preemptivelty make decision for optional tiggers on stack. The ui was referring to game directly, while it should get the current player controlled by gui and write the choices made to its PlayerContoller class instance.
3. Use a thread-safe collection for stack, or maybe marking getStack with synchronized keyword will be sufficint. Edt does not always know the exact number of items on stack, which results in OOB exception.
4. Get x count cannot get a not-null opponent when the game is over which results in npe.
Wish i could do any of the above by that day, but the tablet i have here is not a propper tool to write code.
Some issues to b concerned of:
1. Dgm boosters yeild gates in common slot (someone should write a rule to filter them out, see related thread)
2. Preemptivelty make decision for optional tiggers on stack. The ui was referring to game directly, while it should get the current player controlled by gui and write the choices made to its PlayerContoller class instance.
3. Use a thread-safe collection for stack, or maybe marking getStack with synchronized keyword will be sufficint. Edt does not always know the exact number of items on stack, which results in OOB exception.
4. Get x count cannot get a not-null opponent when the game is over which results in npe.
Wish i could do any of the above by that day, but the tablet i have here is not a propper tool to write code.
Single class for single responsibility.
- Max mtg
- Programmer
- Posts: 1997
- Joined: 02 Jul 2011, 14:26
- Has thanked: 173 times
- Been thanked: 334 times
3 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 11 guests