TNManager.players does not include self?

[Voxel]

Hi,

From what I can see TNManager.players does not include the client. I want to use TNPlayer for scores etc and I was just going to use the data in TNManager.players to populate the scoreboard during play. The client is also a player so I am confused. Do I just fill in the gap with TNManager.player.score for example? Or is there another way that I am unaware of?

Also is there a built in way to notify other players of a change in any of my custom data in the Player Class such as a change in score, or should I just send the details using tno.Send to the other clients?

Thanks.

[ArenMook]

You should use tno.Send. And your assumption is correct -- player list only includes other players. It's basically for "who else is in this channel?"

[riomoko]

There is a way to receive the complete list of the player including client?

Or an example for managing score?

[ArenMook]

Your player will never be a part of the TNManager.players list, but everyone else will be. If you want to include yourself in there, simply consider TNManager.player as a part of the list.

[riomoko]

I see, there are some elegant example how manage score, or manage object characteristics for example how assign a material from an array to cars in a race game without duplicate material?

[ArenMook]

Send the index of that material. You won't be able to sell a reference across the network as each client will have a completely different and unrelated value.

[riomoko]

I try to explain better:
In a gamemanager object the scene not created I have an array of x material and another empty int array where store the client id to the related material
I create a tnet object .if I'm the owner I choose random a material (and checking on the client array is not already taken), the put  the owner player id in the client array.
now I send the index of the material and the index of the client they assign material and fill the client array with the related client id so everybody in the net have the same relation material-> cliend id

and it should work

the question is: how avoid two client choosing the same material at the same time?

[ArenMook]

Don't let each client do it. Route everything through the channel's host. Instead of simply calling an RFC like tno.Send("SetMaterial", Target.All, ...), do a request instead: tno.Send("RequestSetMaterial", Target.Host, ...). Inside this RequestSetMaterial, which is guaranteed to be executed only on one client, check -- is the material already taken by someone else? If so, send some RFC that says "choice invalid". Otherwise proceed to tno.Send("SetMaterial", Target.All, ...).

[riomoko]

Thanks Resolved, now host assign material under a client request