-
-
Notifications
You must be signed in to change notification settings - Fork 45
FAQ
Please watch the following videos that walkthrough the background and initial setup steps.
This is always a configuration error.
Note — IW4MAdmin configuration is stored as a text file in Configuration/IW4MAdminSettings.json
Make sure your server is running and has a map loaded
Make sure your rcon password is not commented out (remove the forward slashes before)
// rcon_password "this is wrong"
rcon_password "this is right"
- You can verify this by entering
rcon_password
orget rcon_password
(for Plutonium T6/IW5) into the server console and comparing the output with IW4MAdmin configuration to make sure they are identical.
Make sure the port the server is running on matches what you entered for IW4MAdmin
- You can verify this by entering
net_port
orget net_port
(for Plutonium T6/IW5) into the server console and comparing the output with IW4MAdmin configuration to make sure they are identical.
Your router may not support NAT Loopback
- If you are hosting from a home PC, and using your external IP Address, try changing your server IP in the IW4MAdmin configuration to 127.0.0.1
Make sure your game log file is being created and log sync is turned on
- Each server must have a unique log file name set in the configuration via the
g_log
dvar - Example —
set g_log "my_server_hostname_mp.log"
-
g_logsync
must be set to always flush (1) for IW4x, (2) for T6 - Example —
set g_logsync 1
This means you selected the wrong parser or the game server port you entered is incorrect
- Ensure the port listed in the IW4MAdmin error message matches the port of your game server
- You can verify this by entering
net_port
orget net_port
(for Plutonium T6/IW5) into the server console and comparing it to the error message port - Ensure the
EventParserVersion
andRconParserVersion
are identical inIW4MAdminSettings.json
and they correspond to the game server you are hosting
If you are running IW4MAdmin remotely, you must setup the game log server python script
If you entered the log path manually, ensure it's correct