How about some more detailed Player/server stats? Options

[harlekin]

How about some more detailed Player/server stats?

We would need:
Script that sends needed information to sl.
Account to verify which server sends information
Maybe the "big 3 or 5" alive server to participate. (should be more then enough to attract other server to join)

We would get:
Much more detailed stats
No need for clans to setup their own crappy VSP or whatever stats.
More hits on splatterladder and a real advantage to trackbase
Stats based on guid, not a simple name based system
maybe more donations

Sure the sended information could be manipulated but the current xp based ranking ain't flawless as well.
Comparsion between serverstatus/xp and sended information could verify data.
Maybe some small fee for the service i could imagine. it's a lot what they get, compared to a only single server based stat system....

[Wolf Enstein]

A very interesting idea, Harlekin, I'll mention it to Schnoog .

[macbeth]

"Maybe the "big 3 or 5" alive server to participate. (should be more then enough to attract other server to join)"
and what about the other servers ?

[harlekin]

"Maybe the "big 3 or 5" alive server to participate. (should be more then enough to attract other server to join)"
and what about the other servers ?

As I said should be enough to attract other and hopefully have more willing to join the system.

This post has been edited by harlekin: Jan 12 2019, 07:28 PM

[schnoog]

Hi harlekin,

I'm open to such things, as long as I'm not the (only) responsible coder.

Technically:
Data-collection:
Keeping the SL table structure untouched. The new data should refer to the server table (where the IP, Server-name, Raw-Name and much more is stored).
The ETServer-Skript grabs the information and sends the data over a simple http(s)-(post)-request to a callback-URI which parses the information into a table(s).

The processing of the data is difficult compared to the collection.

The whole SL is based on php5 (which is EOL and some security fixed were applied manually and still uses such ugly things like register globals [depreated, therefore a wrapper for it], the Virtual Machine is running wheezy, also EOL. A change to Jessie and php7 would mean a lot of work.)
So a php5 compatible codebase would be great

Some ideas:
-An open git repository for development
-A database structure for the new data (with one "foreign" ID for the server) [would create a dump of the server table with several server to link]
-A subdomain for testing, where the current git master can be checked out for live testing.