Briefing
All testers are reminded that the reason for this testing is to find bugs and problems not to play the game. The faster we iron out all the bugs, the faster the update can take place. Bugs or errors can take place in all areas, from calculation error (ex: system doesnt produce income as it should, or battle calculations) to error showing up on the page.
Terms and condition
All testers is required to report any bugs or problems. Those who fails to report and is caught exploiting the bug will be severely punished. Resources (credits & minerals) maybe given to all testers once a while.
All testers is required to read what is new in the update, which can be found at:
http://spacefed.com/news/?/GC/17/UC_Version_1.7_Preview
Also all testers is required to read the manual (half completed) which can be found at:
http://uc2.gamestotal.com/manual/
You can post comments regarding your testing at
http://spacefed.com/gc/forum2/i.cfm?p=detail&cid=1&fid=272057
Beta server is located at: http://uc2.gamestotal.com
How to test
Try out each and every feature. See if you can find any problems. For example, build 10 ship, then calculate if it has deducted the right amount of turns/credits. Then try moving the ship from one system to another, disbanding and all that. Always check turns used, ships disband is the right one, and so on.
Notes
Only Terran Act 1 Missions is done.
All other races to be tested before Viral & Collective
The following isnt completed yet:
- 5 different types of ultimate weapons
- some projects
- staff (governors/generals)
The following features will still be improved on:
- Federation
- Lord & Vassal
- Attacking
You can create multiple accounts (dont create more than 5) for testing purposes. All accounts in beta will be removed after beta has been completed.
If an error occurs so how ?
Please email to us at info@gamestotal.com with subject `UC Beta Bugs` with this info:
1. Your empire name (system name if applicable)
2. Copy the URL of the error, copy the entire error message, screen capture if required
3. Detailed step by step, how you got the error
4. Have you tried logging off and in again then are you able to reproduce the error ?