What does your User table look like?

[CygnusX]

I typically have:

UserID
UserName
Password
Email
isValidEmail
isBanned
isAdmin
Joined
LastSeen


Does anyone store any other/different information here?

[Chris]

LastIP, RegisterIP
isAdmin is not enough as boolean, you need isHelper/isModerator too

I strongly advise also a separate player table to store game related data. I also endorse denormalization of username field.

[CygnusX]

I keep a separate table for IP's.  Each time a user logs in/out/registers/etc, I log it along with their UserID and a time stamp.

I haven't gotten to a point where I distinguish between helpers, moderators and admins.  I guess none of my games have gotten to that size before.  Either you're an admin and can modify stuff, or you can't.

I of course keep all 'game' related data in separate fields.  But, those tables are so different from game to game, its hard to generalize what to keep in them.

Does anyone have any other general tables?  I usually have:

UserInfo - stores userid, gold, turns, turns used, etc
Fighters - a table for storing playable character information (id, class, exp, attributes, etc)
Market - stores purchasable in-game items, prices, etc
Inventory - what each player has in inventory, qty, and isEquipped if it is equipped
News - stores news events for each player
BattleLog - stories previous battles, their outcome, etc

[Nox]

isValidEmail - imho pointless, you can check upon email change, no need to store ... unless you mean if the player way verified via e-mail (then I'd modify the name a bit)
isAdmin - too specific, why not have Role instead to assign any role you want, not just admin (arguably similar to isBanned, but I guess that could stay)
(I see now you replied to this already, but anyway, the mechanism would be very similar... and it's imho worth to have a role that could take care of the game without breaking it etc.)

Why UserInfo when it's not related to user but to fighter/user's character

Anyway these tables doesn't seem general to me, rather game's design-dependant... even the more general tables would depend on focus of your game etc.
For example I have so far these user_* tables: friends, logins, options, signup, tokens ... but I undoubtably many other people here have totally different ones

[CygnusX]

I've never really liked the table name UserInfo.  I've combined this information into both Users and Fighters before, but I've never been happy doing that.  Its been difficult finding a good place for information such as gold, attack turns, and other 'high level' variables.   

isValidEmail just states that the email has been validated.  isValidatedEmail just seemed too long.

I'm curious what you use logins, signup and tokens tables for.

[Nox]

OK
Nothing interesting, logins is just logging table, signup is your Joined expanded and tokens are some authentication fun, which 'm not sure it's all that needed

[Curtis]

I use the following:

Users table:

id, email, username, password, logins, last_login, language

User_Histories:

user_id,time,history

Roles:
id,name,description

Roles_Users:

user_id,role_id


All the stats are in a characters table which uses character_races, character_classes.

[aerosuidae]

Interesting... do any of you salt your password hashes?  http://en.wikipedia.org/wiki/Salt_(cryptography)

Most of my user tables have some form of:

id
is_ai
is_active
is_verified
created_stamp
updated_stamp
email
nickname
password (hash)
password_salt

All groups/permissions are elsewhere.

And as an example, one of my games materializes a lot of per user aggregate data (calculated from user inventories), each tick:

score
currency
income
expense
experience
prestige
wealth
culture
offense
defense
fortify
demolish