[lps]

Originally Posted by Sarabveer No, any code added to GPL software has to be open. HLstatsX wasn't under GPL, that's why game me exists. I'm waiting for this new thing to be finished.

Yea it's going to take more work than I thought, If you're running any SRCDS servers I could really use some live remote logging sources to dump logs to me. If you'd like to PM me I can give you the IP information to send your logs to. I need to make sure this software is compatible with everything HLStatsX was and is up to date.

[psychonic]

Originally Posted by Sarabveer No, any code added to GPL software has to be open. HLstatsX wasn't under GPL, that's why game me exists. I'm waiting for this new thing to be finished.

It is/was. See my earlier post. The GPL only affects binary distribution. If you're not distributing the software (such as when using it privately, with or without changes, including running it on a web server), you cannot be compelled to share your changes. The Affero GPL (AGPL) does explicitly have a clause for that, but the GPL, including v3, does not.

[Phaiz]

What logs exactly are you looking for? I may be able to provide tf2 logs

[lps]

Originally Posted by Phaiz What logs exactly are you looking for? I may be able to provide tf2 logs

TF2 logs work great! From what I understand HLStatsX:CE was not great at TF2.

PM me and I'll send you the IP information.

[Sarabveer]

So this could use the AGPL instead of GPL. I'm just saying, cause Creative Commons is not really a licence targeted for code.

My TF2 and Synergy servers are down cause I couldn't pay for them anymore.

[psychonic]

Originally Posted by Sarabveer So this could use the AGPL instead of GPL. I'm just saying, cause Creative Commons is not really a licence targeted for code.

It depends on his goal. AFAIK, the AGPL does not explicitly prohibit commercial use, but does ensure that all changes are conveyed (assuming that the license is obeyed). So someone could still create a paid hosting service, but all of their changes to the code would be public so anyone could replicate it.

[Mavrick4283]

So let me first say awesome work lps; I have not had the time to work on HLX:CE over the past 2 years as I would have liked to. It is nice to see the community still patch // create new code for this project.

Second let me publicly crush any ideas like "iraqiboy90" had; I am the last dev on this project, I took it over because everyone else was moving along and I did not want to see the project die. So there would be no benefit in me being a dick and trying to steal code as that would kill the project once and for all.

I did PM lps and offer to give him write access to the bitbucket repo if he wanted it; just because it would make it easy for people to find everything.

[lps]

I've almost got the database structure completely re-engineered.

It will remove the need for recording individual events as rows. (This is the major space taker and cause for performance issues).

[Sarabveer]

Yo, Ips, hit me up with a log IP address.
I got TF2MvM server back up.
BTW, my server uses the gameME plugin.

[lps]

Originally Posted by Sarabveer Yo, Ips, hit me up with a log IP address. I got TF2MvM server back up. BTW, my server uses the gameME plugin.

PM Sent. FYI guys, I've just about got the database done.

It has the following DB tables.

• clans_patterns - Holds patterns for clan tag matching
• engines - game engines (for future support of other engines possibly)
• games - game information & per game statistics
• games_actions - action lists
• games_clans - clan list and per clan statistics
• games_maps - map list as per map statistics
• games_maps_heatmap_config - this holds the configuration for heatmap templates
• games_maps_heatmap_data_base - This is a template table, every month will get it's own copy of this for performance / archive / and easy pruning
• games_players - player statistics per game
• games_players_actions - action statistics per player
• games_players_aliases - other names used by players for a game
• games_players_map - map statistics per player
• games_players_maps_weapons - weapon statistics per map per player
• games_players_teams - team statistics per player
• games_players_roles - role statistics per player
• games_players_weapons - weapon statistics per player
• games_ranks - rank listing per game
• games_roles - role statistics per game
• games_servers - server list and per server statistics
• games_servers_chats - chat data per server
• games_servers_players - online players and cached statistics (MEMORY TABLE)
• games_teams - game team list and per team statistics
• games_weapons - list of weapons and per weapon statistics
• players - unique player listing (tracks players across multiple games via steam_id)

Everything is structured such that there will be no reason to ever do full table scans and SUM() the data. That crap is slow. On top of that this new architecture allows for proper foreign keys. All tables have a primary key that is an 'id' column (SMALLINT/INT/BIGINT). Other tables wanting to reference another obect use this ID. No more referencing via 'codes'.

On the backend the script will maintain reverse lookup tables that turn a code into an id. This combined with the timestamps every table and row will have makes it so changes to configurations and options will be done (almost in real time). I haven't created an options table yet.