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

- Documenting changes in CHANGES.txt.

Browse Source
This commit is contained in:
Agetian
2017-05-18 05:49:45 +00:00
parent 96f2268343
commit a5b66415e9
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
forge-gui/release-files/CHANGES.txt
View File

@@ -1,19 +1,20 @@
- IMPORTANT: Partial backwards incompatibility with older decks that contain Masterpieces - - IMPORTANT: Partial backwards incompatibility with older decks that contain Masterpieces -
In case you have decks in your profile folder that contain one or more Masterpieces from the Kaladesh/Aether Revolt masterpiece series (previously the set code was MPS), you may experience an issue with cards that are present in the Masterpieces set disappearing visually and malfunctioning in the game (even if you use a version of the same card from a different set). The two primary waya this manifests itself are: a) you get a message stating that there is an unsupported card in one of your decks (this message shows in the console only); b) the card picture does not show in the game or in the deck editor and the card is reported as non-functional. If this happens to you, you have several options: either remove the offending deck altogether (you may have to do a search inside the profile folder to determine which decks have the mentioned card from the MPS set), or manually edit the deck file and change the set code MPS to MPS_KLD for such cards, or start with a fresh profile folder or at least fresh deck subfolder (but the latter obviously only works if you don't mind losing your entire progress and would like to start fresh). We apologize for the inconvenience. In case you have decks in your profile folder that contain one or more Masterpieces from the Kaladesh/Aether Revolt masterpiece series (previously the set code was MPS), you may experience an issue with cards that are present in the Masterpieces set disappearing visually and malfunctioning in the game (even if you use a version of the same card from a different set). The two primary waya this manifests itself are: a) you get a message stating that there is an unsupported card in one of your decks (this message shows in the console only); b) the card picture does not show in the game or in the deck editor and the card is reported as non-functional. If this happens to you, you have several options: either remove the offending deck altogether (you may have to do a search inside the profile folder to determine which decks have the mentioned card from the MPS set), or manually edit the deck file and change the set code MPS to MPS_KLD for such cards, or start with a fresh profile folder or at least fresh deck subfolder (but the latter obviously only works if you don't mind losing your entire progress and would like to start fresh). We apologize for the inconvenience.
- Planar Conquest changes -
Some adjustments have been made to the algorithm used for calculating probabilities of drawing a card from the Aether which is of rarity that is higher than selected in the filter. Higher rarity cards should now be considerably less common and thus the Aether should not be nearly as susceptible to being exploited for shards.
- Java 8 - - Java 8 -
As part of increased privacy protections (cardforge.org now uses SSL), the content downloaders now require a minimum Java version of 8u101. In the future, all of Forge will be updated to require Java 8. If you're running the latest version of Java, but Forge does not let you use the content downloaders, check to make sure that you've uninstalled old versions. Additionally, check any JDK installations you have and ensure Forge is using the most up-to-date version. As part of increased privacy protections (cardforge.org now uses SSL), the content downloaders now require a minimum Java version of 8u101. In the future, all of Forge will be updated to require Java 8. If you're running the latest version of Java, but Forge does not let you use the content downloaders, check to make sure that you've uninstalled old versions. Additionally, check any JDK installations you have and ensure Forge is using the most up-to-date version.
- Amonkhet Release - - Amonkhet Release -
This release contains all but two of the cards (As Foretold and Shadow of the Grave) from the newly released Amonkhet set. Hopefully we'll get these last two out soon enough. This release contains all but one of the cards (As Foretold) from the newly released Amonkhet set. Hopefully we'll get the last one out soon enough.
- Bug fixes - - Bug fixes -
As always, this release of Forge features an assortment of bug fixes and improvements based on user feedback during the 1.5.61 release run. As always, this release of Forge features an assortment of bug fixes and improvements based on user feedback during the 1.5.61 release run.
- AI generated decks - - AI generated decks -
This release contains a new way to generate random Standard or Modern decks that are themed around a specific card. In the deck selector you choose a card and the AI will build a deck around that card based on associations learnt from recent human generated online decks. The algorithm is non-deterministic, so the decks will vary every time they are generated for a unique deck virtually every time. This release contains a new way to generate random Standard or Modern decks that are themed around a specific card. In the deck selector you choose a card and the AI will build a deck around that card based on associations learnt from recent human generated online decks. The algorithm is non-deterministic, so the decks will vary every time they are generated for a unique deck virtually every time.
- User created quest worlds - - User created quest worlds -
If you have created some of your own quest worlds and don't want them to be overwritten when Forge updates, you can move the world folders to the user quest folder (in USER_FOLDER/quest/worlds) - you will also need to add the world definitions to a customworlds.txt file in that same folder If you have created some of your own quest worlds and don't want them to be overwritten when Forge updates, you can move the world folders to the user quest folder (in USER_FOLDER/quest/worlds) - you will also need to add the world definitions to a customworlds.txt file in that same folder