- Removed a no longer needed known issue.

- Added a fluff piece to the changes.txt file.
This commit is contained in:
Chris
2013-04-23 15:30:35 +00:00
parent 5fff16db45
commit 7a9e33bc6e

View File

@@ -56,6 +56,8 @@ Wishes can now only retrieve cards you own which prevents retrieving an opponent
Flicker effects were using the wrong Defined$ param. Flicker effects were using the wrong Defined$ param.
Spells that Change Target (like Swerve) are now able to redirect a Counterspell onto itself and this is now considered fixed.
- Targeting arrows - - Targeting arrows -
Some people have noticed slowdowns when Targeting arrows are enabled. The battlefield Dock tab includes a targeting icon. You can set the targeting arrows to Off or to Card mouseover to speed up the game. Some people have noticed slowdowns when Targeting arrows are enabled. The battlefield Dock tab includes a targeting icon. You can set the targeting arrows to Off or to Card mouseover to speed up the game.
@@ -221,8 +223,6 @@ Pontiff of Blight
Known Issues Known Issues
------------ ------------
Spells that Change Target (like Swerve) are currently unable to redirect a Counterspell onto itself do to other unforeseen issues with the current infrastructure.
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.