Database will become read-only and break everything

[ethaniccc]

When testing the Anti-Cheat on the test server, for some reason, the Async task crashed with the backtrace:

[13:36:32] [Asynchronous Worker #1 thread/DEBUG]: #0 (): pocketmine\utils\Utils::errorExceptionHandler(integer 2, string[89] SQLite3Stmt::execute(): Unable to execute statement: attempt to write a readonly, string[105] phar:///home/gs-40647/plugins/Mockingbird_dev-51.phar/src/ethaniccc/Mockingbird/, integer 26, array[3])

[13:36:32] [Asynchronous Worker #1 thread/DEBUG]: #1 plugins/Mockingbird_dev-51.phar/src/ethaniccc/Mockingbird/task/NewViolationTask(26): SQLite3Stmt->execute()

[13:36:32] [Asynchronous Worker #1 thread/DEBUG]: #2 src/pocketmine/scheduler/AsyncTask(82): ethaniccc\Mockingbird\task\NewViolationTask->onRun()

[13:36:32] [Asynchronous Worker #1 thread/DEBUG]: #3 (): pocketmine\scheduler\AsyncTask->run()

Have no idea why or when the database suddenly decided to become read-only.

From there, everything breaks from the commands to adding new violations:

[13:36:32] [Server thread/CRITICAL]: ErrorException: "SQLite3::query(): Unable to execute statement: no such table: cheatData" (EXCEPTION) in "plugins/Mockingbird_dev-51.phar/src/ethaniccc/Mockingbird/cheat/Cheat" at line 67

Gotta make a new hack for this too ig :d

[ethaniccc]

If a player is violated too fast, the Async task will crash, but nothing will break and cause the server to crash.

[ethaniccc]

I am now planning on removing the database overall since it's pretty unnecessary, and violations could be stored in a global variable.