[ThatOneGuy]

I have such a plugin already coded. Works with either mysql or sqlite. Just updated it today to be able to be used as a rank system (so that part is already done), and added natives for other plugins to use it based on minutes played or rank. If using mysql (I know youre not, but others may be), it tracks time both globally, and separates out into servers as well. The structure will give you an idea of what im talking about...



Granted, with mysql, the id and server fields are gone.....so it is just (2) - (7). I do need to make one tweak for sqlite, but that is nothing big. PM me if interested.

Alternately, you might be able to tweak the other plugins suggested here for your needs.

[Puppetmaster]

Originally Posted by ThatOneGuy I have such a plugin already coded. Works with either mysql or sqlite. Just updated it today to be able to be used as a rank system (so that part is already done), and added natives for other plugins to use it based on minutes played or rank. If using mysql (I know youre not, but others may be), it tracks time both globally, and separates out into servers as well. The structure will give you an idea of what im talking about... Granted, with mysql, the id and server fields are gone.....so it is just (2) - (7). I do need to make one tweak for sqlite, but that is nothing big. PM me if interested. Alternately, you might be able to tweak the other plugins suggested here for your needs.

Thats really cool, by what method do other plugins access its API? Im guessing directly from the DB or via a series of convars?

[ThatOneGuy]

Originally Posted by Puppetmaster Thats really cool, by what method do other plugins access its API? Im guessing directly from the DB or via a series of convars?

Natives coded into the plugin.

Spoiler

/**
 * Return minutes logged for client under global play time.
 *
 * @param	client		Client index
 * @return				Integer number of minutes logged for client under global play time, or -1 if invalid client.
 */
native tpr_GlobalPlayTime(client);

/**
 * Return minutes logged for client under global spec time.
 *
 * @param	client		Client index
 * @return				Integer number of minutes logged for client under global spec time, or -1 if invalid client.
 */
native tpr_GlobalSpecTime(client);

/**
 * Return minutes logged for client under server play time.
 *
 * @param	client		Client index
 * @return				Integer number of minutes logged for client under server play time, or -1 if invalid client.
 */
native tpr_ServerPlayTime(client);

/**
 * Return minutes logged for client under server spec time.
 *
 * @param	client		Client index
 * @return				Integer number of minutes logged for client under server spec time, or -1 if invalid client.
 */
native tpr_ServerSpecTime(client);

/**
 * Return relative rank for global play time of client.
 *
 * @param	client		Client index
 * @return				Integer rank of client, or -1 if invalid client.
 */
native tpr_GlobalPlayRank(client);

/**
 * Return relative rank for global spec time of client.
 *
 * @param	client		Client index
 * @return				Integer rank of client, or -1 if invalid client.
 */
native tpr_GlobalSpecRank(client);

/**
 * Return relative rank for server play time of client.
 *
 * @param	client		Client index
 * @return				Integer rank of client, or -1 if invalid client.
 */
native tpr_ServerPlayRank(client);

/**
 * Return relative rank for server spec time of client.
 *
 * @param	client		Client index
 * @return				Integer rank of client, or -1 if invalid client.
 */
native tpr_ServerSpecRank(client);

[Lannister]

So this is actually possible?

[friagram]

Originally Posted by Puppetmaster I think a database would be the way to go, since you want to track a potentially large number of players a database would both allow you to store large numbers and efficiently run queries on the data. For instance calculating the top 10 players without a database could be quite hard as you would have to iterate over a list using something like a heap. With a database you would simply make a query ordered by biggest first with a limit of 10 which is quite efficient.

That db has hundreds of thousands of unique steam ids. If you were to use sqlite, you may experience some problems like server stalls and such. I'v not use sqlite for a while, but back in the day it got really congested with clientprefs, and got corrupt sometimes.

[ThatOneGuy]

Originally Posted by friagram That db has hundreds of thousands of unique steam ids. If you were to use sqlite, you may experience some problems like server stalls and such. I'v not use sqlite for a while, but back in the day it got really congested with clientprefs, and got corrupt sometimes.

I'd agree with friagram that you really should look into getting a website. They arent expensive, and using sqlite is gonna be heavy on your server....but yea...the possibility is there if you need it. Alternately, you could use gameme or another stats plugin that hosts it from their own website....i think they also track time...not positive though.

[Lannister]

But i wonder, how's possible for plugins like SoDStats to track everyones kills/death, time, headshots and everything without "hurting" the server? sorry if it sounds dumb!

And thanks for your help guys i appreciate it.

[Puppetmaster]

Originally Posted by friagram That db has hundreds of thousands of unique steam ids. If you were to use sqlite, you may experience some problems like server stalls and such. I'v not use sqlite for a while, but back in the day it got really congested with clientprefs, and got corrupt sometimes.

You could always add purge code that cleans it if say the players have not logged into the server for two weeks or have not spent x amount of time on in the past month? That would clean up a ton of the useless player data and keep everything running smoothly.

[Lannister]

Seems like you guys are having great ideas, i'm glad !

[PlayBoy31]

I have done a rank plugins for my servers, i can implement the rank with time played