Above a lot is written about maps and their selection for servers. Here is a bit more about how to create a game server. Since the solo match (single player) is only a special case of the multi match (multiplayer), there are no separate explanations on that. For a LAN server there are basically two alternatives: Either you open a so-called “dedicated server”, or you open a so-called “list server”. There are again two methods for the fromer: Either you use an extra program for it (which usually has better configuration possibilities for dedicated servers), or you use EF itself for it. Since there are many programs for it, I will only explain how to do this with EF itself. After all, everyone has that. But if one of you still wants to use a program for it, I can recommend the EF-Runner. But I won't explain it here additionally. It then creates the necessary config files, if necessary for several servers.

1. The menu path is as follows: Multi Match → Create Server

So from this menu:

You end up here:

1. Select game type:
   • Free for all (FFA = DM)
   • Team Holomatch (TDM)
   • Tournament (1 on 1) (not necessarily available on the GUI)
   • Capture the Flag (CTF)
2. Select a map (this is the first one, i.e. the one that will be played directly at the beginning, and is played over and over until someone successfully calls for a vote for another map)
3. Select modes if necessary (Elimination, Specialist, Action Hero, Disintegration, Assimilation). Not all combinations of mode and game type are possible. For example, assimilation requires team deathmatch as game type.
4. Click on Continue. You will enter this menu:

1. Enter the Host name: The others will see this name in the list when searching for servers.
2. In the field Human below Players you may change your own name if you haven't done so yet. (This does not exist, of course, if you start the server as Dedicated Server.)
3. Select how many open slots or how many slots occupied by bots should be available.
4. HC skill: Level of difficulty of the bots, where Cadet is the easiest ranging to Captain being the most difficult level.
5. Set Point Limit and Time limit
6. Define Server: The Pure Server option is not the dedicated function, but a security function that does the following: If it is on, the server checks whether the client (= player) really has exactly the same files as on the server (sv_pure = 1). This means, for example, that a player cannot cheat with modified *.pk3 files. But normally you don't need it on LANs. But that's sometimes the reason why you shouldn't change the original *.pk3 files, or recompress them again, or something like that. The file may not be usable afterwards…
7. Under Dedicated Server you have three options:
   • NO (= No dedicated server, so = list server)
   • LAN (only players from the local network may join the server)
   • INTERNET (People from the Internet may also join, not recommended on LANs)
8. Set Advanced settings if necessary:

• Auto join team: Does the server put a connecting player into a team automatically?
• Auto balance: Does the server rebalance the teams, if a team has more players than the other?
• Falling Damage: Will a player suffer damage, when falling off from a heightened position?
• Weapon respawn: Number of seconds after picked up weapons will reappear on their pick up spot.
• Max clients: The maximum number of players that are allowed to connect to the server at the same time.
• Run speed: How fast players can walk.
• Knockback: How powerful are pushing effects like explosions?
• Damage mulitplier: You can increase the damage dealt by any weapon with this factor.
• Minimum players: If there are not enough human players per team, the server automatically fills it wit bots until the number of players has been reached. In teamless modes, the number counts for all players on that server.
• Class change timeout: Number of seconds a player has to wait, until he can change his class in specialties mode. This also counts from the first joining of he match, where you automatically have class assigned.
• Adjust item respawn:
• Holodeck intro: A small intro, that is played just before actually entering the match.
• Force player respawn: Players cannot stay in score screen suspension after being fragged indefiniteley, when turned on.
• Respawn invulnerability: The number of seconds during which a fragged and rejoined player cannot be hit.
• Warmup: Number of seconds a warm up period is applied before the actual match begins.
• Blue team group: Selection of what kind models will be used for blue team's bots. Possible values:
  • None,
  • Female,
  • Proton,
  • Male,
  • Starfleet,
  • Borg,
  • BorgFemale,
  • BorgMale,
  • Aliens,
  • HazardTeam,
  • Klingons and
  • Romulans.
