1 | WHAT IS CROSSFIRE? |
1 | WHAT IS DELIANTRA? |
2 | |
2 | |
3 | This is a multiplayer graphical arcade and adventure game, that runs on |
3 | This is a multiplayer graphical arcade and adventure game, that runs on |
4 | a client/server model. There are clients for Microsoft(R) Windows(TM) |
4 | a client/server model. There are clients for Microsoft(R) Windows(TM) |
5 | and POSIX systems such as Linux and *BSD. To get the most joyful |
5 | and POSIX systems such as Linux and *BSD. To get the most joyful |
6 | experience, the Crossfire+ client should be used. This client is written |
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 |
7 | in Perl and utilises SDL with OpenGL to provide you with the most |
8 | immersive gameplay. |
8 | immersive gameplay. |
9 | |
9 | |
10 | Crossfire has certain flavours from other games, especially Gauntlet (TM) |
10 | Deliantra has certain flavours from other games, especially Gauntlet (TM) |
11 | and Nethack/Moria. |
11 | and Nethack/Moria. |
12 | |
12 | |
13 | Any number of players can move around in their own window on the |
13 | Any number of players can move around in their own window on the |
14 | world, finding and using items and battle monsters. They can choose to |
14 | world, finding and using items and battle monsters. They can choose to |
15 | cooperate or compete in the same "world". |
15 | cooperate or compete in the same "world". |
… | |
… | |
40 | - Time::HiRes >= v1.0 |
40 | - Time::HiRes >= v1.0 |
41 | - URI >= 1.35 |
41 | - URI >= 1.35 |
42 | - YAML >= v0.62 |
42 | - YAML >= v0.62 |
43 | - YAML::Syck >= v0.71 |
43 | - YAML::Syck >= v0.71 |
44 | |
44 | |
45 | **NOTICE**: Crossfire uses an alternative signal stack, so you have to |
45 | **NOTICE**: Deliantra uses an alternative signal stack, so you have to |
46 | use either the "u"context method (slow) or "a"ssembly when configuring Coro. |
46 | use either the "u"context method (slow) or "a"ssembly when configuring Coro. |
47 | |
47 | |
48 | Furthermore, you will need the following programs and libraries: |
48 | Furthermore, you will need the following programs and libraries: |
49 | |
49 | |
50 | - gperf, the GNU perfect hash generator >= v3.0 |
50 | - gperf, the GNU perfect hash generator >= v3.0 |
… | |
… | |
70 | binutils) in your PATH. |
70 | binutils) in your PATH. |
71 | |
71 | |
72 | |
72 | |
73 | COMPILING |
73 | COMPILING |
74 | |
74 | |
75 | Crossfire has been known to compile on a wide variety of systems. It should |
75 | Deliantra has been known to compile on a wide variety of systems. It should |
76 | compile and run on most ISO C++ 200x and POSIX compliant systems. |
76 | compile and run on most ISO C++ 200x and POSIX compliant systems. |
77 | |
77 | |
78 | To get generic directions on compilation, read the INSTALL file. |
78 | To get generic directions on compilation, read the INSTALL file. |
79 | |
79 | |
80 | |
80 | |
81 | INSTALLATION/USAGE |
81 | INSTALLATION/USAGE |
82 | |
82 | |
83 | Crossfire runs on a client/server model. You will also a client to |
83 | Deliantra runs on a client/server model. You will also a client to |
84 | play. You can either connect to a server someone else has set up, or |
84 | play. You can either connect to a server someone else has set up, or |
85 | run your own server and connect to that. There are a number of clients |
85 | run your own server and connect to that. There are a number of clients |
86 | available, but the recommended one is CFPlus (see below for URL). |
86 | available, but the recommended one is CFPlus (see below for URL). |
87 | |
87 | |
88 | To run your own server, you need to build the crossfire server binaries |
88 | To run your own server, you need to build the deliantra server binaries |
89 | and install them, then you will have to download and install map and |
89 | and install them, then you will have to download and install map and |
90 | archetype packs: |
90 | archetype packs: |
91 | |
91 | |
92 | Download both the cfmaps-<version> and cfarch-<version> archives, then |
92 | Download both the cfmaps-<version> and cfarch-<version> archives, then |
93 | use cfutil to install both (the source directories must be writable for |
93 | use cfutil to install both (the source directories must be writable for |
… | |
… | |
102 | of cfutil: |
102 | of cfutil: |
103 | |
103 | |
104 | cfutil --cache --install-maps path/to/cfmaps-<version>/ |
104 | cfutil --cache --install-maps path/to/cfmaps-<version>/ |
105 | cfutil --cache --install-arch path/to/cfarch-<version>/ |
105 | cfutil --cache --install-arch path/to/cfarch-<version>/ |
106 | |
106 | |
107 | Atfer this you can then run the crossfire executable. This starts a |
107 | Atfer this you can then run the deliantra executable. This starts a |
108 | server which you/other people can connect to. |
108 | server which you/other people can connect to. |
109 | |
109 | |
110 | |
110 | |
111 | WEB SITES |
111 | WEB SITES |
112 | |
112 | |
113 | The following web addresses have crossfire information that you may find |
113 | The following web addresses have deliantra information that you may find |
114 | useful: |
114 | useful: |
115 | |
115 | |
116 | http://crossfire.schmorp.de/ (The main site) |
116 | http://www.deliantra.net/ (The main site) |
117 | |
|
|
118 | http://crossfire.real-time.com/ (The website for the old Crossfire game) |
|
|
119 | |
117 | |
120 | |
118 | |
121 | REPORTING BUGS |
119 | REPORTING BUGS |
122 | |
120 | |
123 | First, check the INSTALL file for common problems, and see if yours is |
121 | First, check the INSTALL file for common problems, and see if yours is |
124 | mentioned. |
122 | mentioned. |
125 | |
123 | |
126 | Bugs should be filed using the following email address: |
124 | Bugs should be filed using the following email address: |
127 | crossfire@schmorp.de |
125 | support@deliantra.net |
128 | |
126 | |
129 | When reporting bugs, make sure you include the following: |
127 | When reporting bugs, make sure you include the following: |
130 | |
128 | |
131 | * What version of crossfire did you use? |
129 | * What version of deliantra did you use? |
132 | * What type of computer did you use (CPU type) |
130 | * What type of computer did you use (CPU type) |
133 | * What is the version of the OS? |
131 | * What is the version of the OS? |
134 | * What windowing system are you using (e.g. openwindows, X.org, XFree86) |
132 | * What windowing system are you using (e.g. openwindows, X.org, XFree86) |
135 | * What compiler (and its version) did you use (e.g. gcc, acc)? |
133 | * What compiler (and its version) did you use (e.g. gcc, acc)? |
136 | * Which flags did you give it? |
134 | * Which flags did you give it? |
137 | * If the bug happens when compiling crossfire, send an EXACT copy of the |
135 | * If the bug happens when compiling deliantra, send an EXACT copy of the |
138 | compiler line, as well as the errors it puts out. Sending bugs of the |
136 | compiler line, as well as the errors it puts out. Sending bugs of the |
139 | sort 'it failed with a line like ...' doesn't help any. |
137 | sort 'it failed with a line like ...' doesn't help any. |
140 | * If the bug happened while running crossfire: |
138 | * If the bug happened while running deliantra: |
141 | - Include any output before to the bug. |
139 | - Include any output before to the bug. |
142 | - Give a description of what you did before the bug occured. The better |
140 | - Give a description of what you did before the bug occured. The better |
143 | detailed the description, the better chance we have of figuring |
141 | detailed the description, the better chance we have of figuring |
144 | out where the bug happened, or how we can recreate the bug. |
142 | out where the bug happened, or how we can recreate the bug. |
145 | - If possible, a stack trace from gdb (or other debugger) is very |
143 | - If possible, a stack trace from gdb (or other debugger) is very |
… | |
… | |
150 | |
148 | |
151 | |
149 | |
152 | SUBMITTING PATCHES |
150 | SUBMITTING PATCHES |
153 | |
151 | |
154 | Patches should be submitted to email address: |
152 | Patches should be submitted to email address: |
155 | crossfire@schmorp.de |
153 | support@deliantra.net |
156 | |
154 | |
157 | |
155 | |
158 | PUBLIC SERVERS |
156 | PUBLIC SERVERS |
159 | |
157 | |
160 | The best way to find a server to play is to run the client |
158 | The best way to find a server to play is to run the client |
161 | and hit "Server List" in the setup dialog (this varies |
159 | and hit "Server List" in the setup dialog (this varies |
162 | depending on your client). You can also see a list at |
160 | depending on your client). |
163 | http://crossfire.real-time.com/metaserver/. |
|
|
164 | |
161 | |
165 | The canonical server for use with Crossfire and CFPlus is |
162 | The canonical server for use with Deliantra and CFPlus is |
166 | crossfire.schmorp.de, port 13327 (default). |
163 | gameserver.deliantra.net, port 13327 (the default). |
167 | |
164 | |
168 | |
165 | |
169 | COPYRIGHT |
166 | COPYRIGHT |
170 | |
167 | |
171 | Most files in this distribution are covered by the GNU General Public |
168 | Most files in this distribution are covered by the GNU General Public |
… | |
… | |
177 | given in ext/affero.ext. |
174 | given in ext/affero.ext. |
178 | |
175 | |
179 | |
176 | |
180 | CONTACT |
177 | CONTACT |
181 | |
178 | |
182 | The authors can be reached via e-mail to crossfire@schmorp.de |
179 | The authors can be reached via e-mail to support@deliantra.net |
183 | |
180 | |