|
| 06 Jan 2016 01:50 AM |
| UnstableScript0 ur a poopy scripter who gives bad advice go jump off of Roblox HQ |
|
|
| Report Abuse |
|
cntkillme
|
  |
| Joined: 07 Apr 2008 |
| Total Posts: 44956 |
|
|
| 06 Jan 2016 02:08 AM |
"Oh, chimmi, brilliant! I was getting ready to post that I had a problem with the code that I wrote, which was pretty much identical to yours, except I didn't have: local x... and it wasn't working. Why did that make the difference?" I'm going to explain it because his answer is not accurate. At the time, the local variable was not yet defined (if you define it to nil, it's still defined) so instead it attempts to get the global variable "x" which you never do set.
Also I don't see how compilation has anything to do with this unstable, nor do I understand how you guy can claim a "function" is a waste of memory considering how much memory we have today. Sure it running in the background is unneeded, but it's not going to cause "lag" unless you're actually doing something, a simple function call, a conditional check, and a return is really nothing. Of course disconnecting the event entirely is a better idea, but if it's memory that is that important, you still have dangling references. |
|
|
| Report Abuse |
|
|
| 06 Jan 2016 02:23 AM |
| Note that most functions, depending on their contents, run in fractions of a millisecond. Fractions. |
|
|
| Report Abuse |
|
| |