• Red team group: Same as for Blue.
• Specialties: Do players have special classes like sniper or infiltrator?
• Desintegration: One hit instantly kills.
• Eliminiation: Fragged players stay out of the match until another round starts.
• Action Hero: One player get's all weapons of the game and starting ammunition, has a maximum or 300 health, constantly replenished. Fragging the hero makes a player the hero himself and getting 5 points. Normal frags give 1 point.

To use a dedicated server on your own computer and play on it parallel, you would have to start another instance of Elite Force to connect to the server. However, since this requires a fast computer, so that it doesn't cause any problems, it is recommended to use a computer that has the service running, or if none at hand, to start a list server. And the dedicated server created in EF has another limitation: You can only run one map at a time (or use voting), unless you know a bit about scripting (but that goes too far here). Programs like the EF-Runner can also create a mapcycle without any problems and this very comfortable.

There are basically two ways to automatically start servers without having to click through menus. One runs via a start script, i.e. under Windows a *.bat file, under Linux a shell script or a Systemd Unit. Or you simply start the server and provide the config file via the exec command. Both cases use a server configuration file, which tells the server what it has to look like and what it has to do. By default, the EF server will not run any map or match. You can enter map your map name in the console that will appear after starting the server or start a config manually with exec your config file. But for dedicated servers this is not recommended. Before you have a map running, the server is not accessible from the outside, so not even rcon access is possible. So for testing purposes this may work, but not for stand alone use or even automated starting with the system.

The basis for all this is the dedicated server, which nowadays will be mostly custom software. Under Windows it's pretty easy: Just use a normal EF installation but expanded with an up-to-date version for the dedicated server binaries, see Versions on the matter. If you want to set up a bare server, you don't need all of your EF installation files. You only need the directory BaseEF from the CD, which you have to rename to baseEF under Linux. Otherwise the server won't find its files. In addition, there is the stvoyHM.exe, or better (because more secure), a corresponding dedicated server binary, which is not to be placed in baseEF, but one level higher. Examples would be liliumvoyded.x86_64 (Lilium Voyager x64 under Linux) or cmod_dedicated.x86.exe (cMod x86 under Windows). In order to run the dedicated server under Linux, you might need to make the dedicated server binary executable, before you can run it.

So for example Lilium Voyager under Linux would require a file and a folder to be suitable as an EF dedicated server, e.g.:

• baseEF and
• liliumvoyhm.x86_64.

For Windows the binary would be named liliumvoyded.x86_64.exe. Inside the folder baseEF you should find at least the following files:

• pak0.pk3
• pak1.pk3
• pak2.pk3
• pak3.pk3

You may also extend that folder with your own maps, models, and so on. Just be aware: A player will download those files, if needed, unless either the server or the client forbids it. So if you add custom content, make sure a player has some convenient means to get those contents (e.g. map downloads on or a map package of sorts).

So the final folder structure should look somewhat like this:

• ef_server/liliumvoyhm.x86_64
• ef_server/baseEF/pak0.pk3
• ef_server/baseEF/pak1.pk3
• ef_server/baseEF/pak2.pk3
• ef_server/baseEF/pak3.pk3

For the server to do something customized to your needs, you will have to create a new text file with .cfg extension in the baseEF folder. In principle, the name for the config doesn't matter. However, when named autoexec.cfg the config is loaded automatically during start-up and map running. This special config file is used always. It might contain default definitions (e.g. having the same rcon password for all servers or turning off bot chat).

A minimal server config could look like this:

// Lines with double slashes are used for comments and to keep commands from running, just like this one here.

