Ericthecmh

Nice release. Really good job on cutting down that CPU usage. Comparable to OSBot 1, actually even better than OSBot 1's CPU usage. Very impressed

Shred it. Then I know no one can take advantage. Whoever lost it probably already disabled the number anyways.

In Laz's timezone, there are still a few hours left. We'll have to wait and see. However: 1) It's true that OSBot 2 has incredible high CPU usage. It takes more than 3 times the processing on my laptop compared to OSBot 1. 2) OSBot 2 is going to require new scripts... which people haven't made yet... so... yeah Eric

I'd like to throw in my support for reducing the PM restriction. I didn't realize that there was such a restriction (there wasn't one when I first joined), but only 1 PM an hour is ridiculous...

That's not inflation... Inflation is calculated based on a consumer index, which doesn't change just because soda costs more. 15 USD is 15 USD no matter where you get it; its still double the amount of minimum wage.

What are you talking about... I get 7.50 an hour, and I go to a 70k/year university. I still get by just fine... Oh wait... my parents pay my tuition and housing. But yeah... minimum wage is far too low.

They weren't questions, they were suggestions... I wasn't looking for answers. Don't assume everyone on the forum can't read, Alek. I read your reply, and you told us that neither of the suggestions were going to happen, for the reasons you posted. I don't believe what you said, especially with your argument against auto-compile, but I'm too lazy to PM you about it because 1) it won't change anything, as has been shown many times by the admins who frankly don't care about the scripters. and 2) Even you don't have much of a voice with the devs, Alek. Nobody does. The only way we'd ever get them to change anything is if we all got together. Either way, I'm not arguing with you on whether I read your post. If you read the OP in this thread, all I did was complain that you locked the thread. And I have every right to. The Script Developers section is supposed to be a scripters section for us to discuss things equally, but you ended up locking the thread because you thought your post was the most important and had to be seen by everyone. ... that's cause I reported it and it got fixed by an admin...

You'd probably have to find a someone to convert the money in the market section.

Actually I think I should be the one saying I'm not sure why I even try anymore. Nothing we say ever changes anything with you guys. I read what you said. I posted the thread as a way for scripters to put in their thoughts. It was never a one on one conversation. I was speaking about things that affect all the scripters, not just me personally, so why do you lock the thread and ask me to private message you? Furthermore, I was under the impression from what Maldesto said that no moderation of the Scripter Developers section would happen, except for certain circumstances. None of what I or any other scripter said fell into those circumstances; why did you lock the topic then? Honestly I didn't bother PM-ing you because I gave up. Like I said, nothing we scripters do matters that much... I'll just help where I can, and hope that OSBot doesn't crash.

All right. Thanks for your fixes though

Which randoms were fixed? And thanks Zach and Divinity

Nope. I'm not in contact with @Zach. sorry I can't fix anything unless I get lucky and get an account stuck in it or someone lends me one with an acc in it. However, I'll keep an eye out for these BTW. PrisonPete is fixed in the client apparently, so you should remove this version from your scripts folder. (Unless you want to keep this version, in which case, you should redownload.

Well apparently a update has been released, but I doubt it has fixed all the randoms. As such, I will continue updating these. As for working, once you put it into your scripts folder and then reload, you should get a message in the log like "PrisonPete might override the built in random solver" or something of the like. And so it will automatically run yes. Eric

Hey guys. While we wait for the devs to fix the randoms in the client, I've been releasing fixed randoms that I've fixed since the update. Prison Pete: https://www.dropbox.com/s/8tjleaoj9f2trow/PrisonPete.jar Haven't gotten any other ones. I'll update broken ones as I get them, or if anyone's stuck and wants to let my borrow their account to fix them. To use, just put it into your OSBot/scripts folder, just like a local script, and then reload your scripts and it will be loaded

What's the use of this... I didn't say everything's broken. I said many things are broken. You got lucky this time, nothing that affected you broke. Next time when combat breaks you won't be so lucky...

At the rate this is going? No one will be left at OSBot. Errors just keep adding up... lol I don't think @Zach works on OSBot 1 either... He keeps everything else running though. Without him there wouldn't be an OSBot.

Ouch sorry to hear that... Honestly, if they won't keep OSBot 1 updated, they should find someone who will...

Okay, so I'm a little frustrated by the current status of things. After ver 42 rs update two days ago, there have been many problems with the OSBot 1.7.89 client. Many randoms are broken, the onMessage listener doesn't work, rotateCameraToEntity doesn't work, (possibly selectOption?) and probably other things that I'm not aware of since I don't use them in my scripts. (Please feel free to tack them on here). However, that's to be expected with rs updates. But from what I see, the Developers aren't really working on fixing OSBot 1. Yes, I know Maxi's having some personal life issues, but let's be honest, he wasn't really active on here even before that... And Laz is busy working on OSBot 2, which means that OSBot 1 is just hanging... Honestly, before OSBot 2 is out, keeping OSBot 1 up to date should be the priority... It's what most people are using after all... I made a post in the Script Developers section requesting that the dev open up the source, at least to several trusted scripters, so that they can step in and fix what's broken since the devs are apparently not going to, but @Alek just locked it... List of things I know to be broken so far: 1) RANDOMS 2) onMessage 3) typing 4) rotateCameraToEntity is buggy.

+1 yes agreed.

Lol. Except OSBot 2 still uses more CPU usage even without this issue. Also where did this memory leak thing come from? I barely notice this... Nope, there is no reason why it's horrible. Just people thinking that running OSBot on a VPS will magically solve their problems. Agreed... I run 10+ bots on my desktop... 8GB RAM, i7-3770K

XD Swizz You better keep updating those scripts in the afterlife. We're holding you responsible. But seriously though, if you're buying a one time purchase premium script, you're taking the risk. You can't force any scripter to update their scripts, nor can the OSBot administration.

very very experimental :P but nevertheless it looks good. Still changing quite a bit of my code so that it runs in legacy mode though

No point to repeat what everyone else has said. If I had a cent for every time someone complains about OSBot 2 getting delayed I'd have made more than enough money to pay my way through MIT... If you have every done actual programming you would know that unexpected bugs always happen. It takes 30 % of the effort to write code and 70 % of the effort to debug the code. It's not possible to give an accurate ETA.

Nope, still don't have the skills... Let's keep personal conversation off this thread though.

Added. Good suggestion