#I think Debounce but idk

1 messages · Page 1 of 1 (latest)

oak bramble
#

Whats the problem

faint crest
#

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

lone robin
#

you are connecting to part.touched multiple times

faint crest
#

Do you mind showing me a corrected version of da code

oak bramble
#

like started 3 days ago

#

a scripter 1 rank would be able to fix this

faint crest
faint crest
lone robin
faint crest
#

Ohhh

#

Yea i changed it rn, its working

#

ty

hybrid socket
faint crest
#

fr

oak bramble
faint crest
#

and it says 1 week - 6 months

#
  • Its kinda hard learning when every damn S2+ Judges u like u aint a beginner
hybrid socket
lone robin
#

s1 is slightly past the step of beginner imo

faint crest
lone robin
faint crest
#

I can give you a DSS, TS, Prox(with magnitude) script

#

and much more

#

Every scripter has different strong points

lone robin
faint crest
lone robin
hybrid socket
#

Google!

faint crest
#

one day imma be s3

lone robin
#

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.

faint crest
#

ohh

lone robin
#

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

uncut plover
#

Well actually I'm scripter 1 and I know debounce so I think it's pretty safe to say I'm scripter 2 now