Closed deprid closed 1 month ago
Please provide more information to help me locate the issue. First, pay attention to the entire server startup process and check if there are any messages with the prefix [L4DToolZ]
. If so, please share them with me. Then, please execute the following commands on the server and provide the results: plugin_print
, meta list
.
On server startup:
Summary from above console log:
[L4DToolZ] tickrate: 60
maxplayers set to 18
, hmmm why 18? I set it to 12 in server.cfg
[L4DToolZ] sv_steam_bypass init error
[L4DToolZ] sv_steam_bypass init error
[L4DToolZ] maxplayers set to 31
Unknown command
, probably from the l4d2_bot_improvement.cfg
plugin_print
Loaded plugins:
---------------------
0: "L4DToolZ v2.3.2, https://github.com/lakwsh/l4dtoolz"
1: "Metamod:Source 1.11.0-dev+1155"
---------------------
meta list
Listing 9 plugins:
[01] Pounce Damage Uncap (1.1.0.0) by Michael "ProdigySim" Busby
[02] SourceMod (1.11.0.6964) by AlliedModders LLC
[03] Stripper (1.2.2) by BAILOPAN
[04] Actions (3.8.8) by BHaType
[05] CollisionHook (1.3) by VoiDeD, Adrianilloo, A1m`
[06] Resolve Collision Fix (1.10.1) by BHaType
[07] SDK Tools (1.11.0.6964) by AlliedModders LLC
[08] SDK Hooks (1.11.0.6964) by AlliedModders LLC
[09] DHooks (1.11.0.6964) by AlliedModders LLC
status
hostname: Red Herring Asia
version : 2.2.4.1 9309 secure (unknown)
udp/ip : 0.0.0.0:27016 [ public xx:27016 ]
os : Windows Dedicated
map : c1m2_streets
players : 1 humans, 0 bots (8 max) (not hibernating) (unreserved)
# userid name uniqueid connected ping loss state rate adr
# 2 1 "steeg" STEAM_1:0:59550968 00:54 26 0 active 30000 192.168.1.111:27005
# 3 "Coach" BOT active
# 4 "Ellis" BOT active
# 5 "Rochelle" BOT active
#end
Thank you for your feedback. After verification, I was able to reproduce this issue on the Windows server and will release a patch to fix it shortly.
Regarding the other issues you mentioned, maxplayers set to 18
is the default value set by the game engine during startup, which refers to the maximum number of clients and can be modified using sv_setmax
, though it differs from the concept of maximum players (excluding bots). [L4DToolZ] maxplayers set to 31
indicates that maxplayers has been overwritten to 31.
Additionally, the [L4DToolZ] sv_steam_bypass init error
is due to the server not yet establishing a connection with Steam during startup, which is normal. Initialization usually succeeds after the prompt Connection to Steam servers successful.
appears.
Please try version 2.3.3.
Thanks for the quick update. I have tried the version 2.3.3 (l4dtoolz-2.3.3-31.zip), the tickrate now correctly displays 60000
(with or without sm_cvar sv_minrate 60000
, sm_cvar sv_maxrate 60000
), the issue has been fixed!!
Now I can get rid of the old tickrate_enabler...
By the way, is it a normal behavior that you cannot get last players list anymore on Steam (Steam › View › Players) when using sv_steam_bypass 1
? Or should I open new issue for this one?
Because after enabling sv_steam_bypass
, when players connect to the server, the server does not connect to Steam to verify the player’s ticket, so this is normal behavior.
Okay, got it, I still can see player's steam ID in the chat log plugin, so I'm okay with it as long as no more No Steam logon error.
According to feedback from other users, there might still be a few No Steam logon
errors, but it has significantly decreased compared to when the feature was not enabled.
I've just found the culprit. Your l4dtoolz fork's tickrate enabler function is not working, at least in my case. As side note, I use two cvars differently than the old l4dtoolz:
sv_force_unreserved 0
(old value is 1),sv_steam_bypass 1
(old value is none).I also have installed the recommended plugin a2s_fix along with it for Bypass SteamID Verification feature (the main reason I use your l4dtoolz is because my clients keep getting
No Steam logon
error, but somehow, now my clients get sometimed out
error more frequently, although the old l4dtoolz have thetimed out
error as well asNo Steam logon
).I reinstalled the old tickrate_enabler and enabled both
sm_cvar sv_minrate 60000
,sm_cvar sv_maxrate 60000
(because without them enabled, it will be30000
too). And then combined with your l4dtoolz fork, boom,status
console command showed60000
. I finished about 5+ test and re-test to confirm the issue.Meaning, without the outside tickrate_enabler, using ONLY your l4dtoolz fork, the value is always
30000
. To get60000
value and to get rid ofNo Steam logon
, I have to use both the old tickrate_enabler and your l4dtoolz fork. I even saw one of my client oddly got10000
value (using your l4dtoolz only)?! How did he even got such value since the server was set (unintendedly)30000
.So I hope you could fix this issue so that I don't need to install the old tickrate_enabler to get
60000
.Originally posted by @deprid in https://github.com/lakwsh/l4dtoolz/issues/11#issuecomment-2349947624