Posts: 5,683
Threads: 413
Joined: Aug 2012
Reputation:
0
Did this have to do with .Collided sometimes randomly returning a nil?
Because I remember a few months ago that kept happening and I had to add [lua] if hit and hit.Parent then [/lua] to all my scripts.
Posts: 2,843
Threads: 382
Joined: Jul 2012
Reputation:
0
I'm not sure, but I know if fixed the bug that if you changed a bunch of properties at the same time, some of them wouldn't work.
Posts: 273
Threads: 47
Joined: Apr 2011
''I'm too happy right now.''
Nice to see that your happy. Was it hard to fix the bug?
Posts: 2,843
Threads: 382
Joined: Jul 2012
Reputation:
0
Not really, I had to change a lot of code though.
Posts: 273
Threads: 47
Joined: Apr 2011
Ok. Well, thanks for fixing that bug anyways
Posts: 1,234
Threads: 152
Joined: Apr 2011
Reputation:
0
Did it have to do with any of the bugs I reported :o
Because qwerty said
"Did this have to do with .Collided sometimes randomly returning a nil?"
and that one report I made sends your player to nil after colliding then nothing works no more after you add remove character.
Posts: 5,683
Threads: 413
Joined: Aug 2012
Reputation:
0
No, that's not the same bug -- I mean that say, a Lava script, would malfunction for no apparent reason. It would error at a random moment with something like "attempt to index a non-table" and I figured out it was because .Collided was getting randomly triggered.