search

Tsuey / L4D2-Community-Update

Help us shape the potential future of L4D2 vanilla.
70 stars 23 forks source link

Custom campaign consistency error in versus #296

Open lunatixxx opened 2 years ago

lunatixxx commented 2 years ago

Description

Here I will talk about competitive server that block addons and have sv_consistency protected.

If the player custom campaign is not named exactly like the one uploaded on the server, even if it is the same version player will not be able to join and receive a consistency error.

This is the most stupid thing i have ever see and cause a lot of confusion, because workshop maps have just numbers in their name compared to when you take them on gamemaps.

This is not a problem on campaign because addons are allowed.

Anyway i made a guide that will definitely avoid headache to others: https://steamcommunity.com/sharedfiles/filedetails/?id=2842748197

Reproduction steps

No response

Additional files

No response

Derpduck commented 2 years ago

I am not able to reproduce this, either by renaming the addon which has been downloaded directly from the server host, or by using the workshop version of the addon. Are you sure players simply don't just have a different version of the addon, or that the consistency checks on your server are correctly configured?

lunatixxx commented 2 years ago

I tested myself with city17l4d2, could launch from lobby versus and arrived on server. Renamed the map city16l4d2 on my addons folder, launching again from lobby and this time receiving a consistency error for city17l4d2.vpk

100% sure we had the same version.

I have :

sv_consistency_fix plugin from sirplease.

sv_consistency 1 sv_pure 2 sv_pure_kick_clients 1

Derpduck commented 2 years ago

I reproduced the error on a SirPlease server following your steps. However, we cannot guarantee functionality with modifications such as SourceMod plugins. Could you try to reproduce the same issue with any relevant plugins unloaded from the server?

lunatixxx commented 2 years ago

This is not caused by a plugin as i removed the only one that could interfere. Just reproducing that with "sv_consistency 0" will make you able to join, which is not a solution for versus servers.

Even allowing addons in versus from addonconfig give the same problem, the culprit is really sv_consistency.