Consumable Queue/Wait

[smoky fern]

Is their a way to make a consumable queue so that multiple people dont go up at one time, the point is to defuse a bomb and its 1 person from the game goes up, but a consumable lets you go up next, but if someones bought it at the same time, it goes into a queue?

[umbral lodge]

Use a player list, and every time a player uses the consumable, it adds the player to the list. Naturally it puts them at the bottom, which we can use. When it sends someone up, it gets the player at the top of the list, sends them flying, and removes them from the queue.

[smoky fern]

cheers

[umbral lodge]

No prob

[opaque crane]

@umbral lodge @smoky fern remember that lists are not synced, and you will need to manually sync them

[smoky fern]

wym?

[opaque crane]

Lists are not synced, meaning if I add a player to my list, you wont see any changes

i will need to send you (or Everyone/All) my list whenever I change it

[smoky fern]

i dont get it

[umbral lodge]

Or just have the circuits run for only room auth, using events 🤯

[opaque crane]

And then the room auth leaves and your data vanishes 🤯

[umbral lodge]

Player Leaving: if is room auth: event send to all players: save data: delay 2 secs: start at new room auth 🤯

[opaque crane]

You are, however, somewhat right

Personally, I think you should send list syncing events to the room authority, something like "UpdateList", or "ListAddItem"
The room authority adds these to their own list, and then sends their list to everyone

Doing this carefully to avoid overheating networking will give you a synced list that never desyncs, but will run into an issue if the room authority stops responding to requests (because for example, they turned their headsets off)

[opaque crane]

Player leaving doesnt have to fire

Player leaving only fires when the player leaves through natural methods, aka joining a new room
This event will not and cannot fire if the player leaves by for example, crashing, or closing their client

This is because "Player Leaving" is essentially sent to everyone when the local player says "Hey, I'm leaving the game now"
The local player's client wont know when they are going to crash/turn off their headset

[umbral lodge]

True

We could also use delimiters and variables to create lists that sync, and decode when used

[opaque crane]

I almost always stick to synced string variables for storing synced "list" data lol

[umbral lodge]

Stuff like (Cryptic,Zer0,JJ). Would be a string variable would be decoded into ((Cryptic)(Zer0)(JJ))

[opaque crane]

Display names can only be 15 characters long

I would "Make" everyones display names 15 characters long using some funny substring/concat stuff, then put them into a String Variable separated by dividers, etc CrypticCreator /StatusZer0

I can use math to both get and set a specific substring from that "list", and use String Trim to remove extra spaces

[umbral lodge]

This turned from a help discussion to a synced list tutorial

[smoky fern]

wish i knew wtf yall r talking about