Hello Sharks, I am presenting a cool Roblox datastore module called SillyStore1. It is a useful datastore module, and I am willing to help anyone’s questions. I really don’t know what to put here, but I want this part to be long, so I’m just going to keep writing like this. It’s actually pretty fun to just keep writing, you guys should try it sometimes.
Functions and settings = {
Leaderboard,
Debugging,
Clean Code,
Webhooks,
Easily Customizable,
You Can Customize anything,
81 Line Setting Table
}
(When I say you can customize anything, oh lol, I mean everything.)
STILL IN PROGRESS | This is NOT meant to be an advanced datastore module, it uses Roblox’s default datastore and just provides a simple and clean start for people who don’t like over complicated stuff!
Yup. Let’s just send all our player data through your webhook.
I’m confused on why you have embed methods?
This will crash the game. The Player variable will always be truthy.
You should add a kick message so the player knows what happened. They may think it was their fault and never play again. Also, why kick them in the first place?
@ezz_mady You really should fix this if you haven’t. It should be:
repeat
Player:Kick()
task.wait()
until not Player:IsDescendantOf(game) -- Player will always exist while you have a reference to it, even after being destroyed.
woo yipee i think i updated the module or else my work didnt save anyways im too lazy to check (also tell me if im over the top with the amount of features you can edit despite the fact it changes nothing important)
anyways i think it broke i dunno anyways im making a new module so there wont be anything from this silly module also why do peopole thake this so seriously and they are like hmm you cannot do this and its extremely disrespectful and they are so annoying so if you are like that please stop no one likes you
