[dusk]

pawn Code:

ON DUPLICATE KEY UPDATE ammo = %d;

This part is VERY useful for me... Until today I either send a DELETE query to delete all weapon records for a player and then INSERT new data, or send an UPDATE query and then checked for affected rows.

Concerning the table structure, shouldn't the child table have some kind of unique column? I don't know why but I always add it to any table.. I guess it's for editing rows in pMA. Is that bad practice?

And you should really continue these tutorials. I've seen MANY table structures that have over a hundred columns in one main "player" table.