|
|
| Line 2: |
Line 2: |
|
* Beta5 is in feature freeze so any new features will earliest go into beta6 |
|
* Beta5 is in feature freeze so any new features will earliest go into beta6 |
|
* Beta5 is still open for translations and slight modifications in the map files |
|
* Beta5 is still open for translations and slight modifications in the map files |
|
* The new feature "replays" produces wrong replays for network games that go unnoticed by the player. Also version changes don't invalidate old replays so they might or might not replay correctly. As replays is the most noticeable new feature I don't see a point in releasing beta5 without replays. A prominent Warning when starting a replay about those bugs might be an option in my opinion as we need to show progress. |
|
* The new feature "replays" produces wrong replays for network games that go unnoticed by the player. Also, replays of a different version don't replay correctly and there is not even a warning about this. The big problem is that the replays that play out differently are different in their checksums but not in their game-dumps, which makes it impossible to see what is different between the two games. A prominent warning when starting a replay about those bugs might be an option in my opinion as we need to show progress. |
|
* Online games can still desync, with some difference in building priorities. A nice feature to have when debugging desyncs like this would be human-readable replays, but the replay engine as it is now would need to know that the replays will be saved in human-readable form in advance in order to be able to do so, or a major rewrite would be needed. Also, "human-readable" is only slightly readable. |
|
* We played an online game some time ago and it desynced, with some difference in building priorities. A nice feature to have when debugging desyncs like this would be human-readable replays? However, the replay engine was not built with this in mind and would need a major rewrite. |
|
|
* Scripting (UML) is still broken. It should either be fixed or be replaced by SGSL before release. This may have been fixed though, I'm not sure. |
Latest revision as of 09:09, 26 July 2010
Things left to do prior to releasing beta5:
- Beta5 is in feature freeze so any new features will earliest go into beta6
- Beta5 is still open for translations and slight modifications in the map files
- The new feature "replays" produces wrong replays for network games that go unnoticed by the player. Also, replays of a different version don't replay correctly and there is not even a warning about this. The big problem is that the replays that play out differently are different in their checksums but not in their game-dumps, which makes it impossible to see what is different between the two games. A prominent warning when starting a replay about those bugs might be an option in my opinion as we need to show progress.
- We played an online game some time ago and it desynced, with some difference in building priorities. A nice feature to have when debugging desyncs like this would be human-readable replays? However, the replay engine was not built with this in mind and would need a major rewrite.
- Scripting (UML) is still broken. It should either be fixed or be replaced by SGSL before release. This may have been fixed though, I'm not sure.
