Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem


If you don't want that, you'll have to use an autoexec with the above text listed in Steam Group Servers or mm_dedicated Method: section. Or just manually paste it every time, and type "block1" into your console.
You typed a magic word twice. The second time you tried to bypass the magic word filter by using a `1` instead of an `i`. Not only that, but you also changed your name to something related to said word. I can't exactly provide the evidence through Steam.
I can unban you so long as you keep that trash off the servers.
It seems that Suicide Blitz 2 is bugged for versus. Trying to load the map with versus gives me this error in console:
> "Exceeded limit of number of vpk files supported (512)!"
A quick google shows that other people have ran into this issue with Suicide Blitz 2 as well, and many of the comments on the workshop page show that many people are running into issues running the map in versus mode.
21'540 authorizations
4371 connections to reserved servers (#1 - #6)
359 banned connections
9487 connections on vanilla maps
571 votekicks
You typed it 9 times. You were a machine.
I'll go ahead and unban you but you need to chill lmao.
https://v1.steam.hlxgame.cc/groups/publ4d2/announcements/detail/528726587469725697
Triggering the aimbot anti-cheat is incredibly difficult to do on accident. I'm sorry, but I'm going to have to trust the plugin.
Small interactions like this, found in the base vanilla game, are the reasons behind why I keep things and whatnot.
Common/uncommon infected are just named "Infected" entities. So I was searching if a string contained "infected". However, when a bilejar spawns, it creates an entity called "info_goal_infected_chase". This means I was accidentally deleting that.
I've fixed this by making sure to compared my string "infected" to make sure it is an exact match now.
- Redesigned how my plugin handles the maximum allowed common infected on a map. After 90 common infected, it will start deleting common infected. This is to prevent certain older or poorly made maps from filling up the map with 200 - 300 common infected.
- Fixed the plugin accidentally also deleting bile jars on explosion. Common infected should now always be consistent with vanilla behavior with bile jars.
- NFTables firewall has been tweaked a bit for more security and to minimize connection issues. Still need to keep looking into this because there seems to be connection problems for less than 1% of users on the servers.
- The chat welcome message will no longer display in versus mode unless it is a custom campaign. Hopefully this minimizes how many people immediately quit the server before giving it a try due to concerns about it being 'modded'.
- Fixed an exploit that allowed users to pretend to appear as console chat. Thanks to SirPlease for a quick fix.
Seems to be during events where large amount of common infected are spawning (and possibly being deleted because of the cap? Hopefully it is this plugin that is responsible, and not some weird custom campaign.
I've never noticed this. I don't really change anything with bile jars. Maybe my common infected deletion plugin is at fault but that would be odd since vanilla maps shouldn't easily trigger on vanilla maps. I'll try and look into it sometime. Where are you throwing the bile jars, out of bounds?
Hello. What is the problem with the map? I don't make the maps, I just host them on the servers. So not sure what I could do server-side to be able to fix that.