I'm guessing you used the windows variant, yes?
To be honest that hasn't really been tested much,
I included a simple batch with this release that does the following:
It calls the monitor and then opens a notepad with the stdout.txt - this is where all the output of the monitoring loops went.
For linux it is easy to write a shell script that discards all but the last loop ... your output should have delimiters in it so you can see which loop is which.
Or are you saying they appear multiple times in one loop?!
That would indeed be curious.
I've also noticed that on windows the waiting between loops seems not to work as well as on linux. To be honest it is quite a hack ATM, I'll try and make it more compatible!
No response at all when changing number of scan-loops?!
Even if you ... say ... change to 14 or 10 or something close?

Thanks for the feedback so far ... I'll take some more time to the next releases ServerMonitor for sure ... this was just a quick copy-n-paste number from the old source ... as I said, the waiting loop between scans is really just an awful hack :-P

The application will not launch at all, as long as I have modified the parametres launching it.

I mostly just want to use the server monitor so I can check on my server from my laptop (for some reason it will not run Sauerbraten, something about its Radeon 7500..)

Although I can see MY server, its just a convinience as well. The server monitor could have much more potential as well, a simple GUI could be written to display the data in the stdout.txt and then join servers from there. I was actually looking into programming something like that, but until i can get the server monitor working..

Mmmh. I can't reproduce this error here
The first 4 lines of the BAT should not be edited.
Only the last but one ... that's the true call,
the 3 above it are examples of usage.
The first is just to stop echoing commands to console.
The last is to open the notepad with the stdout.txt file.

I tried 42 as number of loops, it worked fine.

You can also try to call the BAT from a command line yourself,
via START / Run ... / "cmd"
in the window you get (a (faked) DOS prompt) change to the sauerbraten folder and type
use_servermonitor.bat
to run.

You can send me your BAT via email, I'll take a look at it.
Also - good news : I think I've found a way to be more cross platform with the waiting loop!

@GUI : the whole idea was to stay away from GUI stuff :)
Anyway - this would mean forking the development for both Windows & Linux OSes ... something I'm not really willing to take on.
Only solution I'd agree to think about would be a GUI-wrapper written in Python (using boa-constructor).

Since aard implemented his "Debug Message" I've been unable to compile the windows version without commenting out those lines in source :-/
Maybe your issue is somewhow connected to this, but I don't think so.
I can give you the source to the servermonitor if you're interested, it's not very pretty that's why I haven't publicized it yet.

### ScanLoop #84.
2 2 thetowers, SP: 62.149.14.48 Gorynych's_UAIX [10min]
2 4 Death, coopedit: 68.144.13.194 [10min]
2 4 vootdm2, ffa/default: 70.116.9.59 xoltra's 4 cl server in Austin TX USA [7min]
2 2 space, coopedit: 72.9.109.90 AlphaBase [10min]
2 5 jungle, ffa/default: 82.240.106.182 FranceServHosting [1min]
2 1 firstevermap, coopedit: 83.227.77.140 Fred Loves Pie [10min]
20 2 killfactory, DMSP: 203.217.70.22 {sX}Australia [10min]
1470 0 newmap5, coopedit: 200.90.111.211 [10min]

:) works great, I can see my server and all the others, now that I set the scanloops to 84 :D

In fact, I can see more servers now, I don't see half of these servers in the server browser in Sauerbraten..

5/5 now that it works perfectly, exactly as you have said it would. Obviously being down-under means that 12 scanloops aint enough :)

could you please send me a copy too, i could build binaries/debian packages of it for several machines:
gurkan@linuks.mine.nu

thanks

#sauerbraten on quakenet/freenode

Heh, this was for a sauerbraten release over a year old ... you should better look into CSL!

Since I only coded this for my personal benefit and (except for Passa) haven't had any other feedback until now the stuff is pretty much wired into my local setup - that much is true.

But - in general - *Nix users are quick enough to correct the mentioned aspects to get up&running.
I can't publish tar.gz AND zip so I use ZIP, since everybody can unpack that.

Why those scripts shouldn't use temp. files I can't understand; but if you have any improvements I'll gladly incorporate them and give you credit for it.

Since it's all just a quick'n'dirty hack really I haven't released any source for shame, also I think it's a too tempting platform for writing a disturbing (sending maliciously crafted packets) client as to freely grant access to it ;-)