Skip to content

Using /quit after a server is stopped doesn't always work #42

@Pokechu22

Description

@Pokechu22

It's a minor thing, but when a server is stopped (EG with the /stop command) and you type /quit afterwards, the client doesn't always close. Instead, it leaves a blank line and prompts for another command to be run. Typing /quit again will close it.


Setup information:

Version message displayed at startup: Console Client for MC 1.7.2 to 1.7.9 - v1.7.3 - By ORelio & Contributors
OS: Microsoft Windows 8.1 Pro, 6.3.9600 Build 9600, x64-based PC

Here's the login text in the client:
Username : TestUser
Password : <******>
You chose to run in offline mode.
Success. (session ID: 0)
Server IP : localhost
Retrieving Server Info...
Server version : pokechu22 (protocol v5).
Translations file loaded.
Version is supported.
Logging in...
Server is in offline mode.
Server was successfully joined.

Here's the server version (it's a local test sever):
CraftBukkit version git-Bukkit-1.7.9-R0.1-10-g8688bd4-b3092jnks (MC: 1.7.9) (Implementing API version 1.7.9-R0.2)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions