summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorSimon Howard2011-06-13 22:21:37 +0000
committerSimon Howard2011-06-13 22:21:37 +0000
commit391e7466b1efb7cbede4a1c356a210d9e7ee616b (patch)
tree90d13346d9cd3636df44290ded13d59ae3712543 /README
parentfa328faf056affa216f2f3a8764ca0d56262efe9 (diff)
parent822664b4ff873d462370e9e96a9d91e6066c221d (diff)
downloadchocolate-doom-391e7466b1efb7cbede4a1c356a210d9e7ee616b.tar.gz
chocolate-doom-391e7466b1efb7cbede4a1c356a210d9e7ee616b.tar.bz2
chocolate-doom-391e7466b1efb7cbede4a1c356a210d9e7ee616b.zip
Merge from trunk.
Subversion-branch: /branches/raven-branch Subversion-revision: 2347
Diffstat (limited to 'README')
-rw-r--r--README11
1 files changed, 7 insertions, 4 deletions
diff --git a/README b/README
index 06dc1537..f641c126 100644
--- a/README
+++ b/README
@@ -65,10 +65,11 @@ Here are some examples:
You are encouraged to sign up and contribute any useful information
you may have regarding the port!
- * Chocolate Doom is not perfect. See the BUGS file for a list of
- known issues. Because of the nature of the project, you may also
- encounter Vanilla Doom bugs; these are intentionally present; see
- the NOT-BUGS file for more information.
+ * Chocolate Doom is not perfect. Although it aims to accurately
+ emulate Vanilla Doom, some of the behavior of Vanilla Doom can be
+ very difficult to reproduce. Because of the nature of the project,
+ you may also encounter Vanilla Doom bugs; these are intentionally
+ present; see the NOT-BUGS file for more information.
New bug reports can be submitted to the Chocolate Doom bug tracker
on Sourceforge. See:
@@ -85,3 +86,5 @@ Here are some examples:
* Please send any feedback, questions or suggestions to
fraggle@gmail.com. Thanks!
+# vim: tw=70
+