//This sets the name of the server. When players browse the server list, this is what they will read:
seta sv_hostname "My Server"
//This sets the maximum players, that can play on that server. This includes bots, but depending on settings, a bot will be kicked whenever a new player joins the server:
seta sv_maxclients "32"
//If playing (team) deathmatch, maps will continue either until this frag limit has been reached by a team or player or...
seta fraglimit "30"
// until this time limit (in minutes) was reached. This is the longest time a match goes on the current map. This time limit also goes for CTF matches. But those might end before the time limit has been reached, depending on...
seta timelimit "15"
// this value. CTF maps will go until this limit of captures (flag brought home) has been reached by either team:
seta capturelimit "5"
// This controls whether hitting players of one's own team deals any damage to them:
seta g_friendlyfire "1"
// This sets the starting map:
map hm_voy1
// This is displayed immediately after the first match has started:
echo "Runs!"
// This displays the player data, e.g. num, score, ping, name, address, port, rate, right after the map starts: 
status

Note the seta commands: These set server variables. More details you can find here. They come in different flavors, but essentially you need them to describe to the game how your server is supposed to look and behave like.

Also be aware that these commands are run in the order as they are written in the configuration file. If you happen to have a specific setting in there twice, the latest occurrence of it will be effective. Also some of them are relevant in terms of what has to come first. E.g. the map command makes a number of settings effective. Without it the match will not abide by all settings made later on in the config. Also the server will not even be accessibly without a map command issued.

For a list of available stock game maps, see article Maps.

An example: Setting game types with g_gametype should come before running a map. E.g. you can very well start a CTF match on a non-CTF-map. The server will do that, but the map goal can of course not be reached this way for a lack of flags on the map. So setting the g_gametype to 4 before issuing the map command to a CTF map is important. First issuing the map command and then setting the g_gametype would end you up in whatever game type was set before taking place on the map (default is 0).

An extended config utilizing a map cycle could look like this:

(click to expand)

seta sv_hostname  "your server name"
// Displayed whenever a player enters the server:
seta g_motd "your message of the day"
// Some custom variables. It does nothing but is included in the server info. So a player can look up this information:
sets Administrator "your name here"
sets clan "your clan here"
sets ClanWebsite "your web site here"
sets Email "your Email here"
sets location "where you are"
sets CPU "your PC description here"
sets OP "your operating system here"
sets RAM "your Amount of ram here"
sets Connection "your connection here"

//Default Capture The Flag Server Configuration File
//These settings need to be set as they are.

//You can lower the maxrate, but 8000 is our ceiling
// Turns off bots:
set bot_enable 0
// Activates a rudimentary flooding protection for the server:
set sv_floodprotect 1
// Sets the game type to CTF:
set g_gametype 4
// Limits players to this maximum rate (can make it fairer):
set sv_maxRate 8000
// Sets the server to allow 12 players, tops.
set sv_maxclients 12

// Set to 1 to enable expansion mod type, but mind the dependencies on certain game types:
set g_pMODElimination 0
set g_pMODActionHero 0
set g_pMODDisintegration 0
set g_pMODAssimiliation 0
set g_pMODSpecialties 0

//These are recommended settings, but your mileage may vary:
// Turns of the holodeck intro, that by default is played before a player eventually can take part in the action:
set g_holoIntro 0
// Allows map downloads from the server to the player/client:
set sv_allowdownload 1
// Should there be a warm-up-phase, where any player actions have no consequences for the eventual match results?
set g_doWarmup 0
// Should the client only have *exactly* the same files as the server?
set sv_pure 1
// 10 flag captures and the match is over.
set capturelimit 10
// After 15 kills a death match is over.
set fraglimit 15
// No match will last longer than 30 minutes.
set timelimit 30
// Friendly fire will do no damage.
set g_friendlyFire 0
// You could use this to reserve a number of slots for special players providing the proper private slot password. It prevents e.g. admins from being blocked from joining their own servers for it being full. Reserved slots are never occupied by anyone that has not provided the password for them. If you set this to 0, it means all slots are private, unless not password is set.
set sv_privateClients 0
// And this would set the password they need to be allowed to occupy reserved player slots:
set sv_privatePassword ""
// If set to 1, it might impact server performance negatively, but allows for demos to be recorded by players:
set g_synchronousClients 0

