Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
5/24/11
#1
  • Fixed an engine bug that was probably responsible for the weird scripting problems that were sometimes occuring, along with some of the MP bugs. If you have a script that used to break randomly, try it again!

I'm too happy right now.
Reply
#2
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.
Reply
#3
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.
Reply
#4
''I'm too happy right now.''

Smile Nice to see that your happy. Was it hard to fix the bug?
Reply
#5
Not really, I had to change a lot of code though.
Reply
#6
Ok. Well, thanks for fixing that bug anyways Big Grin
Reply
#7
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.
[Image: cxAECR.png]
[Image: r8umfc.gif]
Reply
#8
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.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)