|
| 26 Jul 2016 08:42 AM |
| Several of my scripts have broken, and other people I have spoken to are reporting things breaking as well. |
|
|
| Report Abuse |
|
|
|
| 26 Jul 2016 08:50 AM |
| Doesn't roblox only push updates on Thursday? |
|
|
| Report Abuse |
|
|
| |
|
|
| 26 Jul 2016 08:57 AM |
Upon some investigation, a 'Wait' command is ending the function. The function refuses to run past any 'Wait' commands |
|
|
| Report Abuse |
|
|
|
| 26 Jul 2016 09:00 AM |
| You probably have a thread that's never ending |
|
|
| Report Abuse |
|
|
|
| 26 Jul 2016 09:02 AM |
| The function executed perfectly fine yesterday, but it broke sometime overnight without me even touching it. |
|
|
| Report Abuse |
|
|
|
| 26 Jul 2016 09:03 AM |
| Also as I mentioned other developers I have spoken to have mentioned problems arising last night in their games. |
|
|
| Report Abuse |
|
|
|
| 26 Jul 2016 09:33 AM |
probably bro. :/ wait till they find a way to avoid breaking it. |
|
|
| Report Abuse |
|
|
|
| 26 Jul 2016 09:54 AM |
'The function executed perfectly fine yesterday'
This, and the fact that it's a wait causing it to break, is what makes me feel like it's a thread that's never ending. |
|
|
| Report Abuse |
|
|
Casualist
|
  |
| Joined: 26 Jun 2014 |
| Total Posts: 4443 |
|
|
| 26 Jul 2016 09:56 AM |
We get a thread like this almost daily, 99.999% of the time, it's bad code by the user. Post the code that is breaking w/ relevant output and we can help diagnose the problem. |
|
|
| Report Abuse |
|
|
|
| 26 Jul 2016 10:04 AM |
@Casual It's breaking at a wait function, so I can only assume the task scheduler is resuming a different thread, and that thread never yields (and isn't erroring either, so it doesn't provide feedback that it's a problem)
It's one of those annoying things that'd be really hard to debug. But since it's only happening today it'd be something he changed, which should help find the problem
|
|
|
| Report Abuse |
|
|
Casualist
|
  |
| Joined: 26 Jun 2014 |
| Total Posts: 4443 |
|
|
| 26 Jul 2016 01:33 PM |
Rule number one, never trust the OP. It could be any number of things, you're trusting that OP actually understands the problem (which if it's as you say, wait() would be causing a problem in all scripts, or he has an unyield loop that'd crash the client, in which case it'd be fairly easy to debug). We get these threads fairly often where the Original Poster blames ROBLOX when in reality they are coding with misconceptions which makes them blind to problems.
So until OP posts the offending code snippet(s) so we can identify//verify their problem, I'm going to assume it's probably just OP (notice how the forum isn't flooded with similar threads, which would happen if ROBLOX actually did break something like when Camera:Interpolate() was broken) |
|
|
| Report Abuse |
|
|
|
| 26 Jul 2016 01:45 PM |
'Rule number one, never trust the OP.'
I mean, until given a reason not to we kindof have to go off what the OP says.
As for what you're saying about wait not being a problem, of course it's not. I'm saying the task scheduler probably resumed a thread that isn't ending so that the rest are stopping.
'Several of my scripts have broken' They might be broken, just not running
'Upon some investigation, a 'Wait' command is ending the function.' The wait is yielding the thread, perhaps another thread is holding it all up.
I'm not saying I'm guaranteeing this is the problem, I'm just saying it fits the situation quite well, and we have no good reason to suspect anything else. |
|
|
| Report Abuse |
|
|
|
| 26 Jul 2016 01:49 PM |
Not trying to come across as "Roblox ruined my game!" or anything, was just wandering about a possible cause for what I have experienced.
I have since then found it to be part of a larger problem that I have encountered (talked about in my other recent post). The code affected is also in that post. |
|
|
| Report Abuse |
|
|
Casualist
|
  |
| Joined: 26 Jun 2014 |
| Total Posts: 4443 |
|
|
| 26 Jul 2016 02:04 PM |
@warspy My apologies, I misread your post prior to my last: "But since it's only happening today it'd be something he changed" I read it as: "But since it's only happening today it'd be something changed"
Which I took to mean that you were saying it was ROBLOX; I took issue with that because without seeing his code we can't verify a problem even exists, and if it did we'd being giving up now only to have to deal with it when it comes up later. But since that's not what you were saying, this is all moot. |
|
|
| Report Abuse |
|
|
|
| 26 Jul 2016 02:14 PM |
| Oh.. Nice debate though while it lasted xD |
|
|
| Report Abuse |
|
|