ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/deliantra/server/README
(Generate patch)

Comparing deliantra/server/README (file contents):
Revision 1.4 by pippijn, Mon Mar 5 19:34:20 2007 UTC vs.
Revision 1.12 by root, Wed May 16 12:22:17 2007 UTC

1WHAT IS CROSSFIRE? 1WHAT IS CROSSFIRE?
2 2
3 This is a multiplayer graphical arcade and adventure game, that runs on a 3 This is a multiplayer graphical arcade and adventure game, that runs on
4 client/server model. There are clients for Microsoft(R) Windows(TM) and 4 a client/server model. There are clients for Microsoft(R) Windows(TM)
5 POSIX systems such as Linux and *BSD. To get the most joyful experience, 5 and POSIX systems such as Linux and *BSD. To get the most joyful
6 the Crossfire+ client should be used. This client is written in Perl and 6 experience, the Crossfire+ client should be used. This client is written
7 utilises SDL with OpenGL. 7 in Perl and utilises SDL with OpenGL to provide you with the most
8 immersive gameplay.
8 9
9 Crossfire has certain flavours from other games, especially Gauntlet (TM) 10 Crossfire has certain flavours from other games, especially Gauntlet (TM)
10 and Nethack/Moria. 11 and Nethack/Moria.
11 12
12 Any number of players can move around in their own window, finding 13 Any number of players can move around in their own window on the
13 and using items and battle monsters. They can choose to cooperate 14 world, finding and using items and battle monsters. They can choose to
14 or compete in the same "world". 15 cooperate or compete in the same "world".
16
15 17
16REQUIREMENTS 18REQUIREMENTS
17 19
18 For UNIX, the ISO C++ 200x compiler are required to compile this game. In 20 For UNIX, a modern C++ compiler with some extensions is required to
19 addition, you will need the Perl development libraries along with the 21 compile this game (g++ 4.x works). In addition, you will need the Perl
20 following Perl modules: 22 development libraries along with the following Perl modules (the server
23 is tested with perl 5.8.8 and 5.8-maint) and their dependencies. (the
24 minimum versions below may not be up-to-date, the configure script will
25 check them all, though).
21 26
22 - Crossfire >= v0.97 27 - AnyEvent >= 2.52
23 - Coro >= v3.5 28 - BDB >= v0.1
29 - Compress::LZF >= v1.8
30 - Coro >= v3.63 **SEE IMPORTANT NOTICE BELOW**
24 - Coro::Event >= v2.1 31 - Coro::Event >= v2.1
32 - Crossfire >= v0.98
33 - Digest::MD5 >= v2.0
25 - Event >= v1.08 34 - Event >= v1.08
26 - IO::AIO >= 2.32 35 - IO::AIO >= 2.32
27 - BDB >= v0.1 36 - JSON::XS => 1.21
37 - Pod::POM >= v0.17
38 - Safe::Hole >= v0.10
28 - Storable >= v2.0 39 - Storable >= v2.0
29 - Time::HiRes >= v1.0 40 - Time::HiRes >= v1.0
30 - YAML::Syck >= v0.71 41 - YAML::Syck >= v0.71
31 - Digest::MD5 >= v2.0
32 - Compress::LZF >= v1.71
33 - Safe::Hole >= v0.10
34 - Pod::POM >= v0.17
35 42
36 Furthermore, to build the crossfire server you will need the following: 43 **NOTICE**: Crossfire uses an alternative signal stack, so you have to
44 use either the "u"context method or "a"ssembly when configuring Coro.
37 45
46 Furthermore, you will need the following programs and libraries:
47
38 - gperf, the GNU perfect hash generator 48 - gperf, the GNU perfect hash generator >= v3.0
39 - glib-2.0 >= v2.10 49 - glib-2.0 >= v2.10
40 - libpng >= v1.2 50 - libpng >= v1.2
51 - ImageMagick >= v6.0 (possibly higher, depending on its bugs)
52 - optipng => v0.5.5 (http://optipng.sf.net)
53 - pngnq >= 0.4 (http://freshmeat.net/redir/pngnq/53146/url_homepage/pngnq.html)
54 - rsync >= 2.6 (a must have anyways)
41 55
42 Your compiler must support the Library Technical Report 1 extensions. 56 Your compiler must support the Library Technical Report 1 extensions and
43 The GNU C++ compiler >= version 4.0 does support these. 57 the upcoming typeof extension. The GNU C++ compiler >= version 4.0 does
58 support all these.
59
60 On Debian GNU/Linux, you might get away with something like this for many of the
61 above dependencies:
62
63 apt-get install gperf optipng pngnq rsync imagemagick libglib2.0-dev libpng12-dev
64 apt-get install libpod-pom-perl libsafe-hole-perl libevent-perl
65
44 66
45COMPILING 67COMPILING
46 68
47 Crossfire has been known to compile on a wide variety of systems. It should 69 Crossfire has been known to compile on a wide variety of systems. It should
48 compile and most all ISO C++ 200x and POSIX compliant systems. 70 compile and run on most ISO C++ 200x and POSIX compliant systems.
49 71
50 To get directions on compilation for UNIX/LINUX, read the INSTALL file. 72 To get generic directions on compilation, read the INSTALL file.
51 73
52USAGE
53 74
54 Crossfire runs on a client/server model. You will also need the client to 75INSTALLATION/USAGE
55 play. You can either connect to a server someone else has set up, or run
56 your own server and connect to that. The client package has information for
57 connecting to servers.
58 76
59 To run your own server, you need to make the crossfire binaries and install 77 Crossfire runs on a client/server model. You will also a client to
60 them, and then run the crossfire program. This now creates a server which 78 play. You can either connect to a server someone else has set up, or
61 you/other people can connect to. The map files will need to get downloaded 79 run your own server and connect to that. There are a number of clients
62 and installed for the server to run properly. The maps should be unpacked in 80 available, but the recommended one is CFPlus (see below for URL).
63 the $(TARGET)/share/crossfire directory - after unpacking, you should have a
64 $(TARGET)/share/crossfire/maps directory.
65 81
66 If you plan to run a long term server, you should use one of the scripts 82 To run your own server, you need to build the crossfire server binaries
67 provided that will re-run crossfire if it dies for some reason. 83 and install them, then you will have to download and install map and
84 archetype packs:
85
86 Download both the cfmaps-<version> and cfarch-<version> archives, then
87 use cfutil to install both (the source directories must be writable for
88 this to work):
89
90 cfutil --install-maps path/to/cfmaps-<version>/
91 cfutil --install-arch path/to/cfarch-<version>/
92
93 Both processes can take some time, depending on your resources :) If you
94 plan to repeat the installation you should specify the --cache option
95 which will keep costly-to-generate files around for further runs of
96 cfutil.
97
98 Atfer this you can then run the crossfire executable. This starts a
99 server which you/other people can connect to.
100
68 101
69WEB SITES: 102WEB SITES:
70 103
71 The following web addresses have crossfire information that you may find 104 The following web addresses have crossfire information that you may find
72 useful: 105 useful:
83 116
84 Bugs should be filed using the following email address: 117 Bugs should be filed using the following email address:
85 crossfire@schmorp.de 118 crossfire@schmorp.de
86 119
87 When reporting bugs, make sure you include the following: 120 When reporting bugs, make sure you include the following:
121
88 o What version of crossfire did you use? 122 * What version of crossfire did you use?
89 o What type of computer did you use (CPU type) 123 * What type of computer did you use (CPU type)
90 o What is the version of the OS? 124 * What is the version of the OS?
91 o What windowing system are you using (e.g. openwindows, X.org, XFree86) 125 * What windowing system are you using (e.g. openwindows, X.org, XFree86)
92 o What compiler (and its version) did you use (e.g. gcc, acc)? 126 * What compiler (and its version) did you use (e.g. gcc, acc)?
93 o Which flags did you give it? 127 * Which flags did you give it?
94 o If the bug happens when compiling crossfire, send an EXACT copy of the 128 * If the bug happens when compiling crossfire, send an EXACT copy of the
95 compiler line, as well as the errors it puts out. Sending bugs of the 129 compiler line, as well as the errors it puts out. Sending bugs of the
96 sort 'it failed with a line like ...' doesn't help any. 130 sort 'it failed with a line like ...' doesn't help any.
97 o If the bug happened while running crossfire: 131 * If the bug happened while running crossfire:
98 - Include any output before to the bug. 132 - Include any output before to the bug.
99 - Give a description of what you did before the bug occured. The better 133 - Give a description of what you did before the bug occured. The better
100 detailed the description, the better chance I have of figuring 134 detailed the description, the better chance we have of figuring
101 out where the bug happened, or how I can recreate the bug. 135 out where the bug happened, or how we can recreate the bug.
102 - If possible, a stack trace from gdb (or other debugger) is very 136 - If possible, a stack trace from gdb (or other debugger) is very
103 helpful. 137 helpful.
104 138
105The more information provided, the better chance of the bug being fixed in 139 The more information provided, the better chance of the bug being fixed
106a timely fashion. 140 in a timely fashion.
107 141
108------------------------------------------------------------------------------
109SUBMITTING PATCHES: 142SUBMITTING PATCHES:
143
110Patches should be submitted to email address: 144 Patches should be submitted to email address:
111 crossfire@schmorp.de 145 crossfire@schmorp.de
112 146
113PUBLIC SERVERS: 147PUBLIC SERVERS:
114 148
115The best way to find a server to play is to run the client. It will contact 149 The best way to find a server to play is to run the client
116the metaserver and present a list to choose from. You can also see 150 and hit "Server List" in the setup dialog (this varies
151 depending on your client). You can also see a list at
117a list at http://crossfire.real-time.com/metaserver/ 152 http://crossfire.real-time.com/metaserver/.
118 153
154 The canonical server for use with Crossfire and CFPlus is
155 crossfire.schmorp.de, port 13327 (default).
119 156
120COPYRIGHT 157COPYRIGHT
121 158
122 Copyright (C) 2007 Crossfire Development Team 159 Copyright (C) 2006,2007 Crossfire TRT Development Team
123 Copyright (C) 2000, 2006 Mark Wedel 160 Copyright (C) 2000,2006 Mark Wedel
124 Copyright (C) 1992 Frank Tore Johansen 161 Copyright (C) 1992 Frank Tore Johansen
125 162
126 This program is free software; you can redistribute it and/or modify 163 This program is free software; you can redistribute it and/or modify
127 it under the terms of the GNU General Public License as published by 164 it under the terms of the GNU General Public License as published by
128 the Free Software Foundation; either version 2 of the License, or 165 the Free Software Foundation; either version 2 of the License, or
129 (at your option) any later version. 166 (at your option) any later version.
130 167
131 This program is distributed in the hope that it will be useful, 168 This program is distributed in the hope that it will be useful,
132 but WITHOUT ANY WARRANTY; without even the implied warranty of 169 but WITHOUT ANY WARRANTY; without even the implied warranty of
133 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 170 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
134 GNU General Public License for more details. 171 GNU General Public License for more details.
135 172
136 You should have received a copy of the GNU General Public License 173 You should have received a copy of the GNU General Public License
137 along with this program; if not, write to the Free Software 174 along with this program; if not, write to the Free Software
138 Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. 175 Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
139 176
140 The authors can be reached via e-mail to crossfire@schmorp.de 177 The authors can be reached via e-mail to crossfire@schmorp.de

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines