[HarryPotter]

Originally Posted by cravenge Now that I have time to start working on plug-ins again, I'll try my best to elaborate.[SPOILER=Long answer:]Be aware that I'm going to be a little technical with this post so bear with me.

This explanation is very clear and to the point.

[Shadowysn]

Would it be possible to control Real Zoey Unlock to be disabled unless this plugin fails due to updates, at which point it reenables it?
So Windows servers don't begin to crash with their Zoeys and have a backup option automatically.

[replay_84]

Originally Posted by cravenge Now that I have time to start working on plug-ins again, I'll try my best to elaborate. Long answer: Be aware that I'm going to be a little technical with this post so bear with me. You ever wonder why the L4D1 survivors are never in the same team as the L4D2 ones in the finale of The Passing or why they don't show up on the credits after beating it? That's because it was the original design Valve came up with. They made it so that several of the game's internal functions would only account for 4 survivor indexes and no more/less than that. As long as the value of "m_survivorCharacter" netprop of each survivor stays within the range of 0-3, there's nothing to worry about and that includes clones since they have no impact (well, except for that one bug pre-TLS where only the originals could talk but that's not the point here) However, if that goes beyond the range, abnormalities start to happen and it's because the game didn't expect such change. One example is the unusually large amount of common infected spawned in hordes and another from my experience is the occasional disappearance of common infected even though they're within the line of sight. If you want to test the second case for yourself, play an L4D1 campaign with the L4D2 set preferred but with the L4D1 survivors only. Normally, Valve would be able to fix the issue by increasing the index limit and applying said limit to functions where it should also be in but from what I have analyzed while skimming through the binaries, said fix would break a lot of signatures if implemented in a future update and most of them are often used in popular plug-ins nowadays. Even though they added mod support, I wonder if they expected SourceMod implementation at all. Short answer: This is highly recommended for servers using CSM or any other character selecting and/or changing plug-ins where players can switch to L4D1 survivors in L4D2 (and L4D1 as well if the L4D2 crew is set) campaign.

Not sure if I understand if I still have to use it on a L4D1 server when L4D2 chars are never involved. I says L4D/L4D2 in the title.

[cravenge]

Originally Posted by replay_84 Not sure if I understand if I still have to use it on a L4D1 server when L4D2 chars are never involved. I says L4D/L4D2 in the title.

This is also a must for L4D1 if your server uses any custom character having the "m_survivorCharacter" netprop set to above 3 or even negative values for some bizarre reason (mostly due to erroneous coding of the character managing plug-in you have).

[cravenge]

Originally Posted by Shadowysn Would it be possible to control Real Zoey Unlock to be disabled unless this plugin fails due to updates, at which point it reenables it? So Windows servers don't begin to crash with their Zoeys and have a backup option automatically.

Yes, I already have that fallback option in mind.

[replay_84]

Originally Posted by cravenge This is also a must for L4D1 if your server uses any custom character having the "m_survivorCharacter" netprop set to above 3 or even negative values for some bizarre reason (mostly due to erroneous coding of the character managing plug-in you have).

Ok thanks. Then I'll try it on my servers.

[jjambo789]

After the recent 2226 version update,

/2022 - 105:15: [SM] Exception reported: Signature for "ConvertToExternalCharacter" is broken!
L 11/19/2022 - 105:15: [SM] Blaming: survivor_character_fixes.smx
L 11/19/2022 - 105:15: [SM] Call stack trace:
L 11/19/2022 - 105:15: [SM] [0] SetFailState
L 11/19/2022 - 105:15: [SM] [1] Line 66, F:\Left 4 Dead 2 Server\survivor_character_fixes.sp::OnPluginS tart
L 11/19/2022 - 105:15: [SM] Unable to load plugin "survivor_character_fixes.smx": Error detected in plugin startup (see error logs)

[Silvers]

			"ConvertToExternalCharacter"
			{
				"library"	"server"
				"linux"		"@_Z26ConvertToExternalCharacter21SurvivorCharacterType"
				"windows"	"\x2A\x2A\x2A\x2A\x2A\x2A\x2A\x2A\x83\x2A\x2A\x8B\x2A\x2A\x75\x2A\x83\x2A\x2A\x77\x2A\xFF\x2A\x2A\x2A\x2A\x2A\x2A\xB8\x2A\x2A\x2A\x2A\x5D"
				/* ? ? ? ? ? ? ? ? 83 ? ? 8B ? ? 75 ? 83 ? ? 77 ? FF ? ? ? ? ? ? B8 ? ? ? ? 5D */
			}

[Shadowysn]

by the gods, that ConvertToExternalCharacter signature is volatile

where cravenge at with that 0.2 updata

[Silvers]

The one I posted is valid for previous versions and should be future proof.