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