[Arrow768]

Hi Guys,
atm I am working on a Betting Plugin for the Store Plugin by alongub.

The user should be able to place a bet on what team is going to win.

I have though of the following way to do it:

Create a global array (indexed with the client id), where the team (they have placed the bet on) and the amount of their bet is stored.

If the client disconnects before the round is over, and another client connects, is it possible that the connected client gets the same client ID as the previous client ?

Is there a better way to have a unique index per client ?

[11530]

Originally Posted by Arrow768 If the client disconnects before the round is over, and another client connects, is it possible that the connected client gets the same client ID as the previous client ? Is there a better way to have a unique index per client ?

Yes, there's a good chance the next person who connects will take up that ClientID. Instead, use their UserID which for all intents and purposes should be unique for that server instance until it wraps around at 65535.

[RedSword]

If you want to make it so if a client disconnect and reconnect i.e. 5 minutes later while keeping the same id; you can do an array of last connected (i.e. 100 last connected); or use cookies.

[Dr. Greg House]

Cookies?
What are steamids for?

If you want the credits to be stored after the player leaves anyway you will need a database to store the credit in. Therefore use the steamid for identification. For the on-going bets use a table as well to store them.
Problem solved?

[Arrow768]

The SQL Table is a good idea, I think I am going to do it that way.

[rhelgeby]

It's fine to use client indexes if you do cleanup when a player disconnects. Just remove/reset stuff for that client. A good habit is to reset when a client is connected.