// The EF master servers are set by those. Make sure you include the ravensoft master. It comes pre-configured in a stock EF installation. So even totally new players should see your server, if you announce it to the master servers.
set sv_master1 "efmaster.tjps.eu"
set sv_master2 "master.stvef.org"
set sv_master3 "master.stef1.ravensoft.com:27953"
// Set this to 2 if you want the server to appear on master servers. 1 makes it a dedicated server but not announced to a master server:
seta dedicated 1

//Set map selection, cycle order, and start first map:
set d1 "map hm_borg1 ; set nextmap vstr d2"
set d2 "map hm_borg2 ; set nextmap vstr d3"
set d3 "map hm_borg3 ; set nextmap vstr d4"
set d4 "map hm_kln1 ; set nextmap vstr d5"
set d5 "map hm_scav1 ; set nextmap vstr d6"
set d6 "map hm_dn1 ; set nextmap vstr d7"
set d7 "map hm_dn2 ; set nextmap vstr d8"
set d8 "map hm_for1 ; set nextmap vstr d9"
set d9 "map hm_noon ; set nextmap vstr d10"
set d10 "map hm_cam ; set nextmap vstr d11"
set d11 "map hm_voy1 ; set nextmap vstr d12"
set d12 "map hm_voy2 ; set nextmap vstr d13"
set d13 "map ctf_kln1 ; set nextmap vstr d14"
set d14 "map ctf_kln2 ; set nextmap vstr d15"
set d15 "map ctf_and1 ; set nextmap vstr d16"
set d16 "map ctf_voy1 ; set nextmap vstr d17"
set d17 "map ctf_voy2 ; set nextmap vstr d1"

// Starts the map cycle configured above:
vstr d1


//Misc Settings
// How long does it take for a weapon to respawn after it was picked up (in seconds)?
set g_weaponrespawn 0
// Adjust item respawn times based on player count
set g_adaptrespawn 1
// Do not allow for voting (e.g. new maps).
set g_allowvote 0
// Minimum duration waiting time in seconds between matches. Player cannot issue commands during that time.
set g_intermissionTime 20
// Spawn protection duration in seconds:
//set g_ghostRespawn 3
// Bot character selection for the red team:
//set g_team_group_red hazardteam
// Bot character selection for the blue team:
//set g_team_group_blue borg
// Password needed to enter the server. If empty, no password will be asked from the user.
seta g_password ""
// Password needed for accessing the server via remote console (rcon). Left empty, therefore no rcon access:
seta rconpassword ""
// Sets the maximum number of players being able to join the match (not the server). Rest will be forced to watch:
seta g_maxgameclients 12
// Maximum ping allowed for a player to be able to join. If 0, it is inactive.
seta sv_maxping 0
// Minimum ping allowed for a player to be able to join. If 0, it is inactive.
seta sv_minping 0
// Forces the player to respawn after the set time (in seconds):
seta g_forcerespawn 5
// Kicks players if they do not move for 2 minutes:
seta g_inactivity 120
// Makes the server automatically force balanced teams in terms of player count.
seta g_TeamForceBalance 1
// Automatically puts a new player in the team with the lower score, if 1:
seta g_TeamAutoJoin 0

There are many other cvars, that can control your server. You can find a number of them in article Cvars.

For a mapcycle, as shown in the second example, you have to define manually which map should be loaded after the current one (nextmap command) and add restarting the cycle at the end. You can also set the mode for the current map and other settings that should change when changing maps. This way you can switch between CTF and DM, game modes and maximum bot settings, depending on the map. There is one drawback of this method: You really should turn off the voting system. Otherwise, some player may make the server “take another turn”, essentially leaving the map cycle. You can continue it, by issuing /rcon vstr name, to continue with the section named name. But especially on dedicated servers running 24/7, the more elegant way is to turn of voting altogether.

But speaking of which: If you actually intend to run a dedicated server 24/7, know, that map cycles will be broken after 23 days of uninterruptedly running a server. This is the time it takes for the numSnapshotEntities variable to overflow. If this strikes, you will find a message like this one in your logs:

Server Shutdown (Restarting server due to numSnapshotEntities wrapping)

You cannot avoid this, as it is an engine limitation. After 23 days the server restarts, issuing a map command to the last played map, basically breaking your map cycle. So either restart your server with system means before that, or do not use map cycles to begin with. Otherwise you end up in a situation similar to someone voting a map.

Important: If you use command such as vstr or map, or in general, all commands other than set derivatives, you must write protect your config. EF will overwrite the config after using it, stripping it of any of these commands. So you would end up with pure, uncommented settings, possibly even destroying your work.

Bots are a matter for debate. Some think they are unnecessary. Others say, if the options are being alone on the server or having at least a bot to play against, they want a bot to be there. One thing is for sure: Just with the game you cannot tell the difference between actual players and bot players when browsing open game servers. Both count as players in the eyes of the game server, whenever it comes to the question of whether it is empty, full or how many players are on it. (It is possible to find out about that detail anyway by looking at the ping of players on a server. Bots will always have a ping of 0 while LAN or internet players do not. However, if the game server is not a dedicated server, the hosting player will also have a ping of 0.) Fetting that information requires additional querying, which the in-game server browser does not do.) Bots can be added in two ways:

• Adding bots explicitly with the addbot command: Each bot is named and added, one by one, exactly as specified by its technical name. The name definition here is not case-sensitive.
• Setting bot_minplayers: The server is filled with bots. The number set is the amount of minimum players per team. If a team has less players then specified, a the slots will be filled up with players until the team has enough players. If a human joins the team, then a bot of the team will be kicked from the server. Note: Team is to be understood also as all players during death match. It is kind of like there is only one team. So the cvar can mean either this player count over all on the server (dm) or twice the player count (team modes).

All of these require bot_enable to be set to 1. Otherwise the server will not allow for bots to be used. Also do not make the mistake of setting bot_minplayers higher than the allowed number of players on the server. It will constantly try and add a new bot, just to end up with an error message that the bot could not be added for the server being full.

Examples:

set g_gametype 4
set bot_minplayers 3
map ctf_voy1

Effect: Plays the map ctf_voy1 in CTF mode, filling each team up to 3 players with bots, meaning minimum player count will always be 6 (at least 3 per team).

set g_gametype 0
set bot_minplayers 3
map hm_borg1

Effect: Plays the map hm_borg1 in FFA mode, filling the server up to 3 players with bots. So the minimum number of players will always be 3.

set g_gametype 3
set g_pModAssimilation 1
set bot_minplayers 0
map hm_borg3
addbot arjofa 3 borg
addbot biessman 3 borg
addbot gamma 3 borg
addbot tlar 3 borg
addbot kim 3 starfleet
addbot paladin 3 starfleet
addbot takorr 3 starfleet
addbot wortsla 3 starfleet

Effect: Starts up an Assimilation mode server on map hm_borg3, adding four bots of medium difficulty to each team, Borg and Starfleet. Note the bot_minplayers variable being set to 0 here. If you want to control explicitly which bot is to be added to which team, having the bot filling automatism active as well makes little sense, as it would interfere with the outcome.

For a list of available stock game bots, see Bots.

If you want to get rid of all currently added bots, issue the kickbots command. This can be relevant when using bots in map cycles. Theoretically it would also be possible to use clientkick or kick. However, for both you would need reliable information about the bot's player ID. As this may depend on the situation, it is not really reliable. You might end up kicking an actual player instead. So the most sensible way of getting a specific set of bots on the server is kickbots.

Important: Especially in Assimilation mode beware of the Assimilation Mode Full Server Bug! You might make your server unusable, if you do not properly add bots for that game mode.

Optimal settings for a given internet connection and server can be a matter of religious convictions for some. The truth is: When it comes to these settings, it's always something that should be tailored to your situation. Some values work better for others and worse for the rest. Here are some values, that can be considered as a starting point:

// Maximum rate player can use on this server is 25 kB/sek:
set sv_maxRate "25000"
// Some flood protection:
set sv_floodProtect "1"
// Players should be able to download maps from the server, of they do not have them:
sv_allowDownload "1"
// The HTTP or FTP address used to download maps from:
sv_dlURL "<your http url>"
// Only for servers based on ioQuake3 (which you should use instead of vanilla EF!), we want IPv6 *and* IPv4:
set net_enabled 7

Effect: You can download missing maps from the server via HTTP or FTP (if the client supports it). The players are limited to a maximum data rate of 25 kb/sek. and flood protection is turned on. Also the server is reachable via IPv6 and IPv4.

On the matter of map downloads, see also Map Downloads.

Config files have to be stored in folder baseEF, even if you want to start the dedicated with active mods. The server initially searches for its files there, including the maps, before it starts. Under Linux some dedicated servers search in the folder ~/.stvef/baseEF resp. ~/.local/share/lilium-voyager/baseEF. So it may also depend on the user you run the server as, where it will actually be searching for its files.

When done, you should end up with a file like this:

• ef_server/baseEF/my_super_duper_config.cfg

Or maybe like this:

• /home/your_user_name/.local/share/lilium-voyager/baseEF/my_super_duper_config.cfg

For further settings in the config, see the Config Parameters.

In essence, once you have created your installation and a configuration file, you need the EF dedicated server to run and loading it.

In order to actually use a specific config, you have to state that to the dedicated server binary of EF during running it (or starting it manually, once the server already runs).

The manual specification of a config file to load during start-up can look like this:

"C:\Program Files\Raven\Star Trek Voyager Elite Force\stvoyHM.exe" +seta dedicated 2 +seta sv_pure 0 +exec my_config.cfg

This command can either be put into a Windows shortcut as a start command (the path in which the program is to be executed must be adapted accordingly), or into the starting batch file. There is not much more to do with an EF installation under Windows. For Linux, the case looks like this:

./binaryname +seta dedicated 2 +seta sv_pure 0 +exec my_config.cfg

Run from the directory where the EF server is located. You can of course use the full path of the binary as well.

+seta dedicated 2 makes the server appear on master servers, if your port-forwarding allows for remote access (see section Accessibility on more details). The +seta sv_pure 0 turns of the pure setting. You can also turn that on, with 1 instead of 0. +exec my_config.cfg makes the dedicated server do the actual config loading. There are a number of other parameters you might want to use, but these are probably the most important ones for basic server operations.

If you don't want to start a dedicated server with standard EF but with a mod active, you have to pass this to the server at start-up, e.g. for Pinball by adding +set fs_game pinball. For the use of mods the specification fs_game might be absolutely necessary as start start parameter (not to be set in the config, that's too late to be found). The name of the mod normally corresponds with the name of directory in which the mod data is stored. This will also be the location where the game will be looking for its config files. You could say that for standard EF the mod folder is baseEF. But it doesn't have to be specified separately, because the data is searched for in this directory by default.

A Game Type is kind of the base variation of the game (e.g. team play vs. each player on their own), while a Mode varies a Game Type (e.g. with special classes or one player having a special role).

Here is a brief overview of which game types and which modes belong to which config variables:

If other numbers are used, the game mode is set to FFA.

* Note: Solo is only here for the sake of completeness and is not actually a game type for servers. This mode is set when starting a solo match via GUI in Elite Force, i.e. without other human players. In principle this mode can also be used via console parameters or in a config, but then it is not possible for other players to join the game. Accordingly, it cannot be reached via network (not even via stating localhost / 127.0.0.1).

Not all combinations of game type and mode are allowed. Below is an overview of which combinations of modes are allowed with game types and with modes among each other.

Beware of a glitch that comes around when using bot_minplayers > 0 in conjunction with g_pModAssimilation = 1. When certain game event orders occur, the server gets filled up with bots, up to the point where nobody can join it any longer (not even reserved slots are free). To understand this, keep the following things in mind:

1. bot_minplayers adds a new bot, whenever one team is dropping below the number of players defined by it.
2. In Assimilation mode after a short while you cannot join either team any longer but are forced to spectate (= being part of no team, or the pseudo-team spectator).
3. Whenever Borg assimilate a player from the Starfleet team, the player gets re-assigned to the Borg team, leaving the Starfleet team one player shorter than before. (And the Borg team one player bigger.)

So for the Assimilation mode a team falling below the value of bot_minplayers is normal operations for the Starfleet team. This also means, unless bot_minplayers is set to zero or the Borg queen gets killed before that happens, the Starfleet team will drop below the bot_minplayers value at some point. What happens then is, the game will – as usual – try to add a new bot to the Starfleet team, to compensate the lack of players.

This however will fail, if the timeout for joining a team has already hit. In turn, the new bot will be re-assigned to the spectator-non-team – leaving the Starfleet team one player short, still. So the game will again add another player to team Starfleet, starting the circle anew. This goes on until the server is stacked full with players and/or bots. The bad thing about this is, this also uses up reserved slots, making it impossible for anybody to join the server, as it will be full after this cycle of death hit.

Here is a video showing that phenomenon: https://www.youtube.com/watch?v=No1yFRQb-04

In order to get around this problem, whenever playing Assimilation, make sure to set bot_minplayers to 0. This of course means, by default, no bots will populate the server. This however, can be achieved manually with help of the following commands:

• addbot <name> <level> <team>: Adds a bot of given level to the given team. The name is mandatory. The other values are optional. <team> should be either borg or starfleet. You could also use the regular blue and red values. But then the assignment of the bots to Borg or Starfleet team may be random, as the Borg teams may be chosen to be red or blue, and Starfleet the according opposite. <level> should be between 1 and 5. The default is 3.
• kickbots: This kicks all bots from the server. This is particularly useful, when you work from within a mapcycle, that used bot_minplayers before, so the server is already filled with bots. First kick all bots, then re-add the ones you want to have.

Example:

set bot_minplayers = 0; kickbots; addbot 2_of_3 3 borg; addbot wortsla 3 starfleet;

This fills the server with one player for each team.

When creating an EF 1 game server yourself you only need to open port 27960 (UDP) in a firewall (or alternatively the port you have chosen yourself). You don't have to select a specific port to join, just as long as NAT forwarding and/or firewall allow for it to be used. However, you have to distinguish between LAN server and Internet server when creating the server. LAN servers are, as the term implies, only accessible via LAN, not via the Internet. In principle you can also run multiple servers by using different ports for the different servers. Some ports can be found automatically by EF, so that even a second or third game server running in parallel does not have to be entered manually in EF. The automatically scanned UDP ports for LAN search are 27960-27963.

If you are hosting a match on a computer with an IPv6 address, the game also waits for connections via your IPv6 stack, when using Lilium Voyager or cmod. If a player decides to connect to that server via IPv6, he has to enter the address in the fashion [block1:block2:…:blockn] into the Specify Server fields. Notice the brackets around, they are required. The :: abbreviations are also allowed. The following two cvars may be of particular interest in this case:

net_enabled: Determines, which protocols EF is actually using. You can add (sum!) the following values for their effect:

1. 1: enables IPv4
2. 2: enable IPv6
3. 4: prioritizes IPv6 over IPv4
4. 8: disables IPv6 multicast support

Example: to simply activate IPv4 and IPv6, use set net_enabled 3 (= 1 + 2).

net_port6: The UDP port to be used for the IPv6 protocol the server will listen on.

• Cvars
• In-Game Commands
• Maps
• Map Downloads

[ Back to Star Trek: Voyager Elite Force ]