Version 0.4.0 Release Notes
NautDrafter - Version 0.4.0 -
System Requirements
How to Install NautDrafter
Step-by-step instructions for how to install NautDrafter
What's New
NEW | Added new custom drafting configurations for the Awesome Cup tournament. | |
NEW | Added a new option to control how Random Maps are handled.
| - NAUT-256Getting issue details... STATUS |
NEW | Games that use an Awesome Cup drafting configuration will automatically export the summary at the completion of the game. This summary will be saved to a publicly accessible drop box folder. This will only be available during the Awesome Cup tournament and will be disabled at the completion of the tournament. As its a temporary solution. A longer term strategy will need to be devised in terms of automatic export of games and other integrations. | - NAUT-259Getting issue details... STATUS |
CHANGED | Introduced map pools to custom drafting rules. This allows tournament organizers the flexibility to only allow a subset of maps to be selected for a game. The default drafting configuration has all maps in the map pool. However, tournament specific drafting configurations utilize smaller map pools. Currently, map pools can only be modified pragmatically. If your a tournament organizer, please contact us for help with adding a map pool for your event. | - NAUT-257Getting issue details... STATUS |
FIXED | During a bi-direction ban match, it was possible to ban a naut that was previously picked by either team. The server now disallows bans of nauts that have already been picked. There is not any graphical representation/highlights at this point. The game will just not allow the ban (clicking the ban button will produce no results). | - NAUT-261Getting issue details... STATUS |
FIXED | During a uni-direction ban match, it was possible to ban a naut that was previously picked by the opponent team. The server now disallows bans of natus (on the other team) that have already been picked. | - NAUT-264Getting issue details... STATUS |
Known Issues
UNRESOLVED | If the application is not closed properly after creating a server, the server may still be shown in the server browser, but attempts to join it will fail. Some changes have been made to reduce the likelihood of this happening (58d769f). | |
UNRESOLVED | The Spanish and Chinese language options are only partially translated and machine-translated by Google Translate so may be incorrect. |
See JIRA for all known issues affecting this release.
Troubleshooting
Contact Information
If you have any questions, bug reports or feature requests, our Google+ Community is the best way to reach us.