Garry's Mod

Garry's Mod

ConVar Preset Manager
Showing 1-10 of 12 entries
< 1  2 >
Update: 21 Jan @ 6:46am

Update: 5 Jan @ 5:52pm

Update: 1 Jan @ 12:41am

Update: 21 Oct, 2024 @ 9:11am

Update: 18 Oct, 2024 @ 5:34am

Update: 12 Oct, 2024 @ 10:57pm

Update: 12 Oct, 2024 @ 10:56pm

Update: 10 Oct, 2024 @ 5:06am

Update: 5 Oct, 2024 @ 2:01pm

Update: 5 Oct, 2024 @ 12:28pm

Server ConVar Quickload (svconvarent):.

When spawned, immediately loads a ConVar preset called “quicksave” stored on the server.
Can be executed from the client side.

Server convar quicksave (svsaveent):.

When spawned, saves the current server ConVar configuration on the server with the name “quicksave”.
Can be executed from the client side.

Server cvar default (svdefent):.

When spawned, saves the current ConVar settings as “quicksave” and “backup” and creates and loads a default preset that records the initial server convar values.
This is intended to address the bug described below.

convar_anti_playerconnect_convar_bug:
If this is set to 1,
When a client connects to you
-Save the current settings as “quicksave” and “backup”.
-Create a default ConVar preset.
-. Load the default preset.
This is also a workaround for the “connection failure due to convar” bug, which is described at the bottom.To prevent the bot from malfunctioning, it is activated when it senses that the same user has connected twice in a row.
If you are experiencing the “connection failure due to convar” problem described at the bottom of this page, you will need to follow the steps below to get the client to connect.
1. Connect and disconnect immediately.
2. Connect again and disconnect immediately
3. Wait about 7 seconds
4. Connect again
(I know it's tedious, but this is the only solution I could find for “connection failure due to convar” at the moment.)
--
“connection failure due to convar” bug,
I am experiencing a bug in which when playing gmod online on a P2P or private server, the client cannot connect if the convar of the player who is the server is not the default value.
This problem has always occurred to me, but I have not been able to find a solution on the internet, so I have taken the approach of having the client connect with the convar set back to default.
This is why I am adding a specification to return convar to default.

If the default specification is not needed, it can be disabled with this convar:
convar_anti_playerconnect_convar_bug 0
convar_entity_svdefent_enable 0