IW4M commands not working in game chat

The Anzac

Hey so I have set up a server on T5 server and have almost everything set but still have a couple of issues. My main issue is that I am still unable to use IW4M commands (!rules for example) using the in game chat. My second is that I cannot switch to spectator. I am well aware that there is another topic with the same issue but it is extremely old and seems like it was not resolved.

swordswd

Is this zombies or multiplayer?

The Anzac

Multiplayer. sorry I should have mentioned

swordswd

I recommend going on IW4MAdmins discord for the support. Reason I asked zombies or mp is because ZM rcon doesn't work atm for t5. https://github.com/RaidMax/IW4M-Admin

Ahrimdon

Hi dude! So I noticed that after the last few updates, the game didn't log events correctly, so I reverted all my servers back to r3321, which fixed the issue. This may be a part of your issue, however it may not and may only be exclusive to me. Just thought it was worth mentioning.

Secondly, make sure your logs are setup manually in your IW4MAdminSettings.json.

      "IPAddress": "127.0.0.1",
      "Port": 28968,
      "Password": "123",
      "Rules": [],
      "AutoMessages": [],
      "ManualLogPath": "C:\\Plutonium Servers\\Call of Duty Black Ops I - Dedicated Server\\storage\\t5\\logs\\kinofive.log",
      "RConParserVersion": "Plutonium T5 Parser",
      "EventParserVersion": "Plutonium T5 Parser",
      "ReservedSlotNumber": 0,
      "GameLogServerUrl": null,
      "CustomHostname": null
    },
    {
      "IPAddress": "127.0.0.1",
      "Port": 28969,
      "Password": "123",
      "Rules": [],
      "AutoMessages": [],
      "ManualLogPath": "C:\\Plutonium Servers\\Call of Duty Black Ops I - Dedicated Server\\storage\\t5\\logs\\ascensioncotd.log",
      "RConParserVersion": "Plutonium T5 Parser",
      "EventParserVersion": "Plutonium T5 Parser",
      "ReservedSlotNumber": 0,
      "GameLogServerUrl": null,
      "CustomHostname": null
    }

Make sure to use two \'s when setting up your manual log path. You may need to mess around with some logging settings in your server config, but that may not be necessary. Good luck dude!

FutureRave

IW4M compatibility will be fixed in the next update.