#I think Debounce but idk
1 messages · Page 1 of 1 (latest)
I want it it only update the point 1 once, then they have to step off before it updates again
Ik it will use Debounce or smth maybe, but Idk how to apply it in context of this code
you are connecting to part.touched multiple times
Do you mind showing me a corrected version of da code
i see that you have scripter 1 but it really seems like you're new
like started 3 days ago
a scripter 1 rank would be able to fix this
yea, I started 3 weeks ago
I have tried so much
i just told them what's wrong with it. to fix it, just simply don't connect to part.touched multiple times.
Well s1 is just beginner in general lol
fr
fair
and it says 1 week - 6 months
- Its kinda hard learning when every damn S2+ Judges u like u aint a beginner
It's really just abt improving urself and being able to recognize that you improved
s1 is slightly past the step of beginner imo
slightly
very slightly.
I can give you a DSS, TS, Prox(with magnitude) script
and much more
Every scripter has different strong points
and i'd wager the dss script you give won't have session locking.
whats session locking 😔

one day imma be s3
it's where you 'lock' the datastore so multiple servers (sessions) don't try to write to the same place at the same time (data race). it's unlikely but it can sometimes happen.
ohh
if you dont account for it you can get lost data
if you at least have retries in your datastore then that is clear s1
Well actually I'm scripter 1 and I know debounce so I think it's pretty safe to say I'm scripter 2 now