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 |
4 | the X-Windows environment. It runs on a client/server model. |
4 | a client/server model. There are clients for Microsoft(R) Windows(TM) |
5 | The client runs with X11, GTK, or SDL within a gtk window. A |
5 | and POSIX systems such as Linux and *BSD. To get the most joyful |
6 | windows client is available, and a java client is under development. |
6 | experience, the Crossfire+ client should be used. This client is written |
|
|
7 | in Perl and utilises SDL with OpenGL to provide you with the most |
|
|
8 | immersive gameplay. |
7 | |
9 | |
8 | It has certain flavours from other games, especially Gauntlet (TM) |
10 | Crossfire has certain flavours from other games, especially Gauntlet (TM) |
9 | and Nethack/Moria. |
11 | and Nethack/Moria. |
10 | |
12 | |
11 | Any number of players can move around in their own window, finding |
13 | Any number of players can move around in their own window on the |
12 | and using items and battle monsters. They can choose to cooperate |
14 | world, finding and using items and battle monsters. They can choose to |
13 | or compete in the same "world". |
15 | cooperate or compete in the same "world". |
|
|
16 | |
14 | |
17 | |
15 | REQUIREMENTS |
18 | REQUIREMENTS |
16 | |
19 | |
17 | For UNIX, X-windows and an ANSI C compiler to compile this game. |
20 | For UNIX, a modern C++ compiler with some extensions is required to |
18 | A window system is not needed if you don't want to compile the |
21 | compile this game. In addition, you will need the Perl development |
19 | map editor. |
22 | libraries along with the following Perl modules (the server is tested |
|
|
23 | with perl 5.8.8 and 5.8-maint). |
20 | |
24 | |
21 | For Windows 9x, you need Visual C++ (or some other ANSI C |
25 | - BDB >= v0.1 |
22 | compiler that can read ".dsw"-files). |
26 | - Compress::LZF >= v1.71 |
23 | |
27 | - Coro >= v3.62 **SEE IMPORTANT NOTICE BELOW** |
|
|
28 | - Coro::Event >= v2.1 |
|
|
29 | - Crossfire >= v0.97 |
|
|
30 | - Digest::MD5 >= v2.0 |
|
|
31 | - Event >= v1.08 |
|
|
32 | - IO::AIO >= 2.32 |
|
|
33 | - JSON::XS => 1.11 |
|
|
34 | - Pod::POM >= v0.17 |
|
|
35 | - Safe::Hole >= v0.10 |
|
|
36 | - Storable >= v2.0 |
|
|
37 | - Time::HiRes >= v1.0 |
|
|
38 | - YAML::Syck >= v0.71 |
|
|
39 | |
|
|
40 | **NOTICE**: Crossfire uses an alternative signal stack, so you have to |
|
|
41 | use either the "u"context method or "a"ssembly when configuring Coro. |
|
|
42 | |
|
|
43 | Furthermore, you will need the following programs and libraries: |
|
|
44 | |
|
|
45 | - gperf, the GNU perfect hash generator >= v3.0 |
|
|
46 | - glib-2.0 >= v2.10 |
|
|
47 | - libpng >= v1.2 |
|
|
48 | - ImageMagick >= v6.0 |
|
|
49 | - optipng => v0.5.5 (http://optipng.sf.net) |
|
|
50 | - pngnq >= 0.4 (http://freshmeat.net/redir/pngnq/53146/url_homepage/pngnq.html) |
|
|
51 | - rsync >= 2.6 (a must have anyways) |
|
|
52 | |
|
|
53 | Your compiler must support the Library Technical Report 1 extensions and |
|
|
54 | the upcoming typeof extension. The GNU C++ compiler >= version 4.0 does |
|
|
55 | support all these. |
|
|
56 | |
|
|
57 | On Debian GNU/Linux, you might get away with something like this for many of the |
|
|
58 | above dependencies: |
|
|
59 | |
|
|
60 | apt-get install gperf optipng pngnq rsync imagemagick libglib2.0-dev libpng12-dev |
|
|
61 | apt-get install libpod-pom-perl libsafe-hole-perl libevent-perl |
|
|
62 | |
|
|
63 | |
24 | COMPILING |
64 | COMPILING |
25 | |
65 | |
26 | Crossfire has been known to compile on a wide variety of |
66 | Crossfire has been known to compile on a wide variety of systems. It should |
27 | systems. It should compile and most all ANSI C and Posix |
67 | compile and run on most ISO C++ 200x and POSIX compliant systems. |
28 | compliant systems. |
|
|
29 | |
68 | |
30 | To get directions on compilation for UNIX/LINUX, read the INSTALL file. |
69 | To get generic directions on compilation, 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 | 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 | |
|
|
50 | MAILING LIST |
|
|
51 | |
|
|
52 | For the latest subscription for crossfire mailing lists, go to: |
|
|
53 | http://crossfire.real-time.com/mailinglists/index.html |
|
|
54 | |
|
|
55 | From there you should be able to subscribe/unsubscribe any of the mailing |
|
|
56 | 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 | |
70 | |
60 | |
71 | |
61 | FTP SITES |
72 | INSTALLATION/USAGE |
62 | |
73 | |
63 | FTP-sites where you can look for the latest versions are: |
74 | Crossfire runs on a client/server model. You will also a client to |
|
|
75 | play. You can either connect to a server someone else has set up, or |
|
|
76 | run your own server and connect to that. There are a number of clients |
|
|
77 | available, but the recommended one is CFPlus (see below for URL). |
64 | |
78 | |
65 | http://prdownloads.sourceforge.net/crossfire/ |
79 | To run your own server, you need to make the crossfire binaries and |
66 | ftp://ftp.real-time.com/pub/games/crossfire |
80 | install them, and then run the crossfire program. This now creates a |
|
|
81 | server which you/other people can connect to. First you have to download |
|
|
82 | and install maps and archetype packs, though. |
67 | |
83 | |
68 | Changes made since the latest release can be found at the CVS |
84 | Download both the cfmaps-<version> and cfarch-<version> archives, then use cfutil |
69 | repository. Information on anonymous CVS access as |
85 | to install both: |
70 | the download CVS snapshots and browsing the repository can be |
86 | |
71 | found at: |
87 | cfutil --install-maps path/to/cfmaps-<version>/ |
72 | http://sourceforge.net/cvs/?group_id=13833 |
88 | cfutil --install-arch path/to/cfarch-<version>/ |
|
|
89 | |
|
|
90 | Both processes can take some time, depending on your resources :) |
73 | |
91 | |
74 | |
92 | |
75 | WEB SITES: |
93 | WEB SITES: |
76 | |
94 | |
77 | The following web addresses have crossfire information that you may find |
95 | The following web addresses have crossfire information that you may find |
78 | useful: |
96 | useful: |
79 | |
97 | |
80 | http://crossfire.real-time.com/ |
98 | http://crossfire.schmorp.de/ (The main site) |
81 | real-time is the main crossfire site. |
99 | |
|
|
100 | http://crossfire.real-time.com/ (The website for the old Crossfire game) |
82 | |
101 | |
83 | |
102 | |
84 | REPORTING BUGS |
103 | REPORTING BUGS |
85 | |
104 | |
86 | First, check the INSTALL file for common problems, and see if yours is |
105 | First, check the INSTALL file for common problems, and see if yours is |
87 | mentioned. |
106 | mentioned. |
88 | |
107 | |
89 | Bugs should be filed at the sourceforge web site: |
108 | Bugs should be filed using the following email address: |
90 | http://sourceforge.net/cvs/?group_id=13833 |
109 | crossfire@schmorp.de |
91 | |
110 | |
92 | When reporting bugs, make sure you include the following: |
111 | When reporting bugs, make sure you include the following: |
93 | 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 | o What version of crossfire did you use? |
112 | o What version of crossfire did you use? |
97 | o What type of computer did you use (CPU type) |
113 | o What type of computer did you use (CPU type) |
98 | o What is the version of the OS? |
114 | o What is the version of the OS? |
99 | o What windowing system are you using (Ie, openwindows, X11R6, etc) |
115 | o What windowing system are you using (e.g. openwindows, X.org, XFree86) |
100 | o What compiler (and its version) did you use (ie, gcc, acc, etc)? |
116 | o What compiler (and its version) did you use (e.g. gcc, acc)? |
101 | o Which flags did you give it? |
117 | o Which flags did you give it? |
102 | o If the bug happens when compiling crossfire, send an EXACT copy of |
118 | o If the bug happens when compiling crossfire, send an EXACT copy of the |
103 | the compiler line, as well as the errors it puts out. Sending bugs |
119 | compiler line, as well as the errors it puts out. Sending bugs of the |
104 | of the sort 'it failed with a line like ...' doesn't help any. |
120 | sort 'it failed with a line like ...' doesn't help any. |
105 | o If the bug happened while running crossfire: |
121 | o If the bug happened while running crossfire: |
106 | - Include any output before to the bug. |
122 | - Include any output before to the bug. |
107 | - Give a description of what you did before the bug occured. The better |
123 | - Give a description of what you did before the bug occured. The better |
108 | detailed the description, the better chance I have of figuring |
124 | detailed the description, the better chance I have of figuring |
109 | out where the bug happened, or how I can recreate the bug. |
125 | out where the bug happened, or how I can recreate the bug. |
110 | - If possible, a stack trace from gdb (or other debugger) is very |
126 | - If possible, a stack trace from gdb (or other debugger) is very |
111 | helpful. |
127 | helpful. |
112 | |
128 | |
113 | The more information provided, the better chance of the bug being fixed in |
129 | The more information provided, the better chance of the bug being fixed in |
114 | a timely fashion. |
130 | a timely fashion. |
115 | |
131 | |
116 | Further debugging informatiion can be found at |
132 | SUBMITTING PATCHES: |
117 | http://crossfire.real-time.com/debugging_tips.html |
|
|
118 | |
133 | |
119 | ------------------------------------------------------------------------------ |
134 | Patches should be submitted to email address: |
120 | SUBMITTING PATCHES: See the doc/programming_guide file. |
135 | crossfire@schmorp.de |
121 | The patches should be submitted to the patch tracker on sourceforge: |
|
|
122 | http://sourceforge.net/cvs/?group_id=13833 |
|
|
123 | |
136 | |
124 | PUBLIC SERVERS: |
137 | PUBLIC SERVERS: |
125 | |
138 | |
126 | The best way to find a server to play is to run the client. It will contact |
139 | The best way to find a server to play is to run the client |
127 | the metaserver and present a list to choose from. You can also see |
140 | and hit "Server List" in the setup dialog (this varies |
|
|
141 | depending on your client). You can also see a list at |
128 | a list at http://crossfire.real-time.com/metaserver/ |
142 | http://crossfire.real-time.com/metaserver/. |
129 | |
143 | |
|
|
144 | The canonical server for use with Crossfire and CFPlus is |
|
|
145 | crossfire.schmorp.de, port 13327 (default). |
130 | |
146 | |
131 | COPYRIGHT |
147 | COPYRIGHT |
132 | |
148 | |
133 | Don't get scared by the below, it's included just for "safety" reasons 8) |
149 | Copyright (C) 2007 Crossfire Development Team |
134 | (Don't want anyone to start selling the game) |
|
|
135 | |
|
|
136 | Copyright (C) 2000,2006 Mark Wedel |
150 | Copyright (C) 2000, 2006 Mark Wedel |
137 | Copyright (C) 1992 Frank Tore Johansen |
151 | Copyright (C) 1992 Frank Tore Johansen |
138 | |
152 | |
139 | This program is free software; you can redistribute it and/or modify |
153 | 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 |
154 | 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 |
155 | the Free Software Foundation; either version 2 of the License, or |
… | |
… | |
148 | |
162 | |
149 | You should have received a copy of the GNU General Public License |
163 | You should have received a copy of the GNU General Public License |
150 | along with this program; if not, write to the Free Software |
164 | along with this program; if not, write to the Free Software |
151 | Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. |
165 | Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. |
152 | |
166 | |
153 | The author can be reached via e-mail to crossfire.de |
167 | The authors can be reached via e-mail to crossfire@schmorp.de |