[idea]Peer/Self Channel ID

[LB]

It would be great to not only have a Server ID, but another ID per channel. The first person to join a channel would be 0, second 1, third 2, ect. This way, if we wanted to send a message specifically to the first few people to join, instead of making a complex system to detirmine and kep track of the IDs (which I am having to do), we could just use "Select Peer by Channel Peer ID" and then we have exactly the peer we want. EG if several people join and only the first 4 need to be players and the rest observers, it gets complicated trying to sort everything out.

Also these IDs ould not reset or shift like the Server IDs do. If somone with ID3 leaves and then somone joins, they would nto be ID 3, but rather, ID 4, 5, or 6. They select an unused slot. This would mean we would need a "Peer with Channel Peer ID exists" condition.

I would much appriciate it if this were implemented.

[Mathias]

Also these IDs ould not reset or shift like the Server IDs do. If somone with ID3 leaves and then somone joins, they would nto be ID 3, but rather, ID 4, 5, or 6. They select an unused slot. This would mean we would need a "Peer with Channel Peer ID exists" condition.

This is a pretty bad design decision. What if the channel peer ID gets to over the size of a short?

Generally, this issue should be solved with server code, not client code. If you still think solving it with client code is a good idea, you can probably use the order provided by channel peer loops in the Lacewing extension (since these should correspond to the list made in the server, at least with pylacewing).

[LB]

OK, I don't mind that it won't be done. I was just asking

[dragonguy]

A peer can be on multiple channels, how do you refer to which one-self is in?

[LB]

By the currently selected channel, of course...