[replay_84]

Does this mean players can't join games during map play or mapchange?

[replay_84]

l4d_vs_ds3

[yzybb]

fixed: Host_Error: Overflow error writing string table baseline Scenes

https://github.com/IA-NanaNana/Sourc...le_error_patch

[cravenge]

Originally Posted by yzybb fixed: Host_Error: Overflow error writing string table baseline Scenes https://github.com/IA-NanaNana/Sourc...le_error_patch

I don't think this is the best approach in tackling this because of issues that will arise when that specific error is ignored. It's there for a reason. What reason? Stability? I have absolutely no idea, only Valve does.

[king kong]

Host_Error: Overflow error writing string table baseline Scenes

This error has never happened to me, so I want to ask if the window server has this problem

[Dragokas]

@yzybb, added L4D1 compatibility. Tomorrow I'll tell if that helped or caused new issue.

[cravenge]

This is just my hot take since I'm on my phone at the moment. By patching out that error message, you're allowing the overflow to happen and it might affect the other string tables after Scenes. I'll give the binaries a quick analyzing when I'm on my laptop again.

[Dragokas]

@cravenge, yes, he is only bypass error message. Shame, still nobody hadn't enough time investment for doing deep reversing. Crashes constantly happens, there are much more lot of bad maps around since. Map slots lock was at least the only temp walkaround atm. Experiments are also complicated by the fact the issue isn't always reproduces on low number of players. Usually 4+ are required. When we did quite a similar BaseWriteLines entire function skip with DHooks back in 2020 with Silvers, that didn't end good.

Originally Posted by replay_84 Does this mean players can't join games during map play or mapchange?

yes (on faulty maps)

[cravenge]

Originally Posted by yzybb fixed: Host_Error: Overflow error writing string table baseline Scenes https://github.com/IA-NanaNana/Sourc...le_error_patch

Yeah, this plug-in won't resolve the issue but instead create new ones (and the fact that the wrong byte is stored when it is unloaded will complicate things even more for the server but that doesn't matter).

My point still stands. Buffer overflow is bound to happen and the string tables after Scenes will be affected. I don't know if this will also open a gate for security exploits in your server but it is likely.

[Dragokas]

l4d2_string_table_error_patch test results: server didn't crash, however, the client who experiences table overflow, cannot join the server (freeze on create table). Somebody tested, not me.

Overall, it's better to use l4d2_string_table_error_patch + Map Slots Locker together atm. Still, a temporary compromise solution.