Connecting, running and compiling an FTE server

TEST SERVER

svn up // update

svn diff // show the differences

svn log -l30 // shows the 30 most recent commits

svn update -r 5300 // reverts to revision 5300

m-dbg DEBUG

m-rel release

$ make makelibs -j4 FTE_TARGET=win64 && make m-dbg -j4 FTE_TARGET=win64

more info here.

LINUX SERVER

#!/bin/sh

while true; do

# 2.5 omc: THIS is the command line which runs the server binary generated by:
# quake/fteqw-code/engine
# svn up
# make sv-rel
# the binary ends up in: release/fteqw-sv

./fteqw-code/engine/release/fteqw-sv +set worker_count 0 +gamedir fortress -port 26666 -mem 256 -nohome -condebug +developer 0 -nodumpstack
.
.

echo “Server died, restarting in 5 seconds…”
sleep 5
done

CONNECTING VIA PUTTY /SSH

  1. run puttygen
  2. make a new private public pair
  3. File filezilla, connect to the AGR server, and open/edit the ‘/.ssh/authorised_keys’ file
  4. Copy the public key contents, and paste them to the bottom of the /.ssh/authorised_keys file.
  5. save/upload to the AGR server
  6. save the private key to your comp, lets call it ‘mykey’
  7. in putty Connection-> SSH -> Auth -> ‘private key for authentication’ select mykey

PORT OPENING (so people can connect to your home computer)

  1. In cmd, type ‘ipconfig’, and get your ipv4 address, eg ‘192.168.1.2’
  2. In your router’s port forwarding, open port 27500 on ‘192.168.1.2’
  3. At the FTE server console, type ‘sv_port_tcp 27500’ so that ppl can connect via tcp? Or is that only so that port checker services (ie running on websites) can work?
  4. At the FTE server console, type ‘sv_port 27500/foo’ so fte players can connect only using ‘connect foo’

Leave a Reply

 

 

 

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>