Versions Compared

Old Version 38

changes.mady.by.user sknymick

Saved on

compared with

New Version 39

changes.mady.by.user sknymick

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Formatting: Player Party Control

...

Option Panel Name (if available)settings.tml nameDefault ValueOptionssettings.tml valuesDescription and Notes
Client




Player Name

[client]

[client.identity]

name

""Text fieldText fieldYour player name to join servers with
Server




Server Name

[server]

[server.identity]

name

""Text fieldText fieldSets the server name

[server]

[server.identity]

game-region

0

The server region. Unused in NWN:EE server browser.

[server]

[server.identity]

game-type

-1

The server type. Used when examining a server in the browser.

  • 0 - Action


  • 1 - Story


  • 2 - Story Lite


  • 3 - Roleplay


  • 4 - Team


  • 5 - Melee


  • 6 - Arena


  • 7 - Social


  • 8 - Alternative


  • 9 - PW Action


  • 10 - PW Story


  • 11 - Solo


  • 12 - Tech Support 

Post Game To Internet

[server]

[server.identity]

public

true

Enabled (Ticked)

Disabled (Unticked)

true

false

If ticked (on) it will post the game to Beamdogs centralised server list.
Server Port

[server]

[server.net]

port

51211 - 655351 - 65535The TCP port your server will initiate connections on. UDP firewall punching is used as well by the game.
Player Pausing

[server]

allow-player-pausing

false

Enabled (Ticked)

Disabled (Unticked)

true

false

If true it will allow players to have DM-like powers to pause a server.

In singleplayer mode always set to: Enabled

Server Restore Spell Uses On Login

[server]

restore-spell-uses-on-login

false

Enabled (Ticked)

Disabled (Unticked)

true

false

If false (default) it will act as if the player had rested if they rejoin and restore all their limited spell and feat uses. It's not recommended to enable this usually on a normal server.

If true a players spells and feats used will be saved and will be reapplied on login for server vault characters.

Only One Party

[server]

one-party-only

true

Enabled (Ticked)

Disabled (Unticked)

true

false

All players will join the first players party (first real player - DMs cannot run a party). Very useful for DM or coop playthroughs where there is only one expected party.

Obviously disable this on any server where there may be more than one party travelling around.

Player Party Control

[server]

player-party-control

false

Enabled (Ticked)

Disabled (Unticked)

true

false

Allows players to control their non-PC party members in the same way as DMs do (drag, ctrl+click, etc). This is off by default, and can be enabled in server settings

PVP Setting

[server]

pvp-mode

1 - Party

None

Party

Full

0

1

2

Changes the Player versus Player setting allowing or disallowing what you can attack with a hostile action. This is still dependant on the area PvP settings.

Full PvP: When full PvP is in effect, a PC can take hostile actions against any other PC. This includes outright attacks, pick pocket attempts, and (presumably accidentally) affecting party members with harmful area of effect spells that do not specifically exclude friends (such as fireball). That is, the full range of Player versus Player actions are available. This setting is only available under the "D&D hardcode rules" and "very difficult" difficulty settings.

Party PvP: When party PvP is in effect, a PC can take hostile actions against any PC not in the same party. This is similar to the full PvP setting, but protects party members from hostile actions. This setting is only available under the "D&D hardcode rules" and "very difficult" difficulty settings.

No PvP: When no PvP is in effect, a PC cannot take hostile actions against any other PC.

Item Level Restrictions

[ruleset]

item-level-restrictions

false

Enabled (Ticked)

Disabled (Unticked)

true

false

If enabled it enforces Item Level Restrictions, ie the character level can only equip things based on the value limit set in itemvalue.2da

In singleplayer mode always set to: Disabled

Enforce Legal Characters

[ruleset]

enforce-legal-characters

true

Enabled (Ticked)

Disabled (Unticked)

true

false

Known as "ELC". In multiplayer if enabled it checks that suibmitted characters (new and levelups) adhere to the game rules, since both character generation and levelup are technically done client side and sent to the server for validation.

It is highly recommended to leave this enabled and use NWNX to alter its behaviour for special things, unless you run a friends only game.

In singleplayer mode always set to: Disabled

Ruleset Min Character Level

[ruleset]

min-character-level

11 - 401 - 40

Minimum level to play on the the server. This only realistically works with Local Vault characters, since all Server Vault characters created start at level 1.

In singleplayer mode always set to: Disabled

Ruleset Max Character Level

[ruleset]

max-character-level

401 - 401 - 40

Maximum level to play on the server and presumably an enforced maximum level you can obtain on any one character by levelling - once there it won't award any more XP.

In singleplayer mode always set to: Disabled


[server]

reload-when-empty

true


true

false

If the server is empty, reload the module. Usually you'd have this set to false to disable your server reloading as one person logs in and one out, since modern servers take some time to spawn in all things and reload the module (sometimes several minutes).

[server]

savegames-store-characters

true

true

false

For co-op this is useful since it stores the players in the save game, retaining their relevant quest and XP and item progression (no need to export them each time)

Persistent worlds don't (or shouldn't) use save games so this is irrelevant for them.


[server]

savegames-vault-characters-only

false

true

false

Untested. Likely will only save to save games vault characters, which obviously can be a thing you do - DM run session with vault-only characters or somesuch. Needs some testing to work out how exactly it interacts with the above setting (likeiy if savegames-store-characters is false, this won't do anything regardless).
Server - Advanced




Server Disallow Shouting

[server]

disallow-shouting

false

Enabled (Ticked)

Disabled (Unticked)

true

false

Stops the yellow-coloured server wide shouts from being possible to do for players (DMs can always do them). You can also do a similar thing with OnPlayerChat which can alter the volume of a sent message (so you can convert it to a normal chat).
Server Show Dm Join Messages

[server]

show-dm-join-messages

true

Enabled (Ticked)

Disabled (Unticked)

true

false

If enabled it will show in grey a message "So and so joined as a DM." to all players. Set to false to hide this.
Server Tweaks Use Threaded Timers

[server]

[server.tweaks]

use-threaded-timers

true

Enabled (Ticked)

Disabled (Unticked)

true

false

This is meant to allow NWN to utilise a second core to do a second thread for reading the hardware timer, essentially:

Code Block
while(true) {
    read_hw_timer();
    sleep(config.timer_interval);
}

In SP it tends to make combat messages to wonky with damage messages commonly appearing before the attack rolls. This needs further testing however.

In MP it may benefit from leaving it enable and decreasing the resolution number if things mess up, the setting just below.

Server Tweaks Threaded Timers Resolution

[server]

[server.tweaks]

threaded-timers-resolution

1001 - 10001 - 1000

The resolution (timing) of the tweak above. It should be in milliseconds and decreasing it would lower the time between timer reads.

If you run a server with 2 cores, and want the threaded timers set to true, lowering this value to 1 is potentially a good idea see Server Performance Settings

Server Tweaks resman Max Memory Usage

[server]

[server.tweaks]

[server.tweaks.resman]

max-memory-usage

0.1250.01 - 0.80.01 - 0.8

The memory assigned to resman - the games memory cache of objects. Obviously servers don't load textures or models but they do load a lot of other things. This should be a % of system memory, and given the game is now 64bit could be increased to suitably use more memory on a server. You should monitor the memory usage on the server if you increase this value to make sure the game and OS still has sufficient memory to run.

Also note while the default value is 0.125 (12.5%) the in game options panel displays only 0.XX increments meaning it gets rounded to 0.13.

Server Tweaks 2da Engine Cache Size

[server]

[server.tweaks]

2da-engine-cache-size

111 - 10001 - 1000

This should affect the amount of engine 2da caching the game does. The main 2da files that are not permanently cached in memory are things like iprp_ files and the packages.2da related files. Increasing this number should lead to less loading hiccups on larger servers.

You may need to alter Server Tweaks resman Max Memory Usage if you increase this value significantly.

Server Tweaks 2da User Cache Size

[server]

[server.tweaks]

2da-user-cache-size

101 - 10001 - 1000

The amount of non-engine 2das cached for use with Get2DAString. Most of the engine 2da files (eg; spells.2da, or classes.2da) are automatically cached at game load, but as noted above some are a not, and all of the non-standard 2da files (des_* files, or custom ones) will use this cache.

You may need to alter Server Tweaks resman Max Memory Usage if you increase this value significantly.

Server Tweaks Game Object Cache Size

[server]

[server.tweaks]

game-object-cache-size

1612 - 2012 - 20

This is the 2^n amount of objects to store in game cache. If running in singleplayer this is bumped up one (since it is essentially running a server and client in one).

  • Minimum 12 is 2^12 or 4096 entries.
  • Default 16 is 2^16 or 65536 entries.
  • Maximum 20 is 2 ^ 20 or 1048576 entries.

The amount of entries are not equivalent strictly to amount of memory, since different objects have different sizes.

Increasing it should improve performance on higher memory systems (which nowadays is everything) especially persistent worlds. 18 or 20 would be useful to set it to.

Make sure to monitor your RAM usage if you increase this.

You may need to alter Server Tweaks resman Max Memory Usage if you increase this value significantly.

Server Tweaks Power Saving Clients Required To Disable

[server]

[server.tweaks]

[server.tweaks.power-saving]

clients-required-to-disable

11 - 2551 - 255

Do not increase this number.

The old server would sleep for 10ms each game update. This was fine on small servers but caused severe performance issues on large servers. We added a new config option called Clients Required To Disable CPU Sleep (under Game Options) with an integer value which can be used to toggle this behaviour back on. By default, the server will retain the old behaviour until one or more players join, then it will enter high performance mode without any sleeping. You can change this value to something that is greater than the maximum players allowed on your server if you never want the server to enter high performance mode.

It is recommended this is set to 1 in the modern age of processors else can cause server lag and stuttering for players.

Server Net accept Relayed Connections

[server]

[server.net]

accept-relayed-connections

true

Enabled (Ticked)

Disabled (Unticked)

true

false

Allows the UDP firewall punching via. master server. Leave it on for maximum benefits for connectivity.
Server Tweaks Message Limit

[server]

[server.tweaks]

message-limit = 400

400

400 - 65535

400 - 65535

Amount of message data to send, in bytes. This amount is sent and if there is more data it gets sent "Server Tweaks Game Obj Update Interval" microseconds later (200,000 is 200ms, or every 1/5th of a second).

Message data includes "A creature is new, and looks like this" "a creature you already know about has moved" "a creature has disappeared", "a placeable has appeared", "a VFX has gone off" and so forth. The priority of updates are roughly in the order of importance (ie placeables don't change much):

Code Block
GAMEOBJECTUPDATE_CATEGORY_CREATURE_IN_COMBAT,
GAMEOBJECTUPDATE_CATEGORY_CREATURE_ASSOCIATES,
GAMEOBJECTUPDATE_CATEGORY_CREATURE_PARTY_MEMBERS,
GAMEOBJECTUPDATE_CATEGORY_CREATURE_NOT_IN_COMBAT,
GAMEOBJECTUPDATE_CATEGORY_TRIGGERS,
GAMEOBJECTUPDATE_CATEGORY_DOORS,
GAMEOBJECTUPDATE_CATEGORY_ITEMS,
GAMEOBJECTUPDATE_CATEGORY_PLACEABLES,
GAMEOBJECTUPDATE_CATEGORY_AOEOBJECTS,

In EE the messages are larger than 1.69 due to additions to them for new features (such as visual transforms, or things the client gets updates on they didn't used to). This means object changes can be delayed being displayed clientside if they don't fit in the default 400 size.

With the default values it means that roughly every 200ms you send 400 bytes of updates to a client. If your updates are particularly complex, such as multiple new creatures, with a lot of VFX and whatnot, then only one will fit into the 400 byte window, so next one will come after another 200ms

Tweak this carefully with testing. You might also want to tweak the Update Interval.

  • Lower values are fine for smaller servers with not many object updates. Keeping this low might work if you also lower the Update Interval,
  • Higher values should load more objects in a message at once reducing "pop in" of things, at the sacrifice of some server performance/bandwidth.

Singleplayer: This is not actually used, and instead 20,000 is used to just update lots of data each interval since there's no bandwidth to worry about.

Server Tweaks Message Limit Loading

[server]

[server.tweaks]

message-limit-loading = 2000

2000

400 - 65535

400 - 65535

Message size limit during a loadscreen. Higher values mean clients get sent more data while they're sitting at the loadscreen.

Loadscreens mask sending over the areas tile information, and all static placeables, and other static data (sounds etc.). Static placeables especially can be numerous and loading can sometimes wait for the server to tell the client all of them.

The default value is higher than the normal message limit since loading events are rarer events and stuck the player in limbo until they're done.

Server Tweaks Game Obj Update Interval

[server]

[server.tweaks]

game-obj-update-interval = 200000

200000

0 - 500000

0 - 500000

This is the update interval (in microseconds, 200,000 = 200ms) as described under Server Tweaks Message Limit. The game will check that an PC needs updates on objects it sees/interacts with and then sends that data to them. This means you obviously get delays when many objects change (running around areas, monsters spawning in etc.) but possibly more tied to the message limit itself.

Tweak this carefully with testing. You might also want to tweak the Message Limit:

  • Lower values will send more frequent updates to clients. This should improve the "pop in" of things since messages are sent more often, at the sacrifice of server performance since it has to check for updates for players more often. This is something you should very carefully tweak to be lower.
  • Higher values than the default will delay updates to clients. This might work if you also increase the Message Limit, but if you don't you will get more delays and popups.

Singleplayer: This is used as the minimum update interval even if FPS is low. The 3 states in singleplayer are:

  • High FPS (over 60) do updates every frame (value is 0)
  • Low FPS (under 60) do it based on a formula depending on how much lower it is than 60, but the minimum is game-obj-update-interval (default 200000)
Server Tweaks Game Obj Update Interval Loading

[server]

[server.tweaks]

game-obj-update-interval-loading = 20000

20000

0 - 500000

0 - 500000

The loading interval for load screens.

The default value is lower than the normal message limit since loading events are rarer events and stuck the player in limbo until they're done.

Login




Player Password

[server]

[server.login]

player-password


Text fieldText fieldThe password needed to join if a player, or blank if no password.
DM Password

[server]

[server.login]

dm-password


Text fieldText fieldThe password needed to join if a DM, or blank if no password. For proper servers you also may want to do validation of DM logins (or log it's happening) OnClientEnter or using NWNX.

[server]

[server.login]

admin-password


Text fieldText fieldThis might not be used in the EE version of the nwnserver application but in 1.69 it allowed some remote control of the server without logging in as a client.
Max Players

[server]

[server.login]

max-players

61 - 2551 - 255

[server]

[server.login]

[server.login.player-dm]

enabled

true


true

false

If true it allows the "DM Login" feature in the debug menu to work allowing a player to sudo up to a DM role dynamically.
Autosave




Enabled

[server]

[server.autosave]

enabled

false

Enabled (Ticked)

Disabled (Unticked)

true

false

This will make the game autosave as per the below setting timer. Possibly useful for DM run or coop games where you might forget to save for a bit and lose progress due to a crash or lots of dying.

In singleplayer mode always set to: Disabled

Interval

[server]

[server.autosave]

interval

51 - 301 - 30Amount of minutes between autosaves, if enabled above.
Vault Characters




Vault Characters

[server]

[server.vault]

mode

1

Local

Server

1

0

Set to 0 for server vault, which is where the BIC files are stored on the server, and a new player has to create a new character to join.

In singleplayer mode always set to: 1

Vault Characters - Advanced




Suppress Base

[server]

[server.vault]

supress-base

false

Enabled (Ticked)

Disabled (Unticked)

true

false

Determines if characters in the root server vault directory are made available to players (in addition to characters in their subdirectories).

An odd setting you'll probably never enable unless in a DM run game (where you provide some characters to all players to pick from). Although most server vaults won't have anything in the root by default so it essentially does nothing either way on a new server.

Sticky Player Names

[server]

[server.vault]

sticky-player-names

false

Enabled (Ticked)

Disabled (Unticked)

true

false

Maps players' multiplayer names to their public cdkey in knownservernames.2da, so an admin can reference the two by looking through server files. If the 2da doesn't currently exist in the override folder on the server, it'll be created there. Said to really screw things up if you're using EE's new method of linking cdkey to player vaults.

See https://forums.beamdog.com/discussion/69795/organizing-the-servervault-and-sticky-player-names for more information.

By Player Name

[server]

[server.vault]

by-player-name

false

Enabled (Ticked)

Disabled (Unticked)

true

false

If true above, and true here, will map players' character names to the 2da instead of their multiplayer name.

See https://forums.beamdog.com/discussion/69795/organizing-the-servervault-and-sticky-player-names for more information.

Backup Server Characters

[server]

[server.vault]

backup-server-characters

false

Enabled (Ticked)

Disabled (Unticked)

true

false

Determines if saved characters are backed up on calling ExportAllCharacters and similar functions, or when a PC leaves the server. This copies the current BIC on disk to a BAK file named the same. Then if the server crashes on saving that BIC there is a known good BAK file.

These crashes may have been more common back in earlier versions of NWN before EE came out, and enabling it will decrease server performance due to the copying of BIC files to BAK files (with the servers process held up until this completes, on top of the usual BIC export work).

With a regular backup or method of retaining old BIC files on the filesystem, this is made redundant and can be left disabled.

Privacy




Client Privacy Advertise Device Capabilities

[client]

[client.privacy]

advertise-device-capabilities

true

Enabled (Ticked)

Disabled (Unticked)

true

false

Client only setting - if unticked then the client won't send information such as game version, window size and other pertinent information to the server for use in newer EE features.
[server.log]





[server]

[server.log]

[server.log.creature-deaths]

enabled = false

false

true

false

Logs all creature deaths to the server log. This can be replicated (with of course possibly more useful information) in a creatures OnDeath event.

[server]

[server.log]

[server.log.debug-mode-sends-to-players]

enabled = true

true

true

false

Will send to every player on the server any contents of a call to the nwscript command WriteTimestampedLogEntry - you wouldn't enable this on a production server it's more for easier testing!

[server]

[server.log]

[server.log.heartbeats]

enabled = false

false

true

false

Logs all OnHeartbeat event scripts firing. I mean I guess you might want to see how many are firing, but it also would add more lag since it of course is logging each one.

[server]

[server.log]

[server.log.rotation]

enabled = true

true

true

false

Rotate the server log files when the server shuts down. Needs some testing such as when the server crashes, does it check at startup and rotate or rotate on clean shutdown?

...