The game should already catch most exceptions and bring up an error dialog in this case. The error dialog provides a way to send an error report to us: This attaches the current config.properties file as well as the latest log and a few hardware information (e.g. driver information). The report dialog shows you all information it will send to us - it does not contain any sensible information.
Optionally you can also add some additional information about the crash.
However, if a native error occurs or an internal engine crash, the game cannot catch it - and will crash. In this case we would like to ask you to create a new topic about the crash here (or alternatively you can send a mail to support@jiw-games.net). It's extremely helpful if you attach the latest log file.
We're using the standard Unity log, because it's the only way to get internal outputs of the engine (e.g. errors thrown by the graphics API or a native library). The latest log is always called Player.log and on Windows it can be found in your user directory under /AppData/LocalLow/JIW-Games/Rising World. An easy way to get there is to press Windows key + R and to enter %APPDATA%/../LocalLow/JIW-Games/Rising World.
On Mac, the log can be found at /Users/<Username>/Library/Logs/JIW-Games/Rising World
On Linux, the log is stored at /home/<Username>/.config/unity3d/JIW-Games/Rising World
