[crossfire] Removal of output-count/output-sync from server

[Mark Wedel]

> Yes, I use it too to control how much garbage scrolls by in my client. Please 
> don't remove that until there is a replacement in the client.
> 
> Gene Alexander

  Ok - followup question this:

  the current implementation in the server has several buffers that it uses to 
store/track different messages.  What this means is if you have messages like:

you hit orc
you hit orc hard
you hit orc hard
you hit orc
you hit orc
...

  They get compressed into something like:
3 times you hit orc
2 times you hit orc hard

  and so on.  Is that extra logic still needed, or is it sufficient to just 
track the last message an print repeat counts?

  I'm thinking that if this is most often just used for things like search locks 
or other repeated checks, just buffering/repeating the last message would be 
sufficient, and is certainly a bit simpler to do.

  The disadvantage is that if there is a bunch of other messages being generated 
as you search for traps (say your suffering from poisoning), that would cause 
the search messages to get broken up, etc.

  Thoughts?