Closed Winston2108 closed 4 years ago
Fixed in the develop branch.
@madrabbit711 I'm keeping a table of {message=lastSentTime}
and then I just check against that. If there's no lastSentTime or it's more than 5 seconds ago, we send the message.
Seems the easiest overall, and apparently indexing a table by string is fairly fast (it's a hashtable when indexed by non-integers).
We remove duplicate hit messages, but if a unit is using mixed cannon ammo (for example AP and HE) you can get spammed with AP,HE,AP,HE,AP,HE... messages.
Enhance the hit message code to store all repeat messages for an amount of time, or at least the last N (where N might need to be as small as 2).