Playercommands/Funcommands not working with latest stable release

msleeper · **Author**

I am getting errors when trying to use player/fun commands. I just updated to the latest version of MM and SM. Any ideas?

Code:

[playercommands.smx] "Console<0><Console><Console>" slapped ">f7> nulloperations<28><STEAM_0:0:2008913><>" (damage "0")
[SM] Native "SlapPlayer" reported: This function is not supported on this mod
[SM] Displaying call stack trace for plugin "playercommands.smx":
[SM]   [0]  Line 39, /home/builds/sourcemod/linux-1.3/build/plugins/playercommands/slap.sp::PerformSlap()
[SM]   [1]  Line 204, /home/builds/sourcemod/linux-1.3/build/plugins/playercommands/slap.sp::Command_Slap()

Code:

[playercommands.smx] "Console<0><Console><Console>" slayed ">f7> nulloperations<28><STEAM_0:0:2008913><>"
[SM] Native "ForcePlayerSuicide" reported: "CommitSuicide" not supported by this mod
[SM] Displaying call stack trace for plugin "playercommands.smx":
[SM]   [0]  Line 37, /home/builds/sourcemod/linux-1.3/build/plugins/playercommands/slay.sp::PerformSlay()
[SM]   [1]  Line 146, /home/builds/sourcemod/linux-1.3/build/plugins/playercommands/slay.sp::Command_Slay()

Code:

 
[SM] Native "IgniteEntity" reported: "Ignite" not supported by this mod
[SM] Displaying call stack trace for plugin "funcommands.smx":
[SM]   [0]  Line 69, /home/builds/sourcemod/linux-1.3/build/plugins/funcommands/fire.sp::PerformBurn()
[SM]   [1]  Line 392, /home/builds/sourcemod/linux-1.3/build/plugins/funcommands/fire.sp::Command_Burn()

Bacardi

What game ??? !!!!
TF2, l4d2..

[SM] Native "SlapPlayer" reported: This function is not supported on this mod

and try look these through rcon
plugin_print
meta list
sm plugins list
sm exts list

msleeper

It's TF2. All plugins/mods/extensions are loaded successfully, nothing is showing up as failed or listing errors.

Wazz

Check that the game data files are present and correct on your server.

msleeper

Very strange. I re-uploaded the gamedata files and restarted the server and it started working properly. I assume that an upload was corrupted or something. Either way, thanks for the assistance.