|
Things to do before 1.0.0
From Globulation2
0.9.3 - Beta 3 (needed features)
Bugs to fix
- Any old maps from alpha 23 or before causes the game to freeze/crash when going to custom games. Instead, these files should have their headers compared and incompatible ones should be ignored.
- Random crash when playing with 14 Nicowar ingame. http://glob2.pastebin.com/f7c545644
- Random crash when either (14 players are Nicowar, and you assign player 16 to nicowar on your team) or (you assign 14 nicowar to the same team). http://glob2.pastebin.com/f45f9132
- Crash when quitting a 512x512 game a few seconds in. http://glob2.pastebin.com/f7caba33f
Features to implement
- Voice support (or at least an attempt of it) for Globulation 2 on Windows and Mac OSX needs to be added. 1.0.0 should be feature full on all systems, and this means getting voip to work not only on linux, but windows and Mac OSX too.
- A private (pre game screen) and public (game lobby, irc) interchangeable tabbed interface on the pregame screen needs to be available. People in game should be able to have private chats with people who are playing the game, but also with the lobby to keep up with whats happening and see if someone is having trouble connecting.
- The ability to set teams in custom games. Teams can be set via a team number. Every tesam has a team number. By default, human players have a team number of 1 and AI players have at eam number of 2. Team number selector can go right beside the colour selector in the custom game menu and in the yog game setup menu. People on the same team are allianced in all manners, except Inn View. People on different teams have the standard 0 alliance settings.
- After pressing 't': Now lines are only drawn if the source (the glob) is on the screen. They should be drawn whenever either the source or the target (inn, ...) is on the screen.
- In the settings menu provided while playing, possibly provide an option to change screen size/full screen mode instantly (in case its needed urgently).
- When multiple units convert at once, say how many have been.
Proper form for leaving a game
- If the user tries to quit a custom game, he/she should be presented with "Would you like to save?" message. When saving, the save filename should automatically default to any previous filename save. Saves-default filenames should be done by a formatted date string as well, something like "Big Pond - Wed / March 22" would do very well. Although its long, length doesn't really matter, as long as its quick and easy to read, where as something like "Big Pond 22/03/06" makes you think more about what your reading, and indeed, it may confuse some of those dummer people. Auto saves should be done by map name *and* date, so "Big Pond - Wed / March 22 - Autosave", rather than using one generic name of Autosave. Again, length isn't important, because one can read it all very quickly, without having to "think" about what their reading, which slows them down. When quitting, one should not be presented with the "You Lost" screen, as the person has quit, and it only makes them feel unhappy. They want to get to the main menu, they don't want to be told that they suck. It should only tell them they lost when they actually lost. So, another question should be presented, (this one should have a checkmark saying "Don't ask me again", because it will get annoying after a while, and that option should also be changeable in the options menu), and this one should say "Would you like to see the games statistics?". If the user says yes, then the game should go into the end game statistics, and then it can tell them they lost.
YOG improvements
- Passwords for the YOG system should be encrypted for protection, but in the preferences file and when sending and receiving them from the server.
- At the moment, when a player leaves a YOG match, there is no notice, and their units get left behind uncontrolled.
- If a player leaves a YOG game, it should say "xxxxx has left the game" to indicate to players who is left to play against.
- When the last player of a YOG match leaves, whether they have units left or not, it should automatically let you win (at the moment, it requires all units from all players left on the map to be killed, and this is tiresome).
0.9.4 - Beta 4 (misc but needed improvements)
Features to implement
- Tie up loose ends in the menus and code, for example, things in Settings that mean nothing
- Remove any translations that are out of date. Its better to have 3 good ones and nothing else than 15 incorrect ones that will confuse users.
- Make sure all files have been updated to GPL v3, including preambles and COPYING.
- A complete directory restructuring should take place. Files will be moved and tidied so things are easier to find. Any old files will be removed, and all src/ files will be place in folder relating to their purpose (example: src/yog/, src/gui/, src/ai/ etc).
1.0.0 - Release Candidate 1 (feature freeze, bug fixes and translations only)
- Thoroughly test the new YOG system, and make sure desynchronizing is a thing of the past.
- Fix any remaining bugs from the previous beta's.
1.0.0 - Final release (completion, final tasks)
- Packages from all systems should be made before release, rather than after the release is made. When the announcement is made, the minimum releases available should be source, windows (exe and runtime), mandriva (rpm, and src), debian, and hopefully Mac OSX.
1.1.0 Feature List
Some of the things to make in into 1.1.0 (once 1.0.0 is released) should be:
- Improved path finding
- Smarter AI
- SGSL improvements (both coding and the editor)
- New challenging and intriguing campaign
- Map filters
- Building prioritization
- and more......
| |
Analytics