Lua Challenge: the Catastrophes plugin

[DiamondToaster]

Aww, I've got three fun ones that I was gonna submit.

EDIT: I did find the problem, I just can't seem to find where it went wrong though.

EDIT #2: I DID IT. The answer hit me like a brick. The cWorld:DoWithEntityByID() was returning nil references, thus Entity:GetPosY() would return nil and occasionally crash the server if an operation was done on it. I fixed it using cWorld:DoWithEntityInBox() instead. Whoever came up with that idea, you are a lifesaver.

[xoft]

Failure. Just... so much failure!

Gentlemen, be ashamed of yourselves. So many of you promised something and in the end we get two entries?!?

[xoft]

Alright, I decided to give you one more week. After all, what software project doesn't get delayed? But this is it, after a week, no more time extensions. If you need more time, grab a Tardis or a DeLorean or whatever and travel back in time.

[xoft]

And technically we still only have a single entry, the other two would get disqualified for not following the rules.

[DiamondToaster]

I retracted my own entry since I originally wanted to get something in by the deadline, but I see that it's been extended. I'll polish it up a bit more then actually enter.

[NiLSPACE]

A reminder that there are only 3 days left.

[xoft]

Half an hour left, time to start typing those marketing materials

[xoft]

You know what? Why do I even bother?

[NiLSPACE]

I'm honestly really disapointed. We hear people saying Lua is too slow for years, and now there finally is a chance to show them otherwise, but barely anyone actually takes it even though many said they will. Xoft even had 2 prizes for the winners. Not to mention that he reserved some time for this. As I said, I'm really disapointed.

[tonibm19]

I understand your disappointment. And I'm sorry for xoft, he prepared this so well, as the above said.
In my defense, I will say that my plugin contains bugs and is incomplete, and I had real-life stuff and steam sales, lets be honest.
But yeah, I could have done more probably