Abonneren om te downloaden
ConVar Preset Manager

This mod is a tool to manage ConVar (console variables) for Garry's Mod server and clients.

■Description of main functions
Save current ConVar settings as presets and load them later. Available for both server and client.

■Quick Guide

1. Open the spawn menu, open the Options tab, and open “Convar Preset Manager” from the ConvarPreset tab.
2. Enter a name in “Enter preset name to save”.
3. Select “Server&Client”.
4. Save convar as a preset in “Save Preset”. 4 items should be newly saved. See below for the features and reasons.
5. To load a saved preset, select it from the list and use “Load Selected Preset” to apply the convar in gmod.

----------

■Difference between server and client

-server: Convars are managed and stored on the server side and basically cannot be changed by the client.

-client: Records convar that is managed and stored on the client side.

■Difference between getconvar and clientvdf/servervdf

-getconvar: records the current value of the ConVar valid in the game as a txt file, but due to a bug in gmod, not all the convar are recorded and the file may be interrupted in the middle. In such cases, use clientvdf/servervdf.

-clientvdf/servervdf: reads ConVar values directly from cfg/client.vdf and cfg/server.vdf, respectively, and saves and reads them as txt. Since it records the convar at the start of the game, there will be a difference from the current convar, but it should not cause a bug where the convar cannot be recorded.

Save as txt in "data/convar_presets" and "data/convar_presets_client".


Quickload (svconvarent):.

Loads a ConVar preset “quicksave”.
Can also be executed from the client side.

Quick Save (svsaveent):.

Saves the current server ConVar to the server with the name “quicksave”.
Can also be executed from the client side.

--
The following is a workaround for the “connection failure due to convar” bug.

■About the “connection failure due to convar” bug,
When playing gmod online on a P2P server or private server, there is a bug that prevents the client from connecting if the convar of the player who is the server is not the default value.
This problem has been occurring for over 3 years now, and although I have seen similar questions on the internet, I have not been able to find an effective solution, and in the end, I have not been able to solve the problem except by forcing the client to connect with the convar set back to the default.

Therefore, we are adding a specification to return the convar to default.
From here on down, convar will be the function to achieve that specification.

■cvar default(svdefent):.

When spawned, saves the current ConVar settings as “quicksave” and “backup,” creates a default preset that records the initial server ConVar value, then restores the ConVar.
This is one of the workarounds for the “convar connection failure” bug described at the bottom.

■convar_anti_player_connect_convar_bug:
This is one of the workarounds for the “connection failure due to convar” bug listed at the bottom of the page.
If this is set to 0,
If the client is set to
-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 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 must follow the steps below to enable the client to connect.
1. connect and immediately disconnect.
2. connect again and disconnect immediately.
Wait about 7 seconds. 4.