external-repos/forge
1
0
Fork 0
mirror of https://github.com/Card-Forge/forge.git synced 2025-11-19 20:28:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

- Preparing the changes.txt file for the next beta build and release.

Browse Source
This commit is contained in:
Chris
2013-05-03 11:29:11 +00:00
parent 74216e5197
commit c78a11f4c4
1 changed files with 25 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

39
CHANGES.txt
View File

@@ -1,7 +1,7 @@
Forge Beta: 0#-##-2013 ver 1.3.14 Forge Beta: 05-03-2013 ver 1.3.14
12### cards in total. 12682 cards in total.
------------- -------------
@@ -9,7 +9,7 @@ Release Notes
------------- -------------
- Dragon's Maze - - Dragon's Maze -
Forge now includes 160 of the 166 Dragon's Maze cards in this new set. At this time card pictures for these cards are not available for downloading via the Download LQ Card Pictures and the Download LQ Set Pictures. They will become available at some point in the near future. Please be patient. Forge now includes 160 of the 166 Dragon's Maze cards in this new set. At this time card pictures for these cards are not available for downloading via the Download LQ Card Pictures and the Download LQ Set Pictures buttons. They will become available at some point in the near future. Please be patient.
- Thread bug - - Thread bug -
@@ -22,6 +22,10 @@ java.lang.NullPointerException
We currently suspect that this is a thread misuse issue. This will cause forge to crash eventually on some systems. Once the SwingWorkers that start different types of matches are refactored this problem should be fixed. The problem with a match starting with a blank screen will also be gone. We currently suspect that this is a thread misuse issue. This will cause forge to crash eventually on some systems. Once the SwingWorkers that start different types of matches are refactored this problem should be fixed. The problem with a match starting with a blank screen will also be gone.
- Quest challenge start in play cards -
We have received reports that the quest challenge start in play cards are not appearing on the battlefield for people who were playing the classic mode rather than the fantasy mode. This should now be fixed.
--------- ---------
New Cards New Cards
--------- ---------
@@ -34,6 +38,7 @@ Armored Wolf-Rider
Ascended Lawmage Ascended Lawmage
Awe for the Guilds Awe for the Guilds
Azorius Cluestone Azorius Cluestone
Back from the Brink
Bane Alley Blackguard Bane Alley Blackguard
Battering Krasis Battering Krasis
Beck // Call Beck // Call
@@ -47,7 +52,10 @@ Boros Mastiff
Breaking // Entering Breaking // Entering
Bred for the Hunt Bred for the Hunt
Bronzebeak Moa Bronzebeak Moa
Callous Oppressor
Carnage Gladiator Carnage Gladiator
Carry Away
Catch // Release
Clear a Path Clear a Path
Council of the Absolute Council of the Absolute
Crypt Incursion Crypt Incursion
@@ -107,6 +115,7 @@ Phytoburst
Pilfered Plans Pilfered Plans
Plasm Capture Plasm Capture
Pontiff of Blight Pontiff of Blight
Possibility Storm
Profit // Loss Profit // Loss
Progenitor Mimic Progenitor Mimic
Protect // Serve Protect // Serve
@@ -120,6 +129,7 @@ Render Silent
Renegade Krasis Renegade Krasis
Renounce the Guilds Renounce the Guilds
Restore the Peace Restore the Peace
Rhystic Lightning
Riot Control Riot Control
Riot Piker Riot Piker
Rot Farm Skeleton Rot Farm Skeleton
@@ -155,6 +165,7 @@ Varolz, the Scar-Striped
Viashino Firstblade Viashino Firstblade
Voice of Resurgence Voice of Resurgence
Vorel of the Hull Clade Vorel of the Hull Clade
Vulshok Battlemaster
Wake the Reflections Wake the Reflections
Warleader's Helix Warleader's Helix
Warped Physique Warped Physique
@@ -164,21 +175,11 @@ Woodlot Crawler
Zhur-Taa Ancient Zhur-Taa Ancient
Zhur-Taa Druid Zhur-Taa Druid
Vulshok Battlemaster
Carry Away
Possibility Storm
Rhystic Lightning
Catch // Release
Back from the Brink
Callous Oppressor
------------ ------------
Known Issues Known Issues
------------ ------------
We have received reports that the quest challenge start in play cards are not appearing on the battlefield for some people. This was either fixed recently or it only affects some people but not all of them. Your match.xml and/or your quest save files may be corrupted.
A small number of cards including Wall of Corpses, Abu Ja'far and others with a similar ability are not functional. The common issue here is actually that they check the blocker/attacker after being removed from the battlefield. Probably need to use LKI. Regular destroy/destroy all effects work just fine. The problem cards are caring about battlefield specific properties, that no longer apply when the base card is no longer on the battlefield. A small number of cards including Wall of Corpses, Abu Ja'far and others with a similar ability are not functional. The common issue here is actually that they check the blocker/attacker after being removed from the battlefield. Probably need to use LKI. Regular destroy/destroy all effects work just fine. The problem cards are caring about battlefield specific properties, that no longer apply when the base card is no longer on the battlefield.
On several occasions people have noticed that the Forge deck editor and/or quest mode card shop would not open or display. We have also received reports that some of the tabs/panels in the deck editor are missing. There has also been reports that Forge will crash while creating/populating display components during start up or crash when a match is started. One or both of your layout xml files may be corrupted in some fashion. Try deleting the file(s) named "editor.xml" and/or "match.xml" that are now located in your userDir/preferences/ directory. This should force Forge to then use the default layout xml files instead. On several occasions people have noticed that the Forge deck editor and/or quest mode card shop would not open or display. We have also received reports that some of the tabs/panels in the deck editor are missing. There has also been reports that Forge will crash while creating/populating display components during start up or crash when a match is started. One or both of your layout xml files may be corrupted in some fashion. Try deleting the file(s) named "editor.xml" and/or "match.xml" that are now located in your userDir/preferences/ directory. This should force Forge to then use the default layout xml files instead.
@@ -207,7 +208,17 @@ Some people use the Windows application 7zip. This utility can be found at http:
Contributors to This Release Contributors to This Release
---------------------------- ----------------------------
Asepetci
Gos
Hellfish
Marc
Max
Nordos
Sloth
Sol
Swordshine
Xitax
Chris H
(Quest icons used created by Teekatas, from his Legendora set http://raindropmemory.deviantart.com) (Quest icons used created by Teekatas, from his Legendora set http://raindropmemory.deviantart.com)