9999x Warning: Waiting packet limit was reached

[Swibble]

When I'm playing BA with my friends after about an hour I start getting the message "Warning: Waiting packet limit was reached for Swibble [packets dropped]" about a trillion times per second and then none of my commands work and I can't message anyone even though I can see units move around and people chatting fine. It's starting to get extremely annoying to have this happen every game.

[zerver]

Press F11 and then select "None". Problem solved!

[Pxtl]

To clarify - you likely have a widget running that is spamming messages. F11 to disable your widgets.

[gajop]

is it possible to show the name of the widget/gadget/ai that is doing that so debugging is easier?

[zerver]

AI: yes (implemented already). Otherwise no, the message comes from the server, and the server has no idea about the origin of the packet.

[Swibble]

Thanks a lot guys.

[MarOne]

"Warning: Waiting packet limit was reached for Player [packets dropped]"

I get like x256 of those per sec, and commands don't respond at all can't even pause the game . A lot of players have experienced this bug .

And I've found out that turning off the all widgets stops the bug form happing (thx zerver ), After filtering one by one , the culprit was Immobile Builder widget . I just turn it off and on once it happens , and it goes away !

[zerver]

Good to know, I will try to fix that widget.

[Forboding Angel]

It's the customformations widget. Grab the one from evo: https://code.google.com/p/evolutionrts/ ... tions2.lua Zerver sexxxed it up so that no moar lolspaem.

[zerver]

Yeah that one was also problematic. But this bug with a continuous spam - even though no orders are issued - is caused by ImmobileBuilder (or at least he says so). I encountered the bug myself once, and noticed how a /luaui reload magically solved it.

[Silentwings]

I haven't experienced this bug myself, but I've heard of others who have and who also traced it to immobile builders.

[Forboding Angel]

Oh, I stand corrected.

[zerver]

I think this should fix it

https://github.com/spring/spring/commit ... 4149b8242e