[pizzahut]

If the timer isn't stopped, it might add the time left before map change, thus it could lead to appending the timeleft multiple times if the hostname is not reset in server.cfg. It's possible that it won't happen but it's better to be on the safe side.

What I changed in 1.2.2 is that I read the hostname just before it is changed the first time, instead of reading it at plugin init.

Both (potential) bugs kinda fall into the same category, that is changing the hostname incorrectly.

I haven't seen either bug happening, the old v1.2.1 worked fine for me.

[Cold Rub]

will install the "modified" version and will see if it happens again.

Note;
Name change happened around 95 hours uptime

[pizzahut]

Originally Posted by Cold Rub Name change happened around 95 hours uptime

I didn't test it for that long, but I'll leave it running on Ancient's TFC servers for a while to test it some more. (Unless he wants it removed of course.)

[pizzahut]

Changed: Using m:s format if timeleft < 1h.
Added leading zeros.

[pizzahut]

I've added additional checks which should prevent that the hostname is set to an empty string, which is probably the cause for it being "Half-Life". This is done by checking the string length of the global variable g_old_hostname.

[pizzahut]

Adding "no time limit" to the host name if the limit is set to zero, also giving credit to the author of the original plugin.