Server Query probably limited instances

[norelock]

Describe the bug
Probably Server Query instances is limited

Console log

(node:18848) UnhandledPromiseRejectionWarning: Error: TeamSpeak Server prematurely closed the connection
    at FearBot.closeCallback (C:\Users\Norbert\Desktop\FearBOT-master\node_modules\ts3-nodejs-library\lib\TeamSpeak.js:130:24)
    at Object.onceWrapper (events.js:422:26)
    at FearBot.emit (events.js:327:22)
    at TeamSpeakQuery.<anonymous> (C:\Users\Norbert\Desktop\FearBOT-master\node_modules\ts3-nodejs-library\lib\TeamSpeak.js:58:45)
    at TeamSpeakQuery.emit (events.js:315:20)
    at TeamSpeakQuery.handleClose (C:\Users\Norbert\Desktop\FearBOT-master\node_modules\ts3-nodejs-library\lib\transport\TeamSpeakQuery.js:205:14)
    at ProtocolRAW.emit (events.js:315:20)
    at ProtocolRAW.handleClose (C:\Users\Norbert\Desktop\FearBOT-master\node_modules\ts3-nodejs-library\lib\transport\protocols\raw.js:47:14)    at Socket.emit (events.js:315:20)
    at TCP.<anonymous> (net.js:674:12)
(node:18848) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise 
rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:18848) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Versions used

• TeamSpeak Server Version N/A
• NodeJS Version (check with node -v) N/A
• Library Version N/A

[Multivit4min]

The TeamSpeak Server itself might limit the amount of maximum queries based on ip
teamspeak then mostly just disconnects without any error reason which i could throw as error

since you did not really provide much informations (not even the minimum requirements from the issue template) i can really only guess whats happening

[norelock]

Yeh, that was by limit of max queries

[Multivit4min]

this is a limitation of teamspeaks query, please see #75