#Everybody gets a role
1 messages · Page 1 of 1 (latest)
use events, they take up less cpu and are much simpler
and there’s an option to send to “others” (everyone but you), or “all” (everyone)
Lmk if you need help with that
JazSe is right so i’ll go more in-depth if you need help
NEVER! only in certain situations
this is not one of them
It works so idc
yo shut up
i hate people like you so much
never wanna better what they know
“it works”
your outdated
keep up with the times
just cause it works don’t mean it’s good
it’s bad
sry
that’s like being REALLY REALLY rich and choosing a free android they sell on the side of the roads for homeless ppl over buying a iphone 15
@molten hornet @agile prairie
The "If it works it works" mindset is something you should try to get out of
When it comes to #1020094893458198578, the goal is to help others, including yourself
The For Each method of adding roles to all players is a bad method because of the amount of CPU it uses, and because of the additional networking heat per player, and AFAIK, RPC's
By sending an event to all players, you are using a drastic amount less networking heat, less CPU heat, and only 1 RPC
The simplest method (The event method) is done with only 3 chips to send a signal from the local player, to a specific player (Like I said below, its only optimal if you are sending to All or Others)
An Event Definition, say "Add Role To Local Player", and if you wanted, you could add a String input onto this as to be able to add any role to any player this event is sent to
An Event Sender to send this event, although its only worth the event hassle if sending to All or Others, else you should just use the player input on Player Add Role for local/room auth/auth/player
An Event Receiver, which, when received, adds the input role to the local player
By doing methods "that work" instead of methods that are actually optimized, you will find yourself running out of chips/CPU/networking very fast
You have a point but Ive rarely ran out of CPU\Network heat when using the for each chip. I understand that there are better methods but I would rather do it the way that I already understand
To make things easier for yourself, do it once, make it a private invention, then whenever you need to do it again, spawn in that invention