1 | WHAT IS CROSSFIRE? |
1 | WHAT IS DELIANTRA? |
2 | |
2 | |
3 | This is a multiplayer graphical arcade and adventure game made for |
3 | This is a multiplayer graphical arcade and adventure game, that runs on |
4 | the X-Windows environment. It runs on a client/server model. |
4 | a client/server model. There are clients for Microsoft(R) Windows(TM) |
5 | The client runs with X11, GTK, or SDL within a gtk window. |
5 | and POSIX systems such as Linux and *BSD. To get the most joyful |
|
|
6 | experience, the Deliantra client should be used. This client is written |
|
|
7 | in Perl and utilises SDL with OpenGL to provide you with the most |
|
|
8 | immersive gameplay. |
6 | |
9 | |
7 | It has certain flavours from other games, especially Gauntlet (TM) |
10 | Deliantra has certain flavours from other games, especially Gauntlet (TM) |
8 | and Nethack/Moria. |
11 | and Nethack/Moria. |
9 | |
12 | |
10 | 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 |
11 | and using items and battle monsters. They can choose to cooperate |
14 | world, finding and using items and battle monsters. They can choose to |
12 | or compete in the same "world". |
15 | cooperate or compete in the same "world". |
|
|
16 | |
13 | |
17 | |
14 | REQUIREMENTS |
18 | REQUIREMENTS |
15 | |
19 | |
16 | For UNIX, X-windows and an ANSI C compiler to compile this game. |
20 | For UNIX, a modern C++ compiler with some extensions is required to |
17 | A window system is not needed if you don't want to compile the |
21 | compile this game (g++ 4.x works). In addition, you will need the Perl |
18 | map editor. |
22 | development libraries along with the following Perl modules (the server |
|
|
23 | requires perl 5.10.1). A perl configured for 64 bit integer support is |
|
|
24 | highly recommended to avoid overflows, but 32 bit perls are supported) |
|
|
25 | and their dependencies. In general, the newest version from CPAN will |
|
|
26 | do. The configure script will complain when it detects an unsuitable |
|
|
27 | version. |
19 | |
28 | |
20 | For Windows 9x, you need Visual C++ (or some other ANSI C |
29 | - common::sense |
21 | compiler that can read ".dsw"-files). |
30 | - AnyEvent |
22 | |
31 | - AnyEvent::AIO |
|
|
32 | - AnyEvent::BDB |
|
|
33 | - BDB **compiled against libdb4.[567] (libdb4.4 *might* work)** |
|
|
34 | - Compress::LZF |
|
|
35 | - Coro **SEE IMPORTANT NOTICE BELOW** |
|
|
36 | - Coro::EV |
|
|
37 | - Deliantra |
|
|
38 | - Digest::MD5 |
|
|
39 | - EV |
|
|
40 | - Guard |
|
|
41 | - IO::AIO |
|
|
42 | - JSON::XS |
|
|
43 | - AnyEvent::IRC |
|
|
44 | - Pod::POM |
|
|
45 | - Safe::Hole |
|
|
46 | - Storable |
|
|
47 | - Time::HiRes |
|
|
48 | - URI |
|
|
49 | - YAML::XS |
|
|
50 | |
|
|
51 | **NOTICE**: Deliantra uses an alternative signal stack, so you cannot |
|
|
52 | use the sigaltstack method (== setjmp on unrecognised platforms) for |
|
|
53 | Coro. Try "a"ssembly, "u"context or "p"threads as backend instead on |
|
|
54 | those platforms. |
|
|
55 | |
|
|
56 | Furthermore, you will need the following programs and libraries: |
|
|
57 | |
|
|
58 | - gperf, the GNU perfect hash generator >= v3.0 |
|
|
59 | - blitz++ >= 0.9 |
|
|
60 | - glib-2.0 >= v2.10 |
|
|
61 | - libpng >= v1.2 |
|
|
62 | - ImageMagick >= v6.3 (possibly higher, depending on its bugs) |
|
|
63 | - optipng => v0.5.5 (http://optipng.sf.net) |
|
|
64 | - pngnq >= v0.4 (http://freshmeat.net/redir/pngnq/53146/url_homepage/pngnq.html) |
|
|
65 | - rsync >= v2.6 (a must have anyways) |
|
|
66 | |
|
|
67 | Your compiler must support the Library Technical Report 1 extensions and |
|
|
68 | the upcoming typeof extension. The GNU C++ compiler >= version 4.0 does |
|
|
69 | support all these. |
|
|
70 | |
|
|
71 | On Debian GNU/Linux, you might get away with something like this for many of the |
|
|
72 | above dependencies: |
|
|
73 | |
|
|
74 | apt-get install gperf optipng pngnq rsync imagemagick libglib2.0-dev libpng12-dev |
|
|
75 | apt-get install libpod-pom-perl libsafe-hole-perl libevent-perl libblitz0-dev |
|
|
76 | |
|
|
77 | If you want to get sensible backtraces for error conditions at runtime |
|
|
78 | to be logged you also need the external addr2line program (part of GNU |
|
|
79 | binutils) in your PATH. |
|
|
80 | |
|
|
81 | |
23 | COMPILING |
82 | COMPILING |
24 | |
83 | |
25 | Crossfire has been known to compile on a wide variety of |
84 | Deliantra has been known to compile on a wide variety of systems. It should |
26 | systems. It should compile and most all ANSI C and Posix |
85 | compile and run on most ISO C++ 200x and POSIX compliant systems. |
27 | compliant systems. |
|
|
28 | |
86 | |
29 | To get directions on compilation for UNIX/LINUX, read the INSTALL file. |
87 | To get generic directions on compilation, read the INSTALL file. |
30 | For Win9x, read INSTALL_WIN32.txt. |
|
|
31 | |
|
|
32 | USAGE |
|
|
33 | |
|
|
34 | Crossfire runs on a client/server model. You will also need the |
|
|
35 | client to play. You can either connect to a server someone else |
|
|
36 | has set up, or run your own server and connect to that. The |
|
|
37 | client package has information for connecting to servers. |
|
|
38 | |
|
|
39 | To run your own server, you need to make the crossfire binaries and install |
|
|
40 | them, and then run the crossfire program. This now creates a server which |
|
|
41 | you/other people can connect to. The map files will need to get downloaded |
|
|
42 | and installed for the server to run properly. If you plan to run a long |
|
|
43 | term server, you should use one of the scripts provided that will re-run |
|
|
44 | crossfire if it dies for some reason. |
|
|
45 | |
|
|
46 | MAILING LIST |
|
|
47 | |
|
|
48 | For the latest subscription for crossfire mailing lists, go to: |
|
|
49 | http://crossfire.real-time.com/Website_Index/Mailing_Lists/mailing_lists.jhtml |
|
|
50 | |
|
|
51 | From there you should be able to subscribe/unsubscribe any of the mailing |
|
|
52 | lists. The mailing lists based off the ifi.uio.no host are being |
|
|
53 | discontinued. |
|
|
54 | |
|
|
55 | An archive of old messages can be found at |
|
|
56 | http://www.real-time.com/maillists/rte/crossfire |
|
|
57 | |
88 | |
58 | |
89 | |
59 | FTP SITES |
90 | INSTALLATION/USAGE |
60 | |
91 | |
61 | FTP-sites where you can look for the latest versions are: |
92 | Deliantra runs on a client/server model. You will also need a client to |
|
|
93 | play. You can either connect to a server someone else has set up, or |
|
|
94 | run your own server and connect to that. There are a number of clients |
|
|
95 | available, the recommended one is the Deliantra Client (see below for URL). |
62 | |
96 | |
63 | ftp://ftp.sourceforge.net/pub/sourceforge/crossfire |
97 | To run your own server, you need to build the deliantra server binaries |
64 | ftp://ftp.real-time.com/pub/games/crossfire |
98 | and install them, then you will have to download and install map and |
|
|
99 | archetype packs: |
65 | |
100 | |
66 | Changes made since the latest release can be found at the CVS |
101 | Download both the cfmaps-<version> and cfarch-<version> archives, then |
67 | repository. Information on anonymous CVS access as |
102 | use cfutil to install both (the source directories must be writable for |
68 | the download CVS snapshots and browsing the repository can be |
103 | this to work): |
69 | found at: |
104 | |
70 | http://sourceforge.net/cvs/?group_id=13833 |
105 | cfutil --install-maps path/to/cfmaps-<version>/ |
|
|
106 | cfutil --install-arch path/to/cfarch-<version>/ |
|
|
107 | |
|
|
108 | Both processes can take some time, depending on your resources :) If you |
|
|
109 | plan to repeat the installation you should specify the --cache option |
|
|
110 | first, which will keep costly-to-generate files around for further runs |
|
|
111 | of cfutil: |
|
|
112 | |
|
|
113 | cfutil --cache --install-maps path/to/cfmaps-<version>/ |
|
|
114 | cfutil --cache --install-arch path/to/cfarch-<version>/ |
|
|
115 | |
|
|
116 | Atfer this you can then run the deliantra executable. This starts a |
|
|
117 | server which you/other people can connect to. |
71 | |
118 | |
72 | |
119 | |
73 | If you are looking for a windows/NT client, look at: |
120 | WEB SITES |
74 | http://mids.student.utwente.nl/%7Emichtoen/crossfire/ |
|
|
75 | |
121 | |
76 | WEB SITES: |
|
|
77 | |
|
|
78 | The following web addresses have crossfire information that you may find |
122 | The following web addresses have deliantra information that you may find |
79 | useful: |
123 | useful: |
80 | |
124 | |
81 | http://crossfire.real-time.com/ |
125 | http://www.deliantra.net/ (The main site) |
82 | real-time is the main crossfire site. |
|
|
83 | |
126 | |
84 | |
127 | |
85 | REPORTING BUGS |
128 | REPORTING BUGS |
86 | |
129 | |
87 | First, check the INSTALL file for common problems, and see if yours is |
130 | First, check the INSTALL file for common problems, and see if yours is |
88 | mentioned. |
131 | mentioned. |
89 | |
132 | |
90 | The mailing list is where present development work and bugs are typically |
133 | Bugs should be filed using the following email address: |
91 | discussed. If you want to know what is happening with crossfire, join the |
134 | support@deliantra.net |
92 | list and please ask there. |
|
|
93 | |
|
|
94 | I will likely delete mail messages of the following sort: |
|
|
95 | 1) Bug reports of failed installation when the installation instructions |
|
|
96 | were not followed. |
|
|
97 | 2) Bug reports that contain so little information that it tells me nothing |
|
|
98 | more than the fact that there is a bug. |
|
|
99 | 3) Bugs in which the solution has already been answered in the INSTALL |
|
|
100 | file. |
|
|
101 | |
135 | |
102 | When reporting bugs, make sure you include the following: |
136 | When reporting bugs, make sure you include the following: |
|
|
137 | |
103 | o What version of crossfire did you use? |
138 | * What version of deliantra did you use? |
104 | o What type of computer did you use? |
139 | * What type of computer did you use (CPU type) |
105 | o What release of the operating system did it have? |
140 | * What is the version of the OS? |
106 | o What windowing system are you using (Ie, openwindows, X11R6, etc) |
141 | * What windowing system are you using (e.g. openwindows, X.org, XFree86) |
107 | o What compiler (and its version) did you use (ie, gcc, acc, etc)? |
142 | * What compiler (and its version) did you use (e.g. gcc, acc)? |
108 | o Which flags did you give it? |
143 | * Which flags did you give it? |
109 | o If the bug happens when compiling crossfire, send an EXACT copy of |
144 | * If the bug happens when compiling deliantra, send an EXACT copy of the |
110 | the compiler line, as well as the errors it puts out. Sending bugs |
145 | compiler line, as well as the errors it puts out. Sending bugs of the |
111 | of the sort 'it failed with a line like ...' doesn't help any. |
146 | sort 'it failed with a line like ...' doesn't help any. |
112 | o If the bug happened while running crossfire: |
147 | * If the bug happened while running deliantra: |
113 | - Include any output before to the bug. |
148 | - Include any output before to the bug. |
114 | - Give a description of what you did before the bug occured. The better |
149 | - Give a description of what you did before the bug occured. The better |
115 | detailed the description, the better chance I have of figuring |
150 | detailed the description, the better chance we have of figuring |
116 | out where the bug happened, or how I can recreate the bug. |
151 | out where the bug happened, or how we can recreate the bug. |
117 | o If you managed to compile Crossfire, include the output of |
152 | - If possible, a stack trace from gdb (or other debugger) is very |
118 | "crossfire -o". |
153 | helpful. |
119 | |
154 | |
120 | Lack of any of this information in a bug report can make that bug report |
155 | The more information provided, the better chance of the bug being fixed |
121 | useless. Also, if you have a bug, make sure you are using the latest |
156 | in a timely fashion. |
122 | version. If you report a bug that has since been fixed, you are not likely |
|
|
123 | to get any help. |
|
|
124 | |
|
|
125 | Further debugging informatiion can be found at |
|
|
126 | http://crossfire.real-time.com/debugging_tips.html |
|
|
127 | |
|
|
128 | Mail the bug report to crossfire-devel@listserv.real-time.com |
|
|
129 | |
|
|
130 | ------------------------------------------------------------------------------ |
|
|
131 | SUBMITTING PATCHES: See the doc/programming_guide file. |
|
|
132 | |
157 | |
133 | |
158 | |
134 | PUBLIC SERVERS: |
159 | SUBMITTING PATCHES |
135 | |
160 | |
|
|
161 | Patches should be submitted to email address: |
|
|
162 | support@deliantra.net |
|
|
163 | |
|
|
164 | |
|
|
165 | PUBLIC SERVERS |
|
|
166 | |
136 | The best way to find a server to play is to run the client. It will contact |
167 | The best way to find a server to play is to run the client |
137 | the metaserver and present a list to choose from. You can also see |
168 | and hit "Server List" in the setup dialog (this varies |
138 | a list at http://crossfire.real-time.com/metaserver/ |
169 | depending on your client). |
|
|
170 | |
|
|
171 | The canonical server for use with Deliantra and CFPlus is |
|
|
172 | gameserver.deliantra.net, port 13327 (the default). |
139 | |
173 | |
140 | |
174 | |
141 | COPYRIGHT |
175 | COPYRIGHT |
142 | |
176 | |
143 | Don't get scared by the below, it's included just for "safety" reasons 8) |
177 | Most files in this distribution are covered by the GNU General Public |
144 | (Don't want anyone to start selling the game) |
178 | License, version 3 (COPYING.GPL), or any later version, with the |
|
|
179 | exception of ext/affero.ext, which is covered by the GNU Affero General |
|
|
180 | Public License, Version 3 (COPYING.Affero). Please take note of the |
|
|
181 | special requirements of the Affero license with respect to network |
|
|
182 | servers and configure your network server according to the instructions |
|
|
183 | given in ext/affero.ext. |
145 | |
184 | |
146 | Copyright (C) 2000 Mark Wedel |
|
|
147 | Copyright (C) 1992 Frank Tore Johansen |
|
|
148 | |
185 | |
149 | This program is free software; you can redistribute it and/or modify |
186 | CONTACT |
150 | it under the terms of the GNU General Public License as published by |
|
|
151 | the Free Software Foundation; either version 2 of the License, or |
|
|
152 | (at your option) any later version. |
|
|
153 | |
187 | |
154 | This program is distributed in the hope that it will be useful, |
188 | The authors can be reached via e-mail to support@deliantra.net |
155 | but WITHOUT ANY WARRANTY; without even the implied warranty of |
|
|
156 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the |
|
|
157 | GNU General Public License for more details. |
|
|
158 | |
189 | |
159 | You should have received a copy of the GNU General Public License |
|
|
160 | along with this program; if not, write to the Free Software |
|
|
161 | Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. |
|
|
162 | |
|
|
163 | The author can be reached via e-mail to mwedel@scruz.net |
|
|