AlliedModders

AlliedModders (https://forums.alliedmods.net/index.php)
-   General (https://forums.alliedmods.net/forumdisplay.php?f=58)
-   -   L4D2 - The Last Stand Update - Issues and Bugs - Mega Thread (https://forums.alliedmods.net/showthread.php?t=327495)

Silvers 09-22-2020 21:17

L4D2 - The Last Stand Update - Issues and Bugs - Mega Thread
 
I've started this topic in the hope to keep everything in 1 place, instead of bumping various plugin threads, post issues here and when they're fixed someone can bump the relevant thread with fix details.


Developers:
Mostly vtable offsets need updating. These can be quickly fixed by checking last version vtable offsets against new version. Drag and drop the old/new linux binary into https://asherkin.github.io/vtable/ and compare if offsets shifted (seems most things changed by +1 except very early vtable functions).



disconnected (reason "Disconnected: Issued too many commands to server"):
Quote:

Originally Posted by Lux (Post 2718846)
i set sv_quota_stringcmdspersecond to 999999

Since alot of stuff uses it e.g. z_spawn spawning cmds, ect.

Silver put it in the OP since this shitty "sv_quota_stringcmdspersecond" at default value will murder most servers at atlest use FakeClientCmd to do stuff.

Put sv_quota_stringcmdspersecond "999999" in cfg/server.cfg



Server crashing?
  • Set cvar sv_voiceenable 0 to prevent server crashing - game bug. Valve update fixed (25-Sep-2020)
  • 2 sourcemod gamedata files require updating if your server hasn't automatically updated them.
  • Requires SM 1.10 to stop gamedata being overwritten.
  • Check for plugin and extension updates (bunch listed below, not complete list - post links to updates I missed).



Updated plugins

- All my plugins updated.

- Some plugins may not be required anymore due to internal fixes within L4D2. For example Knife Unlock plugin seems to be obsolete.

- Post updated plugins missing from below and I'll update the lists.


Updated plugins (my plugins):
Updated plugins (3rd party):
Extensions:

ProdigySim 09-23-2020 17:22

Re: L4D2 - The Last Stand Update - Issues and Bugs - Mega Thread
 
Hi there, I'm the guy who posted the updated sourcemod gamedata for the update.
I got trusted with early access to the game and I've been able to inspect some of the binaries to find out about what may break sourcemod plugins/extensions.

I can't talk a lot about the update, but in hopes of helping this update go smoothly,
I wrote up some notes about the major breaking changes I found, which is available as a Github Gist: L4D2 2.2.0.0 gamedata fixes.

If you make extensive user of vtable offsets or memory address reads in your gamedata you might find useful information here to get your plugin ready.
Also, there have been a number of bugfixes in the game, for things like Charger Chest-bumps. So you might find that some plugins become redundant after the update drops.

I apologize for the selection bias of plugins I've tested, but hopefully some of this is generic enough to help.
I'll be around on the SourceMod discord today and can try to answer more questions.

Accelerator 09-24-2020 02:55

Re: L4D2 - The Last Stand Update - Issues and Bugs - Mega Thread
 
What about l4dtoolz? https://github.com/Accelerator74/l4dtoolz
Will the signatures change?

Silvers 09-24-2020 03:00

Re: L4D2 - The Last Stand Update - Issues and Bugs - Mega Thread
 
I've always wondered about this, and it sucks theres no gamedata and hardcoded. They didn't change during the last major plugin breaking updates (The Passing and Steam Pipe - which broke many things), so I suspect this semi major update wouldn't break it either.

Edit: Have locally updated many of my plugins in preparation for the update with what's knowm to change (vtable offsets) and I'm assuming the melee weapon class/script names which I'm pretty sure will be correct so all my melee plugins will be updated straight away. I just want to verify everything before posting so waiting for the update.

For all 3rd party plugins, a post here mentioning which plugin or whats wrong will help. I can't review them all but most will be simple gamedata changes (especially if it's just vtable). Some common plugins I'll update to their threads posting the new gamedata (after I'm done reviewing and posting my stuff), at least it seems a bunch of people will be helping update so should progress very quickly.

Servers may crash with vtable changes because the wrong function is now being called with the wrong args, that's the problem with vtable changes it's not easily known that they are broken unless the server crashes or you specifically test something and not getting the expected results. Signature changes are much easier to detect since most plugins written correctly would throw an error about wrong signature (unless a signature matches something new - again that being the wrong function so would probably crash server anyway - and with that Accelerator extension would help pinpoint if required).

Accelerator 09-24-2020 03:04

Re: L4D2 - The Last Stand Update - Issues and Bugs - Mega Thread
 
Ok, hopefully it will work, but here are a couple more extensions that begs the question :)

Pounce-Damage-Uncap: https://github.com/Accelerator74/Pounce-Damage-Uncap
l4d2_tickrate_enabler: https://github.com/Accelerator74/l4d2_tickrate_enabler

And still interested in the question. The new melee weapons are named shovel and pitchfork (for scripts/console), is that right? https://github.com/Accelerator74/l4d...tension.cpp#L6

Silvers 09-24-2020 03:15

Re: L4D2 - The Last Stand Update - Issues and Bugs - Mega Thread
 
Yeah those are 99% the melee script/classname.

Those extensions probably won't break. l4d2_meleespawncontrol extension is old and superceded by Info Editor plugin which handles the same + many other features that servers and other plugins have been taking advantage of. I would recommend people switch over to that instead of something that's hardly supported.

Accelerator 09-24-2020 03:18

Re: L4D2 - The Last Stand Update - Issues and Bugs - Mega Thread
 
Quote:

Originally Posted by Silvers (Post 2718582)
l4d2_meleespawncontrol extension is old and superceded by Info Editor plugin

Definitely if you are using dhooks :) Not all my servers need dhooks, left4downtown or left4dhooks. Therefore, I prefer to use the simplified obsolete version, l4d2_meleespawncontrol :)

Silvers 09-24-2020 03:29

Re: L4D2 - The Last Stand Update - Issues and Bugs - Mega Thread
 
Well since you've been known to compile extensions, you can provide support for those! That would be greatly appreciated. I suspect most will work fine, l4d2_meleespawncontrol will need an update for the 2 new melee classes. L4DToolZ we'll see but suspect fine also, if even required anymore (screenshot showed 20 players in 1 server testing new update...)

Accelerator 09-24-2020 03:34

Re: L4D2 - The Last Stand Update - Issues and Bugs - Mega Thread
 
Quote:

Originally Posted by Silvers (Post 2718584)
L4DToolZ we'll see but suspect fine also, if even required anymore (screenshot showed 20 players in 1 server testing new update...)

It would be nice if the expansion of the slots was already in the game initially :)

Silvers 09-24-2020 03:36

Re: L4D2 - The Last Stand Update - Issues and Bugs - Mega Thread
 
Sounds like it's not a stock feature but L4DToolZ still works with the update. So no changes.


All times are GMT -4. The time now is 16:41.

Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.