Prototype G Posted December 6, 2019 Share Posted December 6, 2019 12 minutes ago, Ampleram said: Yeah mine finally started to work. Kept crashing after saying downloading client so thought it was down cus of the update is jagex the problem with their servers. Quote Link to comment
Developer Patrick Posted December 6, 2019 Author Developer Share Posted December 6, 2019 16 hours ago, Prototype G said: I found the error of the consumption, you changed some APIs and you broke some scripts :), when the script stops working correctly it begins to consume the processor ... for which we do not have support in the scripts, we fk up. API's didn't change and 1% cpu usage per client is insanely low Quote Link to comment
Prototype G Posted December 6, 2019 Share Posted December 6, 2019 12 minutes ago, Patrick said: API's didn't change and 1% cpu usage per client is insanely low and that you changed that all my scripts were broken ... Quote Link to comment
Prototype G Posted December 6, 2019 Share Posted December 6, 2019 by the way, the proxy sockets error only occurs with osbot. Advertising other bots isn't allowed., runelite, poopbot don't have that problem. it is too annoying to open many accounts with this error ... Quote Link to comment
Prototype G Posted December 6, 2019 Share Posted December 6, 2019 35 minutes ago, Patrick said: API's didn't change and 1% cpu usage per client is insanely low The problem is not the scripts, I just realized that the consumption occurs when the character is stopped, the game is logged off and when you enter the script is stuck. and begins to consume more the processor, bringing it to 100%. Some time ago something similar happened with the osbot and an update you did. Quote Link to comment
Prototype G Posted December 6, 2019 Share Posted December 6, 2019 4 minutes ago, Malcolm said: This sounds like an NPE. Are you running the script and then the script gets "stuck" and eventually gets logged out? Yes, and when the script enters again it starts to consume a lot of processor but still works well. Just now, Prototype G said: Yes, and when the script enters again it starts to consume a lot of processor but still works well. It happens with all my scripts ... Quote Link to comment
Prototype G Posted December 6, 2019 Share Posted December 6, 2019 @Malcolm please help . If the osbot does not work again I will have to leave. and I really live from this. Quote Link to comment
Prototype G Posted December 6, 2019 Share Posted December 6, 2019 Just now, Malcolm said: @Prototype G try opening the logger and when it throws the error post it here. the problem is that there is no such error .. simply when the character stands still that is disconnected by "afk", when reconnecting it consumes a lot of processor but the script continues to work perfect. The problem is the update of the osbot. Not the scripts. When patrick released version 0.62 it broke everything. Quote Link to comment
Prototype G Posted December 6, 2019 Share Posted December 6, 2019 3 minutes ago, Malcolm said: but why is the script just stopping like that? It is designed like this ............. the script will pick up fish near GE and when the necessary time passes without the account moving it disconnects and reconnects ... Quote Link to comment
Prototype G Posted December 6, 2019 Share Posted December 6, 2019 They are not helping me much when the mistake was to update the osbot at all, if everything was perfect. Can you just give me version 0.60? Quote Link to comment
Prototype G Posted December 6, 2019 Share Posted December 6, 2019 it's time to migrate to another script executor. Thanks for the help Quote Link to comment
Naked Posted December 6, 2019 Share Posted December 6, 2019 11 minutes ago, Prototype G said: it's time to migrate to another script executor. Thanks for the help You're complaining about OSBot when it's very obviously the fault of your scripts. Stop trying to blame OSBot. You're not going to get 2.5.60. It was probably a game update that broke it. You going to go to the client that went down for over 2 weeks because they can't write a decent backend, or the one that's detected and has broken API methods? Just get someone to make you a new script or make one yourself. There's plenty of open source code. Quote Link to comment
Prototype G Posted December 6, 2019 Share Posted December 6, 2019 4 minutes ago, Naked said: You're complaining about OSBot when it's very obviously the fault of your scripts. Stop trying to blame OSBot. You're not going to get 2.5.60. It was probably a game update that broke it. You going to go to the client that went down for over 2 weeks because they can't write a decent backend, or the one that's detected and has broken API methods? Just get someone to make you a new script or make one yourself. There's plenty of open source code. It's not the first time this happens with Osbot and its updates Just now, Prototype G said: It's not the first time this happens with Osbot and its updates and I repeat, I doubt the script is. Maybe it could be my java version, since some time ago I had a problem with consumption when I was loading the account in the "download and applying" part consumed the entire processor and changed the java version and it was fixed. but it's all because they update the osbot and you have to adapt to it. Quote Link to comment
Naked Posted December 6, 2019 Share Posted December 6, 2019 16 minutes ago, Prototype G said: It's not the first time this happens with Osbot and its updates and I repeat, I doubt the script is. Maybe it could be my java version, since some time ago I had a problem with consumption when I was loading the account in the "download and applying" part consumed the entire processor and changed the java version and it was fixed. but it's all because they update the osbot and you have to adapt to it. Get the script dev to fix the script or get a new script made. It's not the API. It's something on your end. Stop blaming Patrick. Quote Link to comment
Prototype G Posted December 6, 2019 Share Posted December 6, 2019 5 minutes ago, Naked said: Get the script dev to fix the script or get a new script made. It's not the API. It's something on your end. Stop blaming Patrick. Ok brother, just stop crying. I will try to solve it on my own, I have to become a programmer now xD 1 Quote Link to comment
