#Datastore Bug?
97 messages · Page 1 of 1 (latest)
** You are now Level 3! **
heya
i put print(success) above the if success statement and it doesnt even run it
its so weird
like its bugging or smth
neither the print or warn statements also run
and putting a print statement inside the repeat loop also doesnt run
any print statement
oh yeah, it usually works for me though
because i'm trying to just keep setting it if something goes wrong (with 5 max attempts)
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
hi
h
okay
wait like the entire script?
i cant fit it here
i just changed the until statement to
success or attempt >= 5
and i put print("test") above the pcall
and it prints once only
well i mean that means it works
its a success
but it doesnt print the data saved line
yea because success probably is true
okay
where
?
wait now it doesnt run
its doesnt print
WHAT IS HAPPENING WTWF
what why i thought pcall will only give out either success or not
by the way just to let you know, the problem yesterday is solved
i basically remodeled the data so that it doesnt hold the instance
instead just with key name = value
so if its problem number 2 i should sue roblox's engineers?
lol
i did this
test 1 runs
test 2 doesnt run
so yea something with the set async
oh because i put success and errormsg inside a repeat loop
thus if i create them locally inside the loop
i cant access it outside
for the print data saved and the warn error saving data
i mean shouldnt it techanicallt work the same?
technically
nah mate no difference
i use this aswell for the loading data
and it works just fine
yea it should be
gosh
hmm
theres a bug with set async
i found a guy in the forums that has the same problem as me
wait let me try and restart my roblox studio
so i should use update async?
** You are now Level 4! **
fucking hell
yea but instead of putting the value to set you put in like a function to update it
wait
people said that this doenst work in studio but ingame in works normally
hey man you've been a huge help hahaha its okay if i take it from here
aight let me try this
so if i just return sessionData[playerID] without modifying anything it'd be fine right?
no luck
wait im surfing the forums
it seems like a lot of ppl are having the same problem
DONE
yea basically in studio if you stop the running game the set:async doesnt finish
so basically what i did was i just kicked my player from the command bar
and it worked, it saved because my player left while the server is still running
so if i wanna test i gotta kick my player
then i can shut down the server
HAHAHAHA ITS FINEEE
its something that got overlooked a lot, like so many people posted in the forums the same problem
i just thought to myself why not try to kick the player
and it worked LOL
HAHAHAHA IKRRR
anyways i think i should make like a system where it saves every minute or so
a lot of people are saying that is the way to go
welp
atleast it works not
now*
hey thanks so much by the way HAHAHA
sorry for wasting ur time
HAHAHA
hey is it cool if i added you
on discord
sent
by the way yea what the heck is a metatable
you too
HAHAHAHAHA do u use them
lik ever
like*
not for now
oh
but if u need me to test sure i guess but i rlly gotta sleep now
its 4 am here jesus
i thought to myself 2 hours ago 'man this should be easy, 30 minutes tops'
2 hours later
HAHAHAHAHA
aight man see you, going off now