Lots of databases!

[zythion]

Ok, so I'm designing a remake of an online text browser game I used to play..

I figured, now that I've got the main basis of the site layed out, that it would be a good idea to make a start on the database design..

I've got one set up already, for people that register.. The fields are: ID, Permissions, email, login, password, Empire name, race & referrer.

 

A quick run down of the game, is that you build buildings, to make money/resources (The resources being Money, Food, People, Orium & Argentum..), to buy military,  to buy / steal planets (from attacking). You also have research that can increase fertility, gain resources quicker, etc..

 

To get a better overview (or if you're just interested), it would be a good idea to browse the guide taken from the wayback machine.. (the game stopped running back in 2006)

 

EDIT IN: Saying that, here's a picture of the main page once you've logged in.. Everything in that table will end up in a database. I just can't seem to think of the best way to go about it..

 

I was wondering if anyone would give me any tips on the database design.. How should I make it??

Thanks

[fugix]

store as much information about a unique user as you can, than whens things change user an updater query...will cut down on mysql server response time

[zythion]

Yeah, but all in one table ? My friend said his game (which is sort of the same kind of thing) has around 10 different tables.. He said it should be more, but it's been designed incorrectly.. That's why I'm asking, because his game has less content than the one I'm making, therefore I guess I'd have alot more?