This will reset your Gmod back to it's default settings and remove any additional data that is not part of it's default function. Navigate to your Garry's Mod root directoryĬlick on the "FactoryReset-Gmod.bat" that is displayed in the above screenshot Get a backup of said directories or any other contents within /data/ if you have anything you value within it PAC3 Data is stored at: GarrysMod/garrysmod/data/pac3 & GarrysMod/garrysmod/data/pac3_cache PAC3 data is the only data that should matter for our server. Ensure to collect a backup of any important data in your Gmod before performing this remedy if there is anything you wish to preserve. WARNING : This remedy will almost certainly fix your issue, however, it will delete all settings you have configured for Garry's Mod as well as any PAC3 data you have saved.
The file should be empty by the time you're done. Locate the cache folder, open it, and delete all contents within it ( Can be opened via Steam > Properties > Local Files > Browse Local Files ) ( Often is: steamapps\common\GarrysMod\garrysmod ) Navigate to your Garry's Mod game directory PAC3 should be the only data within there that matters in there. So, give it a quick skim before fully removing to see if there is anything you wish to keep. However, things such as 'PAC3' data can one contained there. WARNING : Chances are, you have nothing important in your cache. Attempt to connect to the server once this is done to see if the issue is resolved Navigate to the "Betas" tab and select the " x86 - 64 - Chromium + 64-bit Binaries" build of Garry's Mod Navigate to your Steam Library Page and Right-Click to " Properties" on your Garry's Mod The best option that will not require you to reset anything One of the listed solutions almost certainly fix your issue. If you have been experiencing a never ending " Sending lua" or " Receiving lua" message when attempting to connect to our server that results in you being stuck on the initial loading screen forever - this is a list of various solutions that have been reported by community members that can fix your issue.
0 kommentar(er)
