[04/Aug/2011 06:37:19] <@quadz> hmm... players have been spamming +ia nades for years, so it's not obvious to me there was a specific intent to crash the server.... so all i can think of at the moment is either disable +ia or debug the server code to eliminate the crash potential :/
Whenever someone +ia's a map, I always find myself dropping nades everywhere, and the map gets covered in them. But that was a different game, and it was probably someone else doing it.
the efficient solution in terms of coding is probably creating a flag and a single conditional statement that disables drop entirely in +IA mode when the map begins.
something counting the number of nades on every server cycle could stand the chance of adding a lot of overhead and slowing the server down
Quote from: Whirlingdervish on August 04, 2011, 11:43:17 AMthe efficient solution in terms of coding is probably creating a flag and a single conditional statement that disables drop entirely in +IA mode when the map begins.Back when +ia was added to mymap, and we started seeing the nade droppage, I considered the following tweak:If infinite ammo is enabled, then dropping ammo means: you just drop a single 'nade, and your inventory would go to zero. You pick the nade back up, you get 50 (infinite.)It'd be simple to implement, but what stopped me was the realization I'd have to make this change to every mod... vanilla, xatrix, coop, etc.But, I guess I could start with vanilla.Quote from: Whirlingdervish on August 04, 2011, 11:43:17 AMsomething counting the number of nades on every server cycle could stand the chance of adding a lot of overhead and slowing the server downWhat I'd probably do is add code at the point where the game is freaking out about "ED_Alloc: no free edicts" or "Ran out of configstrings", to call a "garbage collect" routine that would delete the oldest dropped item(s) until it recovered the space it needed. (But... it may be the server would still have to communicate with the mod to obtain this info.)Regards,