1 | WHAT IS CROSSFIRE? |
1 | WHAT IS CROSSFIRE? |
2 | |
2 | |
3 | This is a multiplayer graphical arcade and adventure game made for |
3 | This is a multiplayer graphical arcade and adventure game, that runs on a |
4 | the X-Windows environment. It runs on a client/server model. |
4 | client/server model. There are clients for Microsoft(R) Windows(TM) and |
5 | The client runs with X11, GTK, or SDL within a gtk window. |
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. |
6 | |
8 | |
7 | It has certain flavours from other games, especially Gauntlet (TM) |
9 | Crossfire has certain flavours from other games, especially Gauntlet (TM) |
8 | and Nethack/Moria. |
10 | and Nethack/Moria. |
9 | |
11 | |
10 | Any number of players can move around in their own window, finding |
12 | Any number of players can move around in their own window, finding |
11 | and using items and battle monsters. They can choose to cooperate |
13 | and using items and battle monsters. They can choose to cooperate |
12 | or compete in the same "world". |
14 | or compete in the same "world". |
13 | |
15 | |
14 | REQUIREMENTS |
16 | REQUIREMENTS |
15 | |
17 | |
16 | For UNIX, X-windows and an ANSI C compiler to compile this game. |
18 | For UNIX, the ISO C++ 200x compiler are required to compile this game. In |
17 | A window system is not needed if you don't want to compile the |
19 | addition, you will need the Perl development libraries along with the |
18 | map editor. |
20 | following Perl modules: |
19 | |
21 | |
20 | For Windows 9x, you need Visual C++ (or some other ANSI C |
22 | - Crossfire >= v0.97 |
21 | compiler that can read ".dsw"-files). |
23 | - Coro >= v3.5 |
22 | |
24 | - Coro::Event >= v2.1 |
|
|
25 | - Event >= v1.08 |
|
|
26 | - IO::AIO >= 2.32 |
|
|
27 | - BDB >= v0.1 |
|
|
28 | - Storable >= v2.0 |
|
|
29 | - Time::HiRes >= v1.0 |
|
|
30 | - YAML::Syck >= v0.71 |
|
|
31 | - Digest::MD5 >= v2.0 |
|
|
32 | - Compress::LZF >= v1.71 |
|
|
33 | - Safe::Hole >= v0.10 |
|
|
34 | - Pod::POM >= v0.17 |
|
|
35 | |
|
|
36 | Furthermore, to build the crossfire server you will need the following: |
|
|
37 | |
|
|
38 | - gperf, the GNU perfect hash generator |
|
|
39 | - glib-2.0 >= v2.10 |
|
|
40 | - libpng >= v1.2 |
|
|
41 | |
|
|
42 | Your compiler must support the Library Technical Report 1 extensions. |
|
|
43 | The GNU C++ compiler >= version 4.0 does support these. |
|
|
44 | |
23 | COMPILING |
45 | COMPILING |
24 | |
46 | |
25 | Crossfire has been known to compile on a wide variety of |
47 | Crossfire has been known to compile on a wide variety of systems. It should |
26 | systems. It should compile and most all ANSI C and Posix |
48 | compile and most all ISO C++ 200x and POSIX compliant systems. |
27 | compliant systems. |
|
|
28 | |
49 | |
29 | To get directions on compilation for UNIX/LINUX, read the INSTALL file. |
50 | To get directions on compilation for UNIX/LINUX, read the INSTALL file. |
30 | For Win9x, read INSTALL_WIN32.txt. |
|
|
31 | |
51 | |
32 | USAGE |
52 | USAGE |
33 | |
53 | |
34 | Crossfire runs on a client/server model. You will also need the |
54 | Crossfire runs on a client/server model. You will also need the client to |
35 | client to play. You can either connect to a server someone else |
55 | play. You can either connect to a server someone else has set up, or run |
36 | has set up, or run your own server and connect to that. The |
56 | your own server and connect to that. The client package has information for |
37 | client package has information for connecting to servers. |
57 | connecting to servers. |
38 | |
58 | |
39 | To run your own server, you need to make the crossfire binaries and install |
59 | 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 |
60 | 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 |
61 | 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 |
62 | and installed for the server to run properly. The maps should be unpacked in |
43 | term server, you should use one of the scripts provided that will re-run |
63 | the $(TARGET)/share/crossfire directory - after unpacking, you should have a |
44 | crossfire if it dies for some reason. |
64 | $(TARGET)/share/crossfire/maps directory. |
45 | |
65 | |
46 | MAILING LIST |
66 | If you plan to run a long term server, you should use one of the scripts |
47 | |
67 | provided that will re-run crossfire if it dies for some reason. |
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 | |
68 | |
76 | WEB SITES: |
69 | WEB SITES: |
77 | |
70 | |
78 | The following web addresses have crossfire information that you may find |
71 | The following web addresses have crossfire information that you may find |
79 | useful: |
72 | useful: |
80 | |
73 | |
81 | http://crossfire.real-time.com/ |
74 | http://crossfire.schmorp.de/ (The main site) |
82 | real-time is the main crossfire site. |
75 | |
|
|
76 | http://crossfire.real-time.com/ (The website for the old Crossfire game) |
83 | |
77 | |
84 | |
78 | |
85 | REPORTING BUGS |
79 | REPORTING BUGS |
86 | |
80 | |
87 | First, check the INSTALL file for common problems, and see if yours is |
81 | First, check the INSTALL file for common problems, and see if yours is |
88 | mentioned. |
82 | mentioned. |
89 | |
83 | |
90 | The mailing list is where present development work and bugs are typically |
84 | Bugs should be filed using the following email address: |
91 | discussed. If you want to know what is happening with crossfire, join the |
85 | crossfire@schmorp.de |
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 | |
86 | |
102 | When reporting bugs, make sure you include the following: |
87 | When reporting bugs, make sure you include the following: |
103 | o What version of crossfire did you use? |
88 | o What version of crossfire did you use? |
104 | o What type of computer did you use? |
89 | o What type of computer did you use (CPU type) |
105 | o What release of the operating system did it have? |
90 | o What is the version of the OS? |
106 | o What windowing system are you using (Ie, openwindows, X11R6, etc) |
91 | o What windowing system are you using (e.g. openwindows, X.org, XFree86) |
107 | o What compiler (and its version) did you use (ie, gcc, acc, etc)? |
92 | o What compiler (and its version) did you use (e.g. gcc, acc)? |
108 | o Which flags did you give it? |
93 | o Which flags did you give it? |
109 | o If the bug happens when compiling crossfire, send an EXACT copy of |
94 | o If the bug happens when compiling crossfire, send an EXACT copy of the |
110 | the compiler line, as well as the errors it puts out. Sending bugs |
95 | compiler line, as well as the errors it puts out. Sending bugs of the |
111 | of the sort 'it failed with a line like ...' doesn't help any. |
96 | sort 'it failed with a line like ...' doesn't help any. |
112 | o If the bug happened while running crossfire: |
97 | o If the bug happened while running crossfire: |
113 | - Include any output before to the bug. |
98 | - Include any output before to the bug. |
114 | - Give a description of what you did before the bug occured. The better |
99 | - Give a description of what you did before the bug occured. The better |
115 | detailed the description, the better chance I have of figuring |
100 | detailed the description, the better chance I have of figuring |
116 | out where the bug happened, or how I can recreate the bug. |
101 | out where the bug happened, or how I can recreate the bug. |
117 | o If you managed to compile Crossfire, include the output of |
102 | - If possible, a stack trace from gdb (or other debugger) is very |
118 | "crossfire -o". |
103 | helpful. |
119 | |
104 | |
120 | Lack of any of this information in a bug report can make that bug report |
105 | The more information provided, the better chance of the bug being fixed in |
121 | useless. Also, if you have a bug, make sure you are using the latest |
106 | a timely fashion. |
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 | |
107 | |
130 | ------------------------------------------------------------------------------ |
108 | ------------------------------------------------------------------------------ |
131 | SUBMITTING PATCHES: See the doc/programming_guide file. |
109 | SUBMITTING PATCHES: |
132 | |
110 | Patches should be submitted to email address: |
|
|
111 | crossfire@schmorp.de |
133 | |
112 | |
134 | PUBLIC SERVERS: |
113 | PUBLIC SERVERS: |
135 | |
114 | |
136 | The best way to find a server to play is to run the client. It will contact |
115 | 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 |
116 | the metaserver and present a list to choose from. You can also see |
138 | a list at http://crossfire.real-time.com/metaserver/ |
117 | a list at http://crossfire.real-time.com/metaserver/ |
139 | |
118 | |
140 | |
119 | |
141 | COPYRIGHT |
120 | COPYRIGHT |
142 | |
121 | |
143 | Don't get scared by the below, it's included just for "safety" reasons 8) |
122 | Copyright (C) 2007 Crossfire Development Team |
144 | (Don't want anyone to start selling the game) |
|
|
145 | |
|
|
146 | Copyright (C) 2000 Mark Wedel |
123 | Copyright (C) 2000, 2006 Mark Wedel |
147 | Copyright (C) 1992 Frank Tore Johansen |
124 | Copyright (C) 1992 Frank Tore Johansen |
148 | |
125 | |
149 | This program is free software; you can redistribute it and/or modify |
126 | 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 |
127 | 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 |
128 | the Free Software Foundation; either version 2 of the License, or |
… | |
… | |
158 | |
135 | |
159 | You should have received a copy of the GNU General Public License |
136 | You should have received a copy of the GNU General Public License |
160 | along with this program; if not, write to the Free Software |
137 | along with this program; if not, write to the Free Software |
161 | Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. |
138 | Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. |
162 | |
139 | |
163 | The author can be reached via e-mail to mwedel@scruz.net |
140 | The authors can be reached via e-mail to crossfire@schmorp.de |