Can not start listen server with SourceMod

sourcemodteam-fortress-2

I have SourceMod set up for a listen server on my copy of TF2. This worked fine as of the Invasion update. However, I updated to the latest version of TF2 and now when I start a server, it crashes before the map loads. This happens regardless of whether I'm setting up a LAN game or a bot match. Removing SourceMod seems to fix it, so I think the problem is with SourceMod itself.

SourceMod and Metamod both load, I can use meta version, and I am using the -insecure flag, but I am unable to start any servers while using them.

I am able to access TF2 with SourceMod enabled, and I can connect to other servers, but I can not start my own without the game crashing.

Does anybody know why this is happening and how I can fix it?

Best Answer

The version of SourceMod or its plugins is out of date.

Usually just updating SourceMod works, however, if the game keeps crashing, check your plugins for new updates.

In my case, the gamedata for TF2Attributes had to be updated. I updated both SourceMod and TF2Attributes and it works fine, I can create servers and people can join them.

Related Solutions

How to create server-wide aliases for console commands in Source games

The server alias syntax is the same as on the client side. You can place aliases inside server.cfg or choose to separate them into their own file for the sake of neatness.

server.cfg

exec aliases.cfg

aliases.cfg

alias "meleeon" "sm_cvar sm_meleemode_enabled 1;sm_cvar example 0"
alias "meleeoff" "sm_cvar sm_meleemode_enabled 0;sm_cvar example 1"

You should also be able to change the default values of cvars registered in SourceMod plugins or have them vary by map. Just ask if that interests you.

Problems connecting to a friend’s server in Team Fortress 2

If it's only people on the same LAN that can connect, then the problem is almost definitely to do with the server's firewall or, more likely, the router that your friend is using.

In the first case, it may be that the firewall is configured to accept connections from computers on the same subnet (i.e. on the LAN), but block connections coming from computers outside the subnet. Set the firewall permissions on the server, and you're set.

In the second case, it's likely that the ports used by the server aren't being forwarded by the router. The router doesn't know what to do with incoming connections that weren't initiated by one of the computers on the LAN, and the TF2 server might not be smart enough to tell the router that it's listening on port 270xx. Forward the required ports using the router (web) configuration tool, and you should be good to go.

Here is some more information about setting up a server, and the needed ports.

EDIT: @Matthew Read posted a nice answer on a similar question listing the ports in use by Valve games.

Best Answer

Related Solutions

How to create server-wide aliases for console commands in Source games

Problems connecting to a friend’s server in Team Fortress 2

Related Topic