1 |
root |
1.1 |
WHAT IS CROSSFIRE? |
2 |
|
|
|
3 |
|
|
This is a multiplayer graphical arcade and adventure game made for |
4 |
|
|
the X-Windows environment. It runs on a client/server model. |
5 |
root |
1.2 |
The client runs with X11, GTK, or SDL within a gtk window. A |
6 |
|
|
windows client is available, and a java client is under development. |
7 |
root |
1.1 |
|
8 |
|
|
It has certain flavours from other games, especially Gauntlet (TM) |
9 |
|
|
and Nethack/Moria. |
10 |
|
|
|
11 |
|
|
Any number of players can move around in their own window, finding |
12 |
|
|
and using items and battle monsters. They can choose to cooperate |
13 |
|
|
or compete in the same "world". |
14 |
|
|
|
15 |
|
|
REQUIREMENTS |
16 |
|
|
|
17 |
|
|
For UNIX, X-windows and an ANSI C compiler to compile this game. |
18 |
|
|
A window system is not needed if you don't want to compile the |
19 |
|
|
map editor. |
20 |
|
|
|
21 |
|
|
For Windows 9x, you need Visual C++ (or some other ANSI C |
22 |
|
|
compiler that can read ".dsw"-files). |
23 |
|
|
|
24 |
|
|
COMPILING |
25 |
|
|
|
26 |
|
|
Crossfire has been known to compile on a wide variety of |
27 |
|
|
systems. It should compile and most all ANSI C and Posix |
28 |
|
|
compliant systems. |
29 |
|
|
|
30 |
|
|
To get directions on compilation for UNIX/LINUX, read the INSTALL file. |
31 |
|
|
For Win9x, read INSTALL_WIN32.txt. |
32 |
|
|
|
33 |
|
|
USAGE |
34 |
|
|
|
35 |
|
|
Crossfire runs on a client/server model. You will also need the |
36 |
|
|
client to play. You can either connect to a server someone else |
37 |
|
|
has set up, or run your own server and connect to that. The |
38 |
|
|
client package has information for connecting to servers. |
39 |
|
|
|
40 |
|
|
To run your own server, you need to make the crossfire binaries and install |
41 |
|
|
them, and then run the crossfire program. This now creates a server which |
42 |
|
|
you/other people can connect to. The map files will need to get downloaded |
43 |
root |
1.2 |
and installed for the server to run properly. The maps should be |
44 |
|
|
unpacked in the $(TARGET)/share/crossfire directory - after unpacking, |
45 |
|
|
you should have a $(TARGET)/share/crossfire/maps directory. |
46 |
|
|
|
47 |
|
|
If you plan to run a long term server, you should use one of the scripts |
48 |
|
|
provided that will re-run crossfire if it dies for some reason. |
49 |
root |
1.1 |
|
50 |
|
|
MAILING LIST |
51 |
|
|
|
52 |
|
|
For the latest subscription for crossfire mailing lists, go to: |
53 |
root |
1.2 |
http://crossfire.real-time.com/mailinglists/index.html |
54 |
root |
1.1 |
|
55 |
|
|
From there you should be able to subscribe/unsubscribe any of the mailing |
56 |
root |
1.2 |
lists. Links to archives of the mailing lists can be found there, as well |
57 |
|
|
as at: |
58 |
|
|
http://gmane.org/find.php?list=crossfire |
59 |
root |
1.1 |
|
60 |
|
|
|
61 |
|
|
FTP SITES |
62 |
|
|
|
63 |
|
|
FTP-sites where you can look for the latest versions are: |
64 |
|
|
|
65 |
root |
1.2 |
http://prdownloads.sourceforge.net/crossfire/ |
66 |
root |
1.1 |
ftp://ftp.real-time.com/pub/games/crossfire |
67 |
|
|
|
68 |
|
|
Changes made since the latest release can be found at the CVS |
69 |
|
|
repository. Information on anonymous CVS access as |
70 |
|
|
the download CVS snapshots and browsing the repository can be |
71 |
|
|
found at: |
72 |
|
|
http://sourceforge.net/cvs/?group_id=13833 |
73 |
|
|
|
74 |
|
|
|
75 |
|
|
WEB SITES: |
76 |
|
|
|
77 |
|
|
The following web addresses have crossfire information that you may find |
78 |
|
|
useful: |
79 |
|
|
|
80 |
|
|
http://crossfire.real-time.com/ |
81 |
|
|
real-time is the main crossfire site. |
82 |
|
|
|
83 |
|
|
|
84 |
|
|
REPORTING BUGS |
85 |
|
|
|
86 |
|
|
First, check the INSTALL file for common problems, and see if yours is |
87 |
|
|
mentioned. |
88 |
|
|
|
89 |
root |
1.2 |
Bugs should be filed at the sourceforge web site: |
90 |
|
|
http://sourceforge.net/cvs/?group_id=13833 |
91 |
root |
1.1 |
|
92 |
|
|
When reporting bugs, make sure you include the following: |
93 |
root |
1.2 |
o If you have a sourceforge login, make sure you are logged in. In this |
94 |
|
|
way, if there are questions about the bug, you will be notified about |
95 |
|
|
the request for more information. |
96 |
root |
1.1 |
o What version of crossfire did you use? |
97 |
root |
1.2 |
o What type of computer did you use (CPU type) |
98 |
|
|
o What is the version of the OS? |
99 |
root |
1.1 |
o What windowing system are you using (Ie, openwindows, X11R6, etc) |
100 |
|
|
o What compiler (and its version) did you use (ie, gcc, acc, etc)? |
101 |
|
|
o Which flags did you give it? |
102 |
|
|
o If the bug happens when compiling crossfire, send an EXACT copy of |
103 |
|
|
the compiler line, as well as the errors it puts out. Sending bugs |
104 |
|
|
of the sort 'it failed with a line like ...' doesn't help any. |
105 |
|
|
o If the bug happened while running crossfire: |
106 |
|
|
- Include any output before to the bug. |
107 |
|
|
- Give a description of what you did before the bug occured. The better |
108 |
|
|
detailed the description, the better chance I have of figuring |
109 |
|
|
out where the bug happened, or how I can recreate the bug. |
110 |
root |
1.2 |
- If possible, a stack trace from gdb (or other debugger) is very |
111 |
|
|
helpful. |
112 |
root |
1.1 |
|
113 |
root |
1.2 |
The more information provided, the better chance of the bug being fixed in |
114 |
|
|
a timely fashion. |
115 |
root |
1.1 |
|
116 |
|
|
Further debugging informatiion can be found at |
117 |
|
|
http://crossfire.real-time.com/debugging_tips.html |
118 |
|
|
|
119 |
|
|
------------------------------------------------------------------------------ |
120 |
|
|
SUBMITTING PATCHES: See the doc/programming_guide file. |
121 |
root |
1.2 |
The patches should be submitted to the patch tracker on sourceforge: |
122 |
|
|
http://sourceforge.net/cvs/?group_id=13833 |
123 |
root |
1.1 |
|
124 |
|
|
PUBLIC SERVERS: |
125 |
|
|
|
126 |
|
|
The best way to find a server to play is to run the client. It will contact |
127 |
|
|
the metaserver and present a list to choose from. You can also see |
128 |
|
|
a list at http://crossfire.real-time.com/metaserver/ |
129 |
|
|
|
130 |
|
|
|
131 |
|
|
COPYRIGHT |
132 |
|
|
|
133 |
|
|
Don't get scared by the below, it's included just for "safety" reasons 8) |
134 |
|
|
(Don't want anyone to start selling the game) |
135 |
|
|
|
136 |
root |
1.2 |
Copyright (C) 2000,2006 Mark Wedel |
137 |
root |
1.1 |
Copyright (C) 1992 Frank Tore Johansen |
138 |
|
|
|
139 |
|
|
This program is free software; you can redistribute it and/or modify |
140 |
|
|
it under the terms of the GNU General Public License as published by |
141 |
|
|
the Free Software Foundation; either version 2 of the License, or |
142 |
|
|
(at your option) any later version. |
143 |
|
|
|
144 |
|
|
This program is distributed in the hope that it will be useful, |
145 |
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of |
146 |
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the |
147 |
|
|
GNU General Public License for more details. |
148 |
|
|
|
149 |
|
|
You should have received a copy of the GNU General Public License |
150 |
|
|
along with this program; if not, write to the Free Software |
151 |
|
|
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. |
152 |
|
|
|
153 |
root |
1.3 |
The author can be reached via e-mail to crossfire@schmorp.de |