Home › Forum › MultiPlayer Game Hacks & Cheats › Steam Games Hacks & Cheats › PLAYERUNKNOWN'S BATTLEGROUNDS (PUBG) Hacks & Cheats › PUBG Discussions & Help › Lag Switch Info (Post Patch)
Lag Switch Info (Post Patch)
Lag Switch Info (Post Patch)
Since the patch (already available on TEST servers, to be released tomorrow May 16th on main servers) you can lag switch only for a brief time, otherwise you will be blocked.
Actually if on a side it will nerf the lag switches a lot, on the other side its usage will be much more secure because you cannot abuse much of it, risking of being banned. For more information about how "safe" a Lag Switch can be, read this thread: http://www.mpgh.net/forum/showthread.php?t=1256169
Since the time of the lag jump is very short, activating/deactivating it manually looses much of its importance, instead it is important to release it (no matter what) before it locks you out, hence it makes much more sense to combine the activation and deactivation in a single command line.
The method I consider safest is:
- Turn Off your windows firewall if it's on;
- Add two new rules in your windows firewall (outbound/inbound .. whenever only the inbound one is effective) to block PUBG (TslGame.exe in your Steam game folder) for all the ports and protocols, the entry will look like this:
- Make a new bat file with this code:
The above batch file, will turn on your file, will wait for 2 seconds, will turn off the firewall again.
Run the batch file manually is now not practical anymore (due to the limited time you have), so the best way is to assign it to a button/macro (Logitech, Razer or whatever gaming device you have), I do NOT recommend you to use autoHotKey because it smells cheating by a mile.
Remember: it needs admin rights to work, so you must disable your Windows UAC, or turn it into an exe and give to it the admin rights, using any batch to exe converter, like this one: http://www.f2ko.de/en/b2e.php
Considerations:
- I intentionally did not added any profile, nor the exe name directly in the batch file to make it more generic as possible. BE can scan the batch file to look for "TslGame.exe", so IMO it's always better to add the firewall rule manually and to leave it there, instead of leaving traces in your batch file.
- Converting the batch into an exe is a smart way to overcome to the Admin rights issues, but it adds more bits to be traced by BE, whenever tracing isn't that trivial: the batch/exe doesn't remain in execution for longer than the timeout, but still risky. I didn't attached any pre-compiled version for obvious reasons: it will be flagged instantly by BE that is following this forum.
- I used 2 seconds in the above batch file, you can adjust it to the value that work for you (it won't be longer than 3 seconds anyway). From my tests I wasn't capable of exceed 1.5s ... however people are experiencing different timeouts, so adjust it to your needs.
- Because of the very short time, forget to use it manually in a proficient manner, it will be useful to "lag switch" in a firefight, by binding it to a macro in example, but you won't go in a house to kill a camper anymore.
- As I mentioned previously, now using a lag switch will be much more secure because you cannot "jump" for 20 seconds, doing crazy things (like multiple kills and such), but IT STILL DETECTABLE in theory, so using it for that single kill will work, doing crazy scores in every round (whenever the usage is not very limited) is a call to be banned:use at your own risk.
Actually if on a side it will nerf the lag switches a lot, on the other side its usage will be much more secure because you cannot abuse much of it, risking of being banned. For more information about how "safe" a Lag Switch can be, read this thread: http://www.mpgh.net/forum/showthread.php?t=1256169
Since the time of the lag jump is very short, activating/deactivating it manually looses much of its importance, instead it is important to release it (no matter what) before it locks you out, hence it makes much more sense to combine the activation and deactivation in a single command line.
The method I consider safest is:
- Turn Off your windows firewall if it's on;
- Add two new rules in your windows firewall (outbound/inbound .. whenever only the inbound one is effective) to block PUBG (TslGame.exe in your Steam game folder) for all the ports and protocols, the entry will look like this:
- Make a new bat file with this code:
Code:
@echo off netsh Advfirewall set allprofiles state on timeout 2 >NUL 2>&1 netsh Advfirewall set allprofiles state off
Run the batch file manually is now not practical anymore (due to the limited time you have), so the best way is to assign it to a button/macro (Logitech, Razer or whatever gaming device you have), I do NOT recommend you to use autoHotKey because it smells cheating by a mile.
Remember: it needs admin rights to work, so you must disable your Windows UAC, or turn it into an exe and give to it the admin rights, using any batch to exe converter, like this one: http://www.f2ko.de/en/b2e.php
Considerations:
- I intentionally did not added any profile, nor the exe name directly in the batch file to make it more generic as possible. BE can scan the batch file to look for "TslGame.exe", so IMO it's always better to add the firewall rule manually and to leave it there, instead of leaving traces in your batch file.
- Converting the batch into an exe is a smart way to overcome to the Admin rights issues, but it adds more bits to be traced by BE, whenever tracing isn't that trivial: the batch/exe doesn't remain in execution for longer than the timeout, but still risky. I didn't attached any pre-compiled version for obvious reasons: it will be flagged instantly by BE that is following this forum.
- I used 2 seconds in the above batch file, you can adjust it to the value that work for you (it won't be longer than 3 seconds anyway). From my tests I wasn't capable of exceed 1.5s ... however people are experiencing different timeouts, so adjust it to your needs.
- Because of the very short time, forget to use it manually in a proficient manner, it will be useful to "lag switch" in a firefight, by binding it to a macro in example, but you won't go in a house to kill a camper anymore.
- As I mentioned previously, now using a lag switch will be much more secure because you cannot "jump" for 20 seconds, doing crazy things (like multiple kills and such), but IT STILL DETECTABLE in theory, so using it for that single kill will work, doing crazy scores in every round (whenever the usage is not very limited) is a call to be banned:use at your own risk.
Originally Posted by santas
