Hello, so I cant really use the template for this since it consists about several suggestions and bugs not just one

So here are a few notes and suggestions about the new client:
1. When you close the client or when you open it with a batch file and close the client or if it doesnt open properly (For example you start the client with an outdated jar with a batch file, the client wont start but the java.exe will still remain as a background process) its not terminating the java.exe process and it will just run in the background forever using 0% CPU usage but the same amount of memory as a properly running client so I have to manually kill them with task manager.
2. Looks like the new client doesnt save settings, I ticked dismiss randoms closed the client then reopened and the option is unticked again.
3. It would be nice if you could launch the client without that sidebar thing and that would be the default, I run my bots side by side and its annoying I have to close that every time I open/reopen a bot, its just an extra unnecessary click.
4. When you click the play button would be better if it would bring up a script selector window rather than opening the sidebar, once again if you run bots side by side you have to constantly move them around since the bar might open out of your screen and stuff.
5. Sometimes scripts are not showing up and you have to press the refresh button.
6. Separating the mouse and keyboard input button in my opinion was an unnecessary move and it was good as it was before, I would replace the keyboard input button with a script restarter button which would load the last script that was running with args and breaks, this a really good QOL improvement if you manually manage your bots or in just general.
7. The IP could show also the port.
8. Login handler is still not that good, sometimes when a script stops and the account logs out and then I try to restart a script its just doesnt log in, login handler appears but nothing happens and then I have to restart the client for that.
9. Another thing to mention is for some reason the client will use alot of ram overtime, like it will start at at like 300-400mb and it will go up to 1gb+ after 24+ hours, and yes I am using the -Xmx512mb command and I have music turned off in my bots.

Edited November 14, 20205 yr by XauGold

1. That's odd, I'll see if there is something that can be done about it.

2. Correct those don't save at the moment, but I've added it on my todo list to add this.

3. I could make the open/close of the sidebar save too and remember that for the next boot.

4. I'll see if it's possible to add an -nosidebar cli argument that will require popups again for these kinds of things.

5. Never seen that before but I can see if there are loading issues when the servers are down or anything.

6. I could look into adding some kind of restart previous setup button.

7. Where?

8. That's odd, not happening for me. I can do some testing but idk.

9. Are you using the webwalker? currently this is using a lot of memory.

22 hours ago, Patrick said:

1. That's odd, I'll see if there is something that can be done about it.

2. Correct those don't save at the moment, but I've added it on my todo list to add this.

3. I could make the open/close of the sidebar save too and remember that for the next boot.

4. I'll see if it's possible to add an -nosidebar cli argument that will require popups again for these kinds of things.

5. Never seen that before but I can see if there are loading issues when the servers are down or anything.

6. I could look into adding some kind of restart previous setup button.

7. Where?

8. That's odd, not happening for me. I can do some testing but idk.

9. Are you using the webwalker? currently this is using a lot of memory.

3. Okay, that would be good so people have the option to have it both ways.

4. Yes that would be great, it was better how it was before that it opened a script selector window so you never had to move anything around if you run them side by side.

6. Yes this is really a good feature and just makes things easier and faster.

7. So I meant the clients titlebar, it could show it like IP:Port.

8. Yeah im not sure why is this happening it might be the scripts fault, 95% of the time I only use 1 script so not really sure.

9. Whatever is on by default thats what im using, im not sure what is the default.

Thanks for listening, honestly I expected these suggestions to be turned down and criticized but its really good when devs listen 😄

 

@Patrick So here is a ghost process or whatever is called 

https://i.gyazo.com/586a93db6feb18fe83530bccd0a8c781.png

Also as you can see from this picture the clients will use alot of ram overtime, the 1gb+ ones are 2-3 day old clients.

Edited November 15, 20205 yr by XauGold

It's quite the list of things so I'll have to see when I can get these done, but they are on the todo list

On 11/14/2020 at 9:03 PM, XauGold said:

7. So I meant the clients titlebar, it could show it like IP:Port.

I just checked and it's already doing this for me... make sure you select the Proxy option 😛

On 11/22/2020 at 5:48 PM, Patrick said:

It's quite the list of things so I'll have to see when I can get these done, but they are on the todo list

I just checked and it's already doing this for me... make sure you select the Proxy option 😛

Hey, im not sure whats the progress atm but can you atleast fix the login handler issue?
Had this login bug happening again and its somewhat frequent, one time it even happened while a script was running with breaks, it just couldnt log back in I guess becuase the login handler didnt get triggered or something.

Edited December 15, 20205 yr by XauGold

On 12/15/2020 at 8:22 PM, XauGold said:

Hey, im not sure whats the progress atm but can you atleast fix the login handler issue?
Had this login bug happening again and its somewhat frequent, one time it even happened while a script was running with breaks, it just couldnt log back in I guess becuase the login handler didnt get triggered or something.

I believe this is fixed? Noone has reported it so far.