Sometimes the Scanner associated with a TelnetStreamCommunicator will fail to read the next line and throw an exception (no newline found). This happens due to forced disconnects without sending input, or sometimes from MUD clients that use automatic names and passwords.
Sometimes the Scanner associated with a TelnetStreamCommunicator will fail to read the next line and throw an exception (no newline found). This happens due to forced disconnects without sending input, or sometimes from MUD clients that use automatic names and passwords.