The whole thing needs a careful hand ;-)

1st off : if your "servers.cfg" seems current (like you just did update from master server in sauerbraten yourself) then you can add the parameter "-o" to omit running the update.

2nd : there is only output for servers where we get an infoline.
so different protocol servers and non-replying servers are omitted completely.

Since you seem to come from down-under (Australia), this might have to do with high pings to other servers.
Try increasing the numbers of scan-loops :
parameter "-s"

So (with good servers.cfg) you could use :

# bin_unix/servermonitor_v011 -o -s123

HTH

Just like it sometimes takes longer for the server to be displayed in the in-game browser so it is here.
Here we set a limit via scan-loops,
this might be more or less variable depending on your connection.

Maximum is "123" ...

Hahaha? How is that funny? So what CC_machine and you were on a server..

hey look at this screenshot! :
http://members.iinet.net.au/~passarello/lolz.JPG

LOLZ someone is on my map!! Its just me!!

Hehe, yeah, well.
BTW - you never answered my email.
I had upped an old version of the linux client (that still clipped off the server-infostring) ... I updated the ZIP the day after your post ... did that or incrementing scan-loops help you out?

Since there's a new release probably coming up soon I'll have to redo this MOD for that protocol again ... so ...

@all:
Is there anything you think should be built into the next version?

Having a problem with that?