Is your feature request related to a problem? Please describe.
It was mentioned in Slack that having the client exit when invalid login credentials are provided during launch would be beneficial.
Even better if it fails when credentials are invalid and if the bot can't start for whatever reason (like bot not in inventory).
Describe the solution you'd like
If RuneMate.jar file is invoked with invalid login credentials, instead of the client program remaining open and displaying "The requested user {USER} could not be found" in the GUI, it should exit with an appropriate warning to the console/shell it was invoked from. This would be beneficial since there's no error/warning sent to stdout that indicates invalid credentials were used.
The RuneMate client could also exit due to other issues with the invocation arguments:
-autostart
Invalid process ID provided (e.g. process DNE / wrong one provided)
Invalid OSRS/RS3 account alias provided (e.g. account DNE)
Invalid bot name (bot name / ID isn't in the inventory)
-world
World may be members-only world but the account is free-to-play
Invalid world (world DNE)
Describe alternatives you've considered
Currently the only alternative I've used is to exit using the GUI.
Additional context
Here's a screenshot of the RuneMate client and the shell not indicating that the credentials were invalid:
Is your feature request related to a problem? Please describe.
It was mentioned in Slack that having the client exit when invalid login credentials are provided during launch would be beneficial.
Even better if it fails when credentials are invalid and if the bot can't start for whatever reason (like bot not in inventory).
Describe the solution you'd like
If
RuneMate.jar
file is invoked with invalid login credentials, instead of the client program remaining open and displaying "The requested user {USER} could not be found
" in the GUI, it should exit with an appropriate warning to the console/shell it was invoked from. This would be beneficial since there's no error/warning sent tostdout
that indicates invalid credentials were used.The RuneMate client could also exit due to other issues with the invocation arguments:
-autostart
-world
Describe alternatives you've considered
Currently the only alternative I've used is to exit using the GUI.
Additional context
Here's a screenshot of the RuneMate client and the shell not indicating that the credentials were invalid: