Additional rules

[tChr]

10 11 and 12 are additions to the ruels page.

The info in 11 and 12 is good to have there, however, I suggest to put it into a separate. "Server info" or whatever page, as these are more of practical info, than they are rules Additionally this is info you want to access more often, and it can be a lil hard to find it in the rulese page.

Actually, It could go into a FAQ

Edit:
It could be cool to use server info direclty. in a separate "servers" page. Printing the users and server stats, as I see some servers do, along with the server status if any server goes offline temporarly for some reason.

[GreEn`mArine]

well, I agree that it's a good idea to have these three points ina FAQ page that is generally about the servers (I dunno how I could integrate a special serverlist featuring only defined servers, KadaverJack would have to code a special *.pl script for that I think, this could be then included into the PHP file, however he would have to install Qstat etc. on the planetnexuiz.com server as I don't like it to have quite some serverquerying stuff being on my PN.de server when it could also be available there) and about the info how to use them. however I'm not sure when I'm going to do that separated page ^^

[tChr]

well, I agree that it's a good idea to have these three points ina FAQ page that is generally about the servers (I dunno how I could integrate a special serverlist featuring only defined servers, KadaverJack would have to code a special *.pl script for that I think, this could be then included into the PHP file, however he would have to install Qstat etc. on the planetnexuiz.com server as I don't like it to have quite some serverquerying stuff being on my PN.de server when it could also be available there) and about the info how to use them. however I'm not sure when I'm going to do that separated page ^^

If someone send me the .pl file I'll rewrite it in PHP.

[KadaverJack]

If someone send me the .pl file I'll rewrite it in PHP.

Bah! PHP sucks
Perl ftw!
And perl has an advantage in this case: it easier to run as cronjob.
Nobody needs more than 1 update per minute for that list, so it makes more sense to generate the list via cronjob and not every time the page is displayed (which could puts more load than necessary on the servers imho).

[tChr]

If someone send me the .pl file I'll rewrite it in PHP.

Bah! PHP sucks
Perl ftw!

Yeah.. and mixing languages in a project rule

And perl has an advantage in this case: it easier to run as cronjob.

eh.. no

Nobody needs more than 1 update per minute for that list, so it makes more sense to generate the list via cronjob and not every time the page is displayed (which could puts more load than necessary on the servers imho).

That I agree with. I dont disagree that perl is good for this kind of stuff either. php has as much on CMDline to do as perl has in web pages. That is, none at all.

[Willis]

Nobody needs more than 1 update per minute for that list, so it makes more sense to generate the list via cronjob and not every time the page is displayed (which could puts more load than necessary on the servers imho).

Keep in mind if its on a cronjob at every minute, thats 1440 activations a day. So it is only the effective solution when you have more than 1440 views in a day. However, being as it can run on a cron, it decreases web page load times, not having to wait for a timeout if a server is offline (though proper php code could handle this fairly well also).