Large response is split into multiple "response" events #47
Description
*Using this package for Minecraft
*Many mods installed on Minecraft, like WorldEdit
*Sending "/say hi" via RCON
*Minecraft responded perfectly, "[rcon] hi"
*Feeling satisified to try more commands
*Sending "/help"via RCON
*So long was the response that the MC server split it into two and more packets, creating two events // rcon.on("response", ()=>{...})
The two events ruined the following event-driven procedure, where I used a queue to determine which client is connecting to the rcon module and only ONE of the event was expected.
Hope there can be a flag to see if the package is finished, and I can use that event to drive following services.