===============================================
2012.12.15
Welcome to the FoG(U) beta pre-view!
0) BETA NDA
--------------
Please remember that this is a beta pre-view, and all the information regarding it (data to acces to FTP, the build itself, or any other info about it) falls under the beta NDA (which is considered accepted by you at the moment you're accessing the FTP), and you can not share it with anyone else except Slitherine and Newrosoft staff.
1) BETA FTP INFO
--------------------
FTP: ftp://devel.matrixgames.com
user: FOGBetaTester
no password
You can use any FTP client you would want to (trying to use the FTP directly via your browser might not always work). You can use Total Commander's internal FTP (http://www.ghisler.com/download.htm), which is free (shareware).
2) BUILD FILES
----------------
In there you will find the FoG(U)_2012.12.15_01_v1.8.10.656_bRC2.rar (the bRC2 build itself) and FoG(U)_2012.12.15_01_v1.8.10.656_bRC2.txt (this file, containing build related instructions). There is also an FoG(U)_2012.12.15_01_v1.8.10.656_bRC2.exe self-extracting archive containing both the build and its readme file.
3) INSTALLATION
-------------------
The build is contained into the a .rar archive. It should be unpacked using any rachive un-packer which knows the .rar archive format. You should best use WinRar itself (http://www.rarlab.com/download.htm), which is also free (shareware). We're also providing the build as a self-extracting (rar) archive.
The content of the archive should be put a folder with full write rights, best directly into a folder on your Desktop (you can also use My Docs, directly in a folder in C drive's root or on any drive other than the system's C one)
4) STARTING UP
------------------
To start the build up, you just need to execute the FoG_v1.8.10.656.exe file. At the first run, you will be asked to provide your FoG(RB) (currently FoG released game) serial numbers. The build would not run without at least providing the FoG base game serial number.
While in Unity's launcher, you can also set the build to run in full-screen or windowed mode, and select the general graphics (Unity renderer's output) quality.
5) CONTROLS
---------------
LMB = left mouse button
RMB = right mouse button
The minimum controls you need to know about:
a) in game
- no selected BG + LMB on a selectable BG => selects a BG
- selected BG + LMB on a MArea hex => moves a BG to the desired MArea hex
- selected BG + mouse hoovering over a MArea hex => automatic movement path
- selected BG + LEFT ALT + mouse hoovering over a EBG => changes impact hex selection
- selected BG + LEFT ALT + mouse hoovering over an impact hex => changes charged EBG selection
- selected BG + LEFT CTRL + mouse hoovering over a MArea hex => manual movement path
- selected BG + RMB & drag => rotates the BG
- no selected BG + LEFT ALT + RMB => switches BG's evade behavior (always evade(default)/auto/no evade)
- M => switches the minimap on/off (default on)
- C => switches the combat prediction panel info on/off
- ` (the key to the left of the 1 key, upper left part of the keyboard for most of the keyboards) switches the Debug Console on/off (default off)
- no selected BG + R + RMB => forces a cohesion drop on the clicked BG
- RIGHT ALT + LMB/RMB & drag => free placement/rotation of BGs (to allow set up test positions fast)
- F12 switches the Debug Menu on/off. You can use it to modify console's output (first column), to force the output of various game methods (second column, the names should be self explanatory), or turn various panels on/off and also modify their output
There are various other controls, especially for the editor, but you should be fine with the above short list.
6) CONTENT
--------------
- the build contains no AI, and therefore you can only play single-player hotseat, or multi-player
- the LOS code is not ready yet, which means there is no FOW, and that ranged attacks are not taking LOS into calculation (ie you can shoot over BGs, etc)
- the're no MP Initiative code atm
7) CONSOLE.LOG
-------------------
The console.log file is your BEST friend. To have a better and more detailed look at the in-game console output, keep the console.log file (from game's root folder) open into any text editor (Notepad should be just fine).
8.) BETA PRE-VIEW BUG REPORTS, FEEDBACK & REQUESTS
------------------------------------------------------------------
When sending a beta report over beta boards/email, please make sure that:
- - the beta board thread starts with a [BUG] (<build's version number>): <text> when you're reporting a bug. Try to look for thread sand post in other threads about the same problem (if any available)
- the post/email must contain at least the console.log and output_log.txt files as attachments, and any other relevant screenshots and/or information
- the beta board thread starts with a [FDBCK] (<build's version number>): <text> when sending general feedback
- the beta board thread starts with a [REQ] (<build's version number>): <text> when asking for new features
- the email's subject is FoG(U) BETA - BUG REPORT (<build's version number>): <text> when you're reporting a bug
- the email's subject is FoG(U) BETA - FEEDBACK (<build's version number>): <text> when sending general feedback
Have a look at the whole game, and let us know what do you think about.. everything you'll find important to mention, please
9) CONTACT
--------------
Please use the beat boards if you have any problems related with this build. You can also directly contact me via email (dan . antonescu @ newrosoft . com), Yahoo Messenger (adonys13), Steam (adonys) or Skype (antonescu.dan).
Regards,
Dan Antonescu