Instale o Steam
iniciar sessão
|
idioma
简体中文 (Chinês simplificado)
繁體中文 (Chinês tradicional)
日本語 (Japonês)
한국어 (Coreano)
ไทย (Tailandês)
Български (Búlgaro)
Čeština (Tcheco)
Dansk (Dinamarquês)
Deutsch (Alemão)
English (Inglês)
Español-España (Espanhol — Espanha)
Español-Latinoamérica (Espanhol — América Latina)
Ελληνικά (Grego)
Français (Francês)
Italiano (Italiano)
Bahasa Indonesia (Indonésio)
Magyar (Húngaro)
Nederlands (Holandês)
Norsk (Norueguês)
Polski (Polonês)
Português (Portugal)
Română (Romeno)
Русский (Russo)
Suomi (Finlandês)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Relatar um problema com a tradução
1. Reinstalling Left 4 Dead 2 (delete local cash option in steam library), then deleting the folder in steam>steamapps>common>
2. Validate files
Do this in this order.I had the same issue it was mainly caused i played on local and host had diffrent mod on pills.Anyway validate files and should be ok.
I don't think this will solve your problem, because you are getting kicked for a MISSING script, not a CONSISTENCY script. I seriously recommend just doing a clean reinstall, but you can try sv_consistency 0 for both the host and your friend joining.
Ever hear of an autoexec.cfg file?
The server needs "sv_consistency 0" in it's config to stop it from checking and then kicking for consistency errors. The message that pops up when being kicked is, I think, "missing file" instead of "inconsistent file" which is misleading. If a friend is hosting locally, he is acting as the server and should change that variable accordingly. It doesn't matter at all what connecting clients have sv_consistency set to, as long as they are not the host.
If this friend being kicked can actually connect to the server and play for a minute or so before being kicked, then it's a consistency check kicking him and changing "sv_consistency 0" on the server will solve it. If he can't even connect to the server, the server/host has an addon that modifies the weapon_pain_pills script which requires all connecting clients to have the same addon installed to even connect (sort of like how custom campaigns require everyone to have it installed in order to connect to the server). In this case, the offending addon would either have to be removed from the server/host or distributed to each client before they can connect. It's possible three of you have that addon now, and this fourth friend is not able to connect because they don't have it.
I should also point out there is no such thing as a "clean" reinstall anymore with The Workshop. If a Workshop addon is causing problems, you're just going to redownload 14Gigs of perfectly fine files and then the Workshop will download the same 10MB addon that caused the original problem anyway. At most, all you ever needed to delete was the /cfg/ folder and /addons/ folder before verifying the cache (which had the same effect as a complete reinstall), but now you might need to also unsubscribe from some Workshop content as well when troubleshooting errors. But telling people to reinstall the entire game is terrible advice, given out when people don't know what the real problem is but feel like chiming in anyway.