1 |
root |
1.1 |
WHAT IS CROSSFIRE? |
2 |
|
|
|
3 |
pippijn |
1.4 |
This is a multiplayer graphical arcade and adventure game, that runs on a |
4 |
|
|
client/server model. There are clients for Microsoft(R) Windows(TM) and |
5 |
|
|
POSIX systems such as Linux and *BSD. To get the most joyful experience, |
6 |
|
|
the Crossfire+ client should be used. This client is written in Perl and |
7 |
|
|
utilises SDL with OpenGL. |
8 |
root |
1.1 |
|
9 |
pippijn |
1.4 |
Crossfire has certain flavours from other games, especially Gauntlet (TM) |
10 |
root |
1.1 |
and Nethack/Moria. |
11 |
|
|
|
12 |
|
|
Any number of players can move around in their own window, finding |
13 |
|
|
and using items and battle monsters. They can choose to cooperate |
14 |
|
|
or compete in the same "world". |
15 |
|
|
|
16 |
|
|
REQUIREMENTS |
17 |
|
|
|
18 |
root |
1.5 |
For UNIX, a modern C++ compiler with some extensions is required to |
19 |
|
|
compile this game. In addition, you will need the Perl development |
20 |
|
|
libraries along with the following Perl modules (the server is tested |
21 |
|
|
with perl 5.8.8 and 5.8-maint). |
22 |
pippijn |
1.4 |
|
23 |
|
|
- Crossfire >= v0.97 |
24 |
|
|
- Coro >= v3.5 |
25 |
|
|
- Coro::Event >= v2.1 |
26 |
|
|
- Event >= v1.08 |
27 |
|
|
- IO::AIO >= 2.32 |
28 |
|
|
- BDB >= v0.1 |
29 |
|
|
- Storable >= v2.0 |
30 |
|
|
- Time::HiRes >= v1.0 |
31 |
|
|
- YAML::Syck >= v0.71 |
32 |
|
|
- Digest::MD5 >= v2.0 |
33 |
|
|
- Compress::LZF >= v1.71 |
34 |
|
|
- Safe::Hole >= v0.10 |
35 |
|
|
- Pod::POM >= v0.17 |
36 |
|
|
|
37 |
root |
1.5 |
Furthermore, you will need the following programs and libraries: |
38 |
pippijn |
1.4 |
|
39 |
root |
1.7 |
- gperf, the GNU perfect hash generator >= v3.0 |
40 |
pippijn |
1.4 |
- glib-2.0 >= v2.10 |
41 |
|
|
- libpng >= v1.2 |
42 |
root |
1.7 |
- ImageMagick >= v6.0 |
43 |
|
|
- optipng => v0.5.5 (http://optipng.sf.net) |
44 |
|
|
- rsync >= 2.6 (a must have anyways) |
45 |
pippijn |
1.4 |
|
46 |
root |
1.5 |
Your compiler must support the Library Technical Report 1 extensions and |
47 |
|
|
the upcoming typeof extension. The GNU C++ compiler >= version 4.0 does |
48 |
root |
1.6 |
support all these. |
49 |
pippijn |
1.4 |
|
50 |
root |
1.1 |
COMPILING |
51 |
|
|
|
52 |
pippijn |
1.4 |
Crossfire has been known to compile on a wide variety of systems. It should |
53 |
|
|
compile and most all ISO C++ 200x and POSIX compliant systems. |
54 |
root |
1.1 |
|
55 |
|
|
To get directions on compilation for UNIX/LINUX, read the INSTALL file. |
56 |
|
|
|
57 |
|
|
USAGE |
58 |
|
|
|
59 |
root |
1.5 |
Crossfire runs on a client/server model. You will also need the client |
60 |
|
|
to play. You can either connect to a server someone else has set up, |
61 |
|
|
or run your own server and connect to that. The client package has |
62 |
|
|
information for connecting to servers. |
63 |
|
|
|
64 |
|
|
To run your own server, you need to make the crossfire binaries |
65 |
|
|
and install them, and then run the crossfire program. This now |
66 |
|
|
creates a server which you/other people can connect to. The map |
67 |
|
|
files will need to get downloaded and installed for the server to run |
68 |
|
|
properly. The map pack is released together with the server and can be |
69 |
|
|
downloaded form the same location. The maps should be copied into the |
70 |
|
|
$(TARGET)/share/crossfire/maps directory - after unpacking, you should |
71 |
|
|
have a $(TARGET)/share/crossfire/maps/scorn directory. |
72 |
root |
1.2 |
|
73 |
|
|
If you plan to run a long term server, you should use one of the scripts |
74 |
|
|
provided that will re-run crossfire if it dies for some reason. |
75 |
root |
1.1 |
|
76 |
|
|
WEB SITES: |
77 |
|
|
|
78 |
|
|
The following web addresses have crossfire information that you may find |
79 |
|
|
useful: |
80 |
|
|
|
81 |
pippijn |
1.4 |
http://crossfire.schmorp.de/ (The main site) |
82 |
|
|
|
83 |
|
|
http://crossfire.real-time.com/ (The website for the old Crossfire game) |
84 |
root |
1.1 |
|
85 |
|
|
|
86 |
|
|
REPORTING BUGS |
87 |
|
|
|
88 |
|
|
First, check the INSTALL file for common problems, and see if yours is |
89 |
|
|
mentioned. |
90 |
|
|
|
91 |
pippijn |
1.4 |
Bugs should be filed using the following email address: |
92 |
|
|
crossfire@schmorp.de |
93 |
root |
1.1 |
|
94 |
|
|
When reporting bugs, make sure you include the following: |
95 |
|
|
o What version of crossfire did you use? |
96 |
root |
1.2 |
o What type of computer did you use (CPU type) |
97 |
|
|
o What is the version of the OS? |
98 |
pippijn |
1.4 |
o What windowing system are you using (e.g. openwindows, X.org, XFree86) |
99 |
|
|
o What compiler (and its version) did you use (e.g. gcc, acc)? |
100 |
root |
1.1 |
o Which flags did you give it? |
101 |
pippijn |
1.4 |
o If the bug happens when compiling crossfire, send an EXACT copy of the |
102 |
|
|
compiler line, as well as the errors it puts out. Sending bugs of the |
103 |
|
|
sort 'it failed with a line like ...' doesn't help any. |
104 |
root |
1.1 |
o If the bug happened while running crossfire: |
105 |
|
|
- Include any output before to the bug. |
106 |
|
|
- Give a description of what you did before the bug occured. The better |
107 |
pippijn |
1.4 |
detailed the description, the better chance I have of figuring |
108 |
|
|
out where the bug happened, or how I can recreate the bug. |
109 |
root |
1.2 |
- If possible, a stack trace from gdb (or other debugger) is very |
110 |
|
|
helpful. |
111 |
root |
1.1 |
|
112 |
root |
1.2 |
The more information provided, the better chance of the bug being fixed in |
113 |
|
|
a timely fashion. |
114 |
root |
1.1 |
|
115 |
|
|
------------------------------------------------------------------------------ |
116 |
pippijn |
1.4 |
SUBMITTING PATCHES: |
117 |
|
|
Patches should be submitted to email address: |
118 |
|
|
crossfire@schmorp.de |
119 |
root |
1.1 |
|
120 |
|
|
PUBLIC SERVERS: |
121 |
|
|
|
122 |
|
|
The best way to find a server to play is to run the client. It will contact |
123 |
|
|
the metaserver and present a list to choose from. You can also see |
124 |
|
|
a list at http://crossfire.real-time.com/metaserver/ |
125 |
|
|
|
126 |
|
|
|
127 |
|
|
COPYRIGHT |
128 |
|
|
|
129 |
pippijn |
1.4 |
Copyright (C) 2007 Crossfire Development Team |
130 |
|
|
Copyright (C) 2000, 2006 Mark Wedel |
131 |
root |
1.1 |
Copyright (C) 1992 Frank Tore Johansen |
132 |
|
|
|
133 |
|
|
This program is free software; you can redistribute it and/or modify |
134 |
|
|
it under the terms of the GNU General Public License as published by |
135 |
|
|
the Free Software Foundation; either version 2 of the License, or |
136 |
|
|
(at your option) any later version. |
137 |
|
|
|
138 |
|
|
This program is distributed in the hope that it will be useful, |
139 |
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of |
140 |
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the |
141 |
|
|
GNU General Public License for more details. |
142 |
|
|
|
143 |
|
|
You should have received a copy of the GNU General Public License |
144 |
|
|
along with this program; if not, write to the Free Software |
145 |
|
|
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. |
146 |
|
|
|
147 |
pippijn |
1.4 |
The authors can be reached via e-mail to crossfire@schmorp.de |