Basic stuffs to do if you want to run a crossfire server
1) download crossfire source package from sourceforge and extract it somewhere
2) change to the source directory and do a ./configure --prefix=<dir to install to>
3) do a make && make install
4) put the maps in <dir to install to>/share/crossfire/maps/
5) go in a console, go to <dir to install to> and type ./bin/crossfire
6) you should get a a pack of messages from server initialisation and then something like 'waiting player connection' (unless you activated weather)
At this stage you should be able to connect to your local server with a crossfire client on same computer by typing 'localchost' (without the quotes) in the metaserver selection.
Can you confirm you reach this step?
How do I put my server up?
Moderator: Board moderators
- gumbyscout
- Luser
- Posts: 21
- Joined: Fri Feb 06, 2004 2:12 am
Damn
Compiled windows version of server still exist?
Perhaps the location of maps is different on windows but not a problem. If server don't find the map, you'll get a message like 'couldn't load original map <path to HallOfSelectionMap>' when first client tried to connect. Whatever your server problem is, you have to read what's out in console. If you've got too much mesages in console you may try to redirect to a file using the standard dos output redirection (crossfire.exe > logfile.txt).
If you can't connect to your server, but the server stay in 'waiting for user connection...' mode and dont move even a bit when a client tries to connect, this may be because of some windows firewall thingie
Perhaps the location of maps is different on windows but not a problem. If server don't find the map, you'll get a message like 'couldn't load original map <path to HallOfSelectionMap>' when first client tried to connect. Whatever your server problem is, you have to read what's out in console. If you've got too much mesages in console you may try to redirect to a file using the standard dos output redirection (crossfire.exe > logfile.txt).
If you can't connect to your server, but the server stay in 'waiting for user connection...' mode and dont move even a bit when a client tries to connect, this may be because of some windows firewall thingie
- gumbyscout
- Luser
- Posts: 21
- Joined: Fri Feb 06, 2004 2:12 am
mmm
run server with output redirection to a file an post the file in this forum, will be easier...