forked from LegoGMI/ManualeGM
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy path302_05_errors.html
50 lines (41 loc) · 1.45 KB
/
302_05_errors.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Error options</title>
<link href="style.css" rel="stylesheet" type="text/css">
</head>
<body background="images/back.gif">
<!--START-->
<h3>Error options</h3>
Here you can set a number of options that relate to the way errors are reported.
<p>
<b>Display error messages</b><br>
When checked, error messages are shown to the player. In the final
version of the game you might want to uncheck this option.
<p>
<b>Write error messages to file <tt>game_errors.log</tt></b><br>
When checked all error messages are written to a file called
<tt>game_errors.log</tt> in the game folder.
<p>
<b>Abort on all error messages</b><br>
Normally, certain errors are fatal while others can be ignored.
When checking this option all errors are considered fatal and lead
to aborting the game. In the final version of the game you distribute
you might want to check this option.
<p>
<b>Treat uninitialized variables as 0</b><br>
One common error is to use a variable before a value is assigned to it.
Sometimes this is difficult to avoid. When checking this option such
uninitialized variables no longer report an error but are treated as
value 0. Be careful though. It might mean that you don't spot typing
mistakes anymore.
<!--END-->
</body>
</html>
<!-- KEYWORDS
error messages
error options
uninitialized variables
error log
game_error.log
-->