If b_statsaver is 1, then player XP, skills, medals, weaponstats, team, class, and weapon selection are all saved across disconnects.
These stats will still be reset whenever the server would normally reset them (e.g. at the beginng of a new campaign).

Admins may further refine the skill system by changing amount of XP required to increase rank in each skill. This can be especially useful with per-map configurations.

The XP requirements for each skill level are split up over 7 variables:
b_levels_battlesense
b_levels_covertops
b_levels_engineer
b_levels_fieldops
b_levels_lightweapons
b_levels_medic
b_levels_soldier

Each variable accepts 1-4 integers denoting the amount of XP required for each level. Omitting values will disable any of the levels higher than those specified. A value of -1 for any skill level also disables that particular level, although the associated skills will still be gained when reaching a higher level, if allowed. Leaving the value blank causes the default values to be used: 20 50 90 140.

Examples:
Disable level 3 and 4 engineers:
b_levels_engineer "20 50"
Don't give medics full revive until level 4:
b_levels_medic "20 50 -1 140"
Give everyone binoculars almost immediately:
b_levels_battlesense "5 50 90 140"

Players can see the currently active skill customizations with the skills command.

The stopwatch XP saver, which can be toggled with the b_xpstopwatch variable, will keep XP across stopwatch rounds A->B, similar to the way campaign play keeps XP. After both halves of a stopwatch round are complete, XP will be reset.

ET Pro adds the ability for server administrators to place a watermark image on the client's HUD, above the lagometer.   (For examples, see the player guide.)

The watermark display is controlled by 3 variables: The first, b_watermark, specified the filename of the watermark image. The filename used in b_watermark automatically has 'watermark/' prepended to it, so if b_watermark is set to 'ourclan/ourwatermark', the server and client will actually look for 'watermark/ourclan/ourwatermark.

The watermark display is also affected by b_watermarkFadeAfter and b_watermarkFadeTime: b_watermarkFadeAfter specifies the time, in seconds, that the watermark will appear on-screen before fading away (although a value of -1 will prevent it from fading away at all.) The watermark display/fade process will occur every time a map is loaded, so some administrators may prefer to only display the watermark for a moment to ensure it does not obscure the display. Finally, the b_watermarkFadeTime variable specifies how long the fading process will take, allowing administrators to decide how quickly their watermark fades away.

Making watermarks is a fairly simple task, but there are some restrictions and general tips that you should keep in mind.

• The dimensions of the watermark must be a power of two--for example, 32x32, 64x64, 128x128.
• The watermark is always drawn at the same size relative to the rest of the display (which is 48x48 pixels at 640x480), but it won't hurt to make the watermark a bit larger than this--players running the game at higher video resolutions will see more detail if that detail exists in the watermark image. Using a watermark size of 128x128 will ensure it looks nice up to 1600x1200 without making the required download very large.
• Try to keep the filenames unique--as a rough guide, we suggest something like watermark/ourclan/ourwatermark.tga for the filename, placed inside a pk3 named something like ourclan-watermark.pk3.
• For best results, use alpha channels (transparent areas) where possible in the image--you can make part of the watermark partly or fully transparent, allowing the game view to be seen through the transparent parts of the watermark.

ET Pro gives server administrators more fine-grained control over weapons restrictions: the number of flamethrowers, mobile MG42s, mortars, and panzerfausts allowed for each team can be individually adjusted.

Heavy weapons restrictions are split up into the following variables:
team_maxFlamers
team_maxMG42s
team_maxMortars
team_maxPanzers
team_maxMines

Setting any of these variables to -1 disables the limitation, while a value of 0 or greater specifies the number of each weapon that each team is allowed to use.

Example:
To disable panzerfausts entirely and allow 1 flamethrower on each team, one would use:
team_maxPanzers 0
team_maxFlamers 1

Misc weapon restrictions:
b_riflegrenades (default 1, enabled) allows admins to enable/disable rifle grenades (useful for LMS/OLTL games)

The multiview system from OSP has been added to ET Pro. Multiview functionality can be toggled with b_multiview. Multiview may sometimes take more bandwidth and CPU usage when enabled, so administrators whose servers are using most of the available CPU power or bandwidth may wish to leave it disabled.

For additional information on multiview, see the player guide.