There are about few tags. Each "m1, m2, m3,..." correspond to a tag. Curr_tag is the number of the actual tag in game. Unique id is the steam ID.
It would help if you actually gave us some context in which to put this. You posted a dozen functions but failed to provide any order in which they are supposed to be called. What are you hooking to? Show us your code for PlayerAuthed / PlayerConnect / etc...
[QUOTE=Loucouss;29544456]There are about few tags. Each "m1, m2, m3,..." correspond to a tag. Curr_tag is the number of the actual tag in game. Unique id is the steam ID.[/QUOTE]
Not OP's problem, but you're doing it horribly wrong.
Instead of having a player_trail table with a shitton of columns, have a table with the following columns: player_id, trail_id. Then when a player has a trail "lololo", create a new row with player_id corresponding to your playerid, and trail_id set to "lololo" or another unique identifier for that trail. Then, when you want to list all the trails available to a player, just "SELECT trail_id FROM sometable WHERE player_id = '...';"... When you want to add a trail available to a player, "INSERT INTO sometable (player_id, trail_id) VALUES ('...', 'lolololo');", and when you want to make a trail not available for the player, "DELETE FROM sometable WHERE player_id = '...';".
Sorry, you need to Log In to post a reply to this thread.