| 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 |
|
|
The client runs with X11, GTK, or SDL within a gtk window. |
| 6 |
|
|
|
| 7 |
|
|
It has certain flavours from other games, especially Gauntlet (TM) |
| 8 |
|
|
and Nethack/Moria. |
| 9 |
|
|
|
| 10 |
|
|
Any number of players can move around in their own window, finding |
| 11 |
|
|
and using items and battle monsters. They can choose to cooperate |
| 12 |
|
|
or compete in the same "world". |
| 13 |
|
|
|
| 14 |
|
|
REQUIREMENTS |
| 15 |
|
|
|
| 16 |
|
|
For UNIX, X-windows and an ANSI C compiler to compile this game. |
| 17 |
|
|
A window system is not needed if you don't want to compile the |
| 18 |
|
|
map editor. |
| 19 |
|
|
|
| 20 |
|
|
For Windows 9x, you need Visual C++ (or some other ANSI C |
| 21 |
|
|
compiler that can read ".dsw"-files). |
| 22 |
|
|
|
| 23 |
|
|
COMPILING |
| 24 |
|
|
|
| 25 |
|
|
Crossfire has been known to compile on a wide variety of |
| 26 |
|
|
systems. It should compile and most all ANSI C and Posix |
| 27 |
|
|
compliant systems. |
| 28 |
|
|
|
| 29 |
|
|
To get directions on compilation for UNIX/LINUX, 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 |
|
|
|
| 58 |
|
|
|
| 59 |
|
|
FTP SITES |
| 60 |
|
|
|
| 61 |
|
|
FTP-sites where you can look for the latest versions are: |
| 62 |
|
|
|
| 63 |
|
|
ftp://ftp.sourceforge.net/pub/sourceforge/crossfire |
| 64 |
|
|
ftp://ftp.real-time.com/pub/games/crossfire |
| 65 |
|
|
|
| 66 |
|
|
Changes made since the latest release can be found at the CVS |
| 67 |
|
|
repository. Information on anonymous CVS access as |
| 68 |
|
|
the download CVS snapshots and browsing the repository can be |
| 69 |
|
|
found at: |
| 70 |
|
|
http://sourceforge.net/cvs/?group_id=13833 |
| 71 |
|
|
|
| 72 |
|
|
|
| 73 |
|
|
If you are looking for a windows/NT client, look at: |
| 74 |
|
|
http://mids.student.utwente.nl/%7Emichtoen/crossfire/ |
| 75 |
|
|
|
| 76 |
|
|
WEB SITES: |
| 77 |
|
|
|
| 78 |
|
|
The following web addresses have crossfire information that you may find |
| 79 |
|
|
useful: |
| 80 |
|
|
|
| 81 |
|
|
http://crossfire.real-time.com/ |
| 82 |
|
|
real-time is the main crossfire site. |
| 83 |
|
|
|
| 84 |
|
|
|
| 85 |
|
|
REPORTING BUGS |
| 86 |
|
|
|
| 87 |
|
|
First, check the INSTALL file for common problems, and see if yours is |
| 88 |
|
|
mentioned. |
| 89 |
|
|
|
| 90 |
|
|
The mailing list is where present development work and bugs are typically |
| 91 |
|
|
discussed. If you want to know what is happening with crossfire, join the |
| 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 |
|
|
|
| 102 |
|
|
When reporting bugs, make sure you include the following: |
| 103 |
|
|
o What version of crossfire did you use? |
| 104 |
|
|
o What type of computer did you use? |
| 105 |
|
|
o What release of the operating system did it have? |
| 106 |
|
|
o What windowing system are you using (Ie, openwindows, X11R6, etc) |
| 107 |
|
|
o What compiler (and its version) did you use (ie, gcc, acc, etc)? |
| 108 |
|
|
o Which flags did you give it? |
| 109 |
|
|
o If the bug happens when compiling crossfire, send an EXACT copy of |
| 110 |
|
|
the compiler line, as well as the errors it puts out. Sending bugs |
| 111 |
|
|
of the sort 'it failed with a line like ...' doesn't help any. |
| 112 |
|
|
o If the bug happened while running crossfire: |
| 113 |
|
|
- Include any output before to the bug. |
| 114 |
|
|
- Give a description of what you did before the bug occured. The better |
| 115 |
|
|
detailed the description, the better chance I have of figuring |
| 116 |
|
|
out where the bug happened, or how I can recreate the bug. |
| 117 |
|
|
o If you managed to compile Crossfire, include the output of |
| 118 |
|
|
"crossfire -o". |
| 119 |
|
|
|
| 120 |
|
|
Lack of any of this information in a bug report can make that bug report |
| 121 |
|
|
useless. Also, if you have a bug, make sure you are using the latest |
| 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 |
|
|
|
| 133 |
|
|
|
| 134 |
|
|
PUBLIC SERVERS: |
| 135 |
|
|
|
| 136 |
|
|
The best way to find a server to play is to run the client. It will contact |
| 137 |
|
|
the metaserver and present a list to choose from. You can also see |
| 138 |
|
|
a list at http://crossfire.real-time.com/metaserver/ |
| 139 |
|
|
|
| 140 |
|
|
|
| 141 |
|
|
COPYRIGHT |
| 142 |
|
|
|
| 143 |
|
|
Don't get scared by the below, it's included just for "safety" reasons 8) |
| 144 |
|
|
(Don't want anyone to start selling the game) |
| 145 |
|
|
|
| 146 |
|
|
Copyright (C) 2000 Mark Wedel |
| 147 |
|
|
Copyright (C) 1992 Frank Tore Johansen |
| 148 |
|
|
|
| 149 |
|
|
This program is free software; you can redistribute it and/or modify |
| 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 |
|
|
|
| 154 |
|
|
This program is distributed in the hope that it will be useful, |
| 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 |
|
|
|
| 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 |
