Comments on: Designing Browsergames: a flexible stats system

By: ABDUKRAHMAN

ABDUKRAHMAN — Wed, 14 Oct 2009 08:05:10 +0000

I already diged this my firend.

regards
gibs
______________________________________________
hunting blind | best hockey fights | anti snoring mouthpiece

By: Smitty927

Smitty927 — Sat, 19 Sep 2009 05:51:19 +0000

When dealing with a larger player base, having a separate table structure for stats only is the way to go! The reason for this? Simple really. If it is in the user table, and you are running queries on the stats data on every page load, it would be more demanding on the database.

To eliminate the need for querying 3 tables as Anubis has pointed out, simply create a new view of the 3 tables and then query that view.

By: Anubis

Anubis — Sun, 26 Apr 2009 01:26:19 +0000

It would actually be just as fast to do it this way as in 1 table... for example:

3 tables, users, stats, user_stats (to use the example tables)

I want to grab the stat "Attack" for the user with ID 1.

Attack's ID = 1, User ID = 1. SO

SELECT `user_stats`.`value` FROM `user_stats`,`stats`,`users` WHERE `user_stats`.`userid` = `users`.`id` AND `user_stats`.`statid` = `stats`.`id` WHERE `users`.`id`=1 AND `stats`.`id`=1 LIMIT 1;

And there you have it.

By: Luke

Luke — Sun, 15 Mar 2009 16:12:11 +0000

Chances are when it comes to performance that selecting your stats directly
from your user table will be faster – however, if you ever want to add(or
remove) a stat you will need to make changes directly to your user table.

By: Mark

Mark — Sun, 15 Mar 2009 12:41:50 +0000

What method would be faster? Having the stats in your user table is one query less right?

I tend to select all data from the user in my header using a mysql_fetch_array so I can use things like $user['credits'] or $user['id'] wherever I want. Is this a bad habit? I figured you were gonna use the user data on almost every page anyway.

By: Angela Bradford

Angela Bradford — Tue, 17 Feb 2009 04:51:14 +0000

658087

By: Angela Poole

Angela Poole — Tue, 17 Feb 2009 01:55:16 +0000

556429

By: Cara B Levi

Cara B Levi — Tue, 10 Feb 2009 00:40:36 +0000

great article!, grats for u site

By: Luke

Luke — Fri, 10 Oct 2008 16:02:40 +0000

Hi Scion,

I am not quite sure I understand what the benefit of using the two different types of columns would be – especially in a loosely typed language like Perl or PHP. Whether the user retrieves a number or a word, that value will still be loosely-typed after it’s been retrieved – which means the issue can bite the user either way. How would changing the number of columns in the tables fix that?

By: Scion

Scion — Fri, 10 Oct 2008 15:28:10 +0000

I would caution against mixing types in the same field, If you do sooner or later it WILL come back to bite you.

If you want to have some stats that are numeric and some that are text based there are several possible approaches.

One would be to replace the value field with two fields one numeric that other text…and have a third Enum typed field to indicate which of those contains the value.

Another aproach would be too have two seperate tables one for text based stats and the other for numeric stats.

although im not convinced for the need for text based stats…theyre not really stats…theyre..ummm…something else?