game:BindToClose() is not working?

Help and Feedback Scripting Support
, ,
#28

Actually i think i figured out one possible reason. Try going to the url you set directly and show what you see or tell me what happens. Does it take long to load? Etc… Glitch puts projects to sleep on the free tier

(Edit: terrible grammar fix)

#29

I know they put projects to sleep, that is why i am using game:BindToClose(). game:BindToClose() should give the glitch bot an extra 30 seconds to wake up before the server shuts down.

#30

That is not guaranteed. You say it should but the question is if it does, i have had glitch projects before that have refused to start at all sometimes. Glitch is free, that is an advantage and a disadvantage, you get free hosting but it isnt 100% reliable, that is the cost.

Personally i would never use a free glitch project in a live production game if it had a time limit (like 30 seconds to start) because it is not guaranteed that it will start in time.

What is the purpose of the glitch app? What does it do, anything expensive? The more information available to people the easier this will be to figure out, because i don’t think it has to do with your roblox code.

Edit: If the http request takes more than 30 seconds, roblox will shut the server down whether or not it was completed. If the glitch app doesn’t start in time it will cancel

#31

You should move your wait(30) lower or quite simply, get rid of it and follow saving async. Otherwise, it’s going to run on one player wait 30 seconds, and then forcefully close before it even gets to the next player.

#32

There is only 1 player per server, so that wouldn’t be the problem.

1 Like
#33

It would be because it is inside BindToClose, which automatically terminates the server regardless of if it completes. After 30 seconds the game is closed and all functions will be stopped, so that doesn’t work.

(If you didn’t know, wait is incredibly unreliable!)

#34

The glitch app usually starts within 5-10 seconds.

#35

Instead of relying on print on BindToClose, maybe consider sending a webhook to Discord on the BindToClose? Roblox could be killing the ability for the /devconsole to receive print events on processing a shutdown.

#36

Adding the wait is simply my way of making BindToClose keep the server open for its maximum period (30 seconds).

#37

Read all the replies. They make a request to glitch to rank someone, not to discord.

#38

Well the print gets fired after the player gets kicked and it shows in the dev console so…

#39

But that is unnecessary, there is no reason to keep the server open if the request has completed. The http request yields.

#40

Maybe try to wake up the server (make req to base url not to ranker) every 5 minutes starting from when player joins or something like that to ensure it’s ready to use when they finish.

#41

It’s not possible or favorable to keep waking a glitch bot up as it will self terminate and won’t listen until an actual web browser interacts with it.

It’s highly suggested to either pay for Glitch Pro for 24/7 running of your apps or use an alternative service as Glitch’s Policy on ‘keeping a full-stack app awake on a free plan’ isn’t allowed anymore.

#42

Well I don’t think there are any free alternatives-

#43

What’s the intent of using glitch?

Saving data? Firestore Realtime database works.
Processing data? Google Scripts is free.

#44

You could try https://replit.com. It’s very similar to glitch and allows uptime robots.

#45

I’m using it to rank players in a group after they pass an application in-game.

#46

Are there any tutorials for how to rank players in a group from in-game using repl.it?

#47

I would probably suggest instead of kicking a player, keep the player ingame and have the server ping the glitch app over and over until it is successful, then to kick the player after it has ran.