1 | WHAT IS CROSSFIRE? |
1 | WHAT IS CROSSFIRE? |
2 | |
2 | |
3 | This is a multiplayer graphical arcade and adventure game, that runs on a |
3 | This is a multiplayer graphical arcade and adventure game, that runs on |
4 | client/server model. There are clients for Microsoft(R) Windows(TM) and |
4 | a client/server model. There are clients for Microsoft(R) Windows(TM) |
5 | POSIX systems such as Linux and *BSD. To get the most joyful experience, |
5 | and POSIX systems such as Linux and *BSD. To get the most joyful |
6 | the Crossfire+ client should be used. This client is written in Perl and |
6 | experience, the Crossfire+ client should be used. This client is written |
7 | utilises SDL with OpenGL. |
7 | in Perl and utilises SDL with OpenGL to provide you with the most |
|
|
8 | immersive gameplay. |
8 | |
9 | |
9 | Crossfire has certain flavours from other games, especially Gauntlet (TM) |
10 | Crossfire has certain flavours from other games, especially Gauntlet (TM) |
10 | and Nethack/Moria. |
11 | and Nethack/Moria. |
11 | |
12 | |
12 | 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 |
13 | and using items and battle monsters. They can choose to cooperate |
14 | world, finding and using items and battle monsters. They can choose to |
14 | or compete in the same "world". |
15 | cooperate or compete in the same "world". |
|
|
16 | |
15 | |
17 | |
16 | REQUIREMENTS |
18 | REQUIREMENTS |
17 | |
19 | |
18 | For UNIX, a modern C++ compiler with some extensions is required to |
20 | For UNIX, a modern C++ compiler with some extensions is required to |
19 | compile this game. In addition, you will need the Perl development |
21 | compile this game. In addition, you will need the Perl development |
20 | libraries along with the following Perl modules (the server is tested |
22 | libraries along with the following Perl modules (the server is tested |
21 | with perl 5.8.8 and 5.8-maint). |
23 | with perl 5.8.8 and 5.8-maint). |
22 | |
24 | |
23 | - Crossfire >= v0.97 |
25 | - BDB >= v0.1 |
|
|
26 | - Compress::LZF >= v1.71 |
24 | - Coro >= v3.5 |
27 | - Coro >= v3.5 |
25 | - Coro::Event >= v2.1 |
28 | - Coro::Event >= v2.1 |
|
|
29 | - Crossfire >= v0.97 |
|
|
30 | - Digest::MD5 >= v2.0 |
26 | - Event >= v1.08 |
31 | - Event >= v1.08 |
27 | - IO::AIO >= 2.32 |
32 | - IO::AIO >= 2.32 |
28 | - BDB >= v0.1 |
33 | - JSON::XS => 1.11 |
|
|
34 | - Pod::POM >= v0.17 |
|
|
35 | - Safe::Hole >= v0.10 |
29 | - Storable >= v2.0 |
36 | - Storable >= v2.0 |
30 | - Time::HiRes >= v1.0 |
37 | - Time::HiRes >= v1.0 |
31 | - YAML::Syck >= v0.71 |
38 | - YAML::Syck >= v0.71 |
32 | - Digest::MD5 >= v2.0 |
|
|
33 | - Compress::LZF >= v1.71 |
|
|
34 | - Safe::Hole >= v0.10 |
|
|
35 | - Pod::POM >= v0.17 |
|
|
36 | |
39 | |
37 | Furthermore, you will need the following programs and libraries: |
40 | Furthermore, you will need the following programs and libraries: |
38 | |
41 | |
39 | - gperf, the GNU perfect hash generator |
42 | - gperf, the GNU perfect hash generator >= v3.0 |
40 | - glib-2.0 >= v2.10 |
43 | - glib-2.0 >= v2.10 |
41 | - libpng >= v1.2 |
44 | - libpng >= v1.2 |
42 | - ImageMagick >= 6.0 (convert must be in your PATH). |
45 | - ImageMagick >= v6.0 |
43 | - optipng (http://optipng.sf.net) |
46 | - optipng => v0.5.5 (http://optipng.sf.net) |
|
|
47 | - pngnq >= 0.4 (http://freshmeat.net/redir/pngnq/53146/url_homepage/pngnq.html) |
|
|
48 | - rsync >= 2.6 (a must have anyways) |
44 | |
49 | |
45 | Your compiler must support the Library Technical Report 1 extensions and |
50 | Your compiler must support the Library Technical Report 1 extensions and |
46 | the upcoming typeof extension. The GNU C++ compiler >= version 4.0 does |
51 | the upcoming typeof extension. The GNU C++ compiler >= version 4.0 does |
47 | support all these. |
52 | support all these. |
48 | |
53 | |
|
|
54 | On Debian GNU/Linux, you might get away with something like this for many of the |
|
|
55 | above dependencies: |
|
|
56 | |
|
|
57 | apt-get install gperf optipng pngnq rsync imagemagick libglib2.0-dev libpng12-dev |
|
|
58 | apt-get install libpod-pom-perl libsafe-hole-perl libevent-perl |
|
|
59 | |
|
|
60 | |
49 | COMPILING |
61 | COMPILING |
50 | |
62 | |
51 | Crossfire has been known to compile on a wide variety of systems. It should |
63 | Crossfire has been known to compile on a wide variety of systems. It should |
52 | compile and most all ISO C++ 200x and POSIX compliant systems. |
64 | compile and run on most ISO C++ 200x and POSIX compliant systems. |
53 | |
65 | |
54 | To get directions on compilation for UNIX/LINUX, read the INSTALL file. |
66 | To get generic directions on compilation, read the INSTALL file. |
55 | |
67 | |
56 | USAGE |
|
|
57 | |
68 | |
58 | Crossfire runs on a client/server model. You will also need the client |
69 | INSTALLATION/USAGE |
59 | to play. You can either connect to a server someone else has set up, |
|
|
60 | or run your own server and connect to that. The client package has |
|
|
61 | information for connecting to servers. |
|
|
62 | |
70 | |
63 | To run your own server, you need to make the crossfire binaries |
71 | Crossfire runs on a client/server model. You will also a client to |
64 | and install them, and then run the crossfire program. This now |
72 | play. You can either connect to a server someone else has set up, or |
65 | creates a server which you/other people can connect to. The map |
73 | run your own server and connect to that. There are a number of clients |
66 | files will need to get downloaded and installed for the server to run |
74 | available, but the recommended one is CFPlus (see below for URL). |
67 | properly. The map pack is released together with the server and can be |
|
|
68 | downloaded form the same location. The maps should be copied into the |
|
|
69 | $(TARGET)/share/crossfire/maps directory - after unpacking, you should |
|
|
70 | have a $(TARGET)/share/crossfire/maps/scorn directory. |
|
|
71 | |
75 | |
72 | If you plan to run a long term server, you should use one of the scripts |
76 | To run your own server, you need to make the crossfire binaries and |
73 | provided that will re-run crossfire if it dies for some reason. |
77 | install them, and then run the crossfire program. This now creates a |
|
|
78 | server which you/other people can connect to. First you have to download |
|
|
79 | and install maps and archetype packs, though. |
|
|
80 | |
|
|
81 | Download both the cfmaps-<version> and cfarch-<version> archives, then use cfutil |
|
|
82 | to install both: |
|
|
83 | |
|
|
84 | cfutil --install-maps path/to/cfmaps-<version>/ |
|
|
85 | cfutil --install-arch path/to/cfarch-<version>/ |
|
|
86 | |
|
|
87 | Both processes can take some time, depending on your resources :) |
|
|
88 | |
74 | |
89 | |
75 | WEB SITES: |
90 | WEB SITES: |
76 | |
91 | |
77 | The following web addresses have crossfire information that you may find |
92 | The following web addresses have crossfire information that you may find |
78 | useful: |
93 | useful: |
… | |
… | |
109 | helpful. |
124 | helpful. |
110 | |
125 | |
111 | The more information provided, the better chance of the bug being fixed in |
126 | The more information provided, the better chance of the bug being fixed in |
112 | a timely fashion. |
127 | a timely fashion. |
113 | |
128 | |
114 | ------------------------------------------------------------------------------ |
|
|
115 | SUBMITTING PATCHES: |
129 | SUBMITTING PATCHES: |
|
|
130 | |
116 | Patches should be submitted to email address: |
131 | Patches should be submitted to email address: |
117 | crossfire@schmorp.de |
132 | crossfire@schmorp.de |
118 | |
133 | |
119 | PUBLIC SERVERS: |
134 | PUBLIC SERVERS: |
120 | |
135 | |
121 | The best way to find a server to play is to run the client. It will contact |
136 | The best way to find a server to play is to run the client |
122 | the metaserver and present a list to choose from. You can also see |
137 | and hit "Server List" in the setup dialog (this varies |
|
|
138 | depending on your client). You can also see a list at |
123 | a list at http://crossfire.real-time.com/metaserver/ |
139 | http://crossfire.real-time.com/metaserver/. |
124 | |
140 | |
|
|
141 | The canonical server for use with Crossfire and CFPlus is |
|
|
142 | crossfire.schmorp.de, port 13327 (default). |
125 | |
143 | |
126 | COPYRIGHT |
144 | COPYRIGHT |
127 | |
145 | |
128 | Copyright (C) 2007 Crossfire Development Team |
146 | Copyright (C) 2007 Crossfire Development Team |
129 | Copyright (C) 2000, 2006 Mark Wedel |
147 | Copyright (C) 2000, 2006 Mark Wedel |