It doesn't need to survive map changes or server restarts, just for the
duration of the round.
I considered the player index but thought that disconnects would be an
issue.

Where can I get the global ID?

On 7 September 2016 at 04:22, Ben Lubar <ben.lu...@gmail.com> wrote:

> 1..32 is players because 0 is the static part of the map.
>
> On Tue, Sep 6, 2016 at 12:14 PM Björn Stabel <stabel...@gmx.de> wrote:
>
> > Does it need to survive map changes and server restarts?
> > If not, why go with the global ID instead of the userid?
> >
> > If you can only use arrays, you could use the player index (That's
> > 0..32, 1..32 or something like that).
> > But that thing gets re-used, so you can have a bit of a cleanup problem
> > if you don't clean it up on all kinds of (dis)connects.
> >
> > Am 06.09.2016 um 13:47 schrieb Tom Schumann:
> > > What's the best way of storing information against each player from in
> a
> > > plugin? I'd like to store a ready state for each player but I'm not
> sure
> > > how to uniquely index each player - Steam ID would probably be ideal
> but
> > I
> > > don't think this would work in LAN or for bots.
> > > _______________________________________________
> > > To unsubscribe, edit your list preferences, or view the list archives,
> > please visit:
> > > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlcoders
> > >
> > >
> >
> >
> > _______________________________________________
> > To unsubscribe, edit your list preferences, or view the list archives,
> > please visit:
> > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlcoders
> >
> >
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlcoders
>
>
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlcoders

Reply via email to