Refactored to use OOP

Don't get me wrong but OOP is mistake in MTA, i would avoid it at any cost (especially for such simple script), unless you can't do some code without it.
It's horrible in performance, and simply enabling it in meta would cause increased memory/cpu usage.

Regardless of the perceived efficiency, it is simply much easier for most people to read and write object-oriented code. Which is frankly more important than micro-efficiencies and premature optimizations, especially for a project of this magnitude. Writing it this way means it is more accessible to more people, and much easier for people like me who context-switch a lot.

I doubt the overhead of OOP degrades performance by such a margin that could be reasonably referred to as "horrible". If you have serious concerns about my code using OOP, please raise them here. Otherwise I fear this is off-topic, but feel free to open an issue and we could discuss OOP usage in this repo potentially.

it is simply much easier for most people to read and write object-oriented code

Most of people uses POP, i can tell you that by observing scripting help channels from many years. Also, there is way more scripts written in just POP.
Anyways it's up to you, i just suggested refraining by using it :)

@itslewiswatson There is no clear coding guidelines yet, but we won't accept this PR if it uses OOP.. performance hit can be ~ 20% additional load

@Dutchman101 the PR uses good old-fashioned procedural now