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
|
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>Notes for developers</title>
</head>
<body>
<h1>Notes for developers</h1>
<p>You are free to make whatever changes to the code you wish, as long as you
abide by the terms set out in the <a href="LICENCE">GNU General
Public License</a>. Obviously, I only have a limited amount of time to devote
to dopewars development, and so encourage discussion of the dopewars code,
documentation and concept, and particularly welcome suggested improvements.</p>
<p>You are free to distribute modified versions of the code,
again subject to the licence, but I also welcome patches to the code at my
email address,
<a href="mailto:ben@bellatrix.pcl.ox.ac.uk">ben@bellatrix.pcl.ox.ac.uk</a>.
If I choose to include these patches in a new dopewars version, you will of
course be credited in the changelog (unless, of course, you don't want to
be).</p>
<p>If you wish to write your own client to connect to a dopewars server, then
you need to understand the protocol that dopewars uses, which is
documented <a href="protocol.html">here</a>.</p>
<p>The definitive source on the internal workings of the dopewars game code
is the source code itself. It is not exactly "self-documenting", but I have
endeavoured to add sufficient documentation to the source where necessary;
any discussion here of the internal workings, however, may be incomplete, out
of date, and possibly misleading. Feel free to email me at the address above
with questions on this; I might possibly even know the answers!</p>
<hr />
<ul>
<li><a href="index.html">Main index</a></li>
</ul>
<p>Last update: <b>25-10-2001</b></p>
</body>
</html>
|
