By pre-ordering Overgrowth, you can do two things:
- Access the Secret Preorder Forums (referred to as SPF)
- Check out the latest alphas
First of all, you need an account on the forum. If you don't have one already, register there. Then follow the link given in your pre-order email, and type your nickname to get access to the SPF.
In the SPF, you'll find a sticky named "Unofficial alpha XX, weekly build". You can check that post out to get the link to download the latest Overgrowth alpha.
The SPF is also a place where discuss discuss the alpha with others who have preordered the game, speculate about Overgrowth and ask questions to the Wolfire team. Participate and join us in the discussions!
After preordering Overgrowth and linking a forum account, access to the Secret Preorder Forum becomes available. Each week, the alpha build is posted as a stickied topic with a title of the form: "Unofficial Overgrowth a###, weekly build".
There are multiple download options available - a direct download, torrent download, and a "differences" download, which can be used to update a previously installed alpha.
Additionally, once at least one full alpha installation has been performed, the community-made SUMLauncher may be used for updates (requires a Java Runtime Environment)
Upon opening the game, you will be greeting with a menu screen. There is a side-scrolling list of levels from which to choose. Clicking on a thumbnail causes the level to load. If you need to change settings such as the games resolution or anti-aliasing, please refer to Configuring Overgrowth.
For help controlling your character, see Player Controls.
Overgrowth is currently in Alpha, and as such, features may be buggy, incomplete, non-functional, or otherwise broken. In order to help with development, you can report bugs to Wolfire via email at [email protected]
Your email should contain the following:
- The Alpha Version in which the problem was encountered
- Your system setup (Hardware, OS, etc.)
- A Brief explanation of the problem
- Actions performed, step by step, which led up to encountering the problem
- Expected and Actual Results
- Attachments (screenshots, crash reports, etc.)
Refer to this webpage for tips on how to write a quality bug report.