Maxi

Congratulations Basic on your new Veteran rank

The answer has already been given on the thread btw ;)

Nope. Nope. This year.

http://osbot.org/forum/topic/153-private-bot-beta-live/ http://osbot.org/forum/topic/351-public-bot-beta-live/

Very close. There were only 2 people and the idea to create the bot was conceived earlier.

Shit, @Oliver knows.

WHO KNOWS WHAT HAPPENS ON MARCH 2'ND? (p.s. First person with the answer gets the Veteran rank)

Dear community, I am looking for people who are having the SSLHandshake exception. I have written a fix for it, but I need some users to test it before I release it. Please PM and I'll provide you with a test client. Sincerely, Maxi

If you are still having this issue please send me a PM. I have written a fix for this but before I release it I want people to test it.

There is obstacle support in the client you that right? There is a door handler.

On a second look, the IP.chat server seems to be reachable and the api is reachable. I'll keep this in mind, I'm all for this feature.

Did you pay with an echeck?

You are not using the latest version of OSBot.

This would be hard to implement with the forum's chat because as far as I'm aware the IP.Chat protocol isn't public. A chat module however is possible, but there are more important things that we work on. A simple irc implementation shouldn't take too much time, we'll keep this in mind. If anyone wants to write this and provide it then we can consider to implement it in the client.

Can you make me an avatar, something related to OSBot and my position?

Donate it to me

Dear community, This update contains quite a few updates. Besides a couple of API updates / additions we wanted to make we also faced some changes in OSRS that caused some issues. We are happy to release this so enjoy! The following patches are included in this update: @Maxi's changes: -Applet resize issue has been resolved -PolygonArea getRandomPoint() method patched -Fixed bank scrolling -Fixed item definition issues that occurred as of the latest OSRS update -Patched Trade API to correctly access the container items + added offer and removal functionality -Disabled anti-ban while human input is enabled -Some rare stability issues have been addressed @Alek's changes: -EquipmentSlot: Removed actions --Equipment equip method searches for both "Wield" and "Wear" -Added PositionFilter -Added price filter to script browser -Temporary fix to script selector pack error causing OSBot not to load -Ensured Quests are opened (not diaries or minigames) while calling Quests methods -Added Quests method getQuestPoints() -Deprecated verifyTrade() -API Docs have been updated Sincerely, The OSBot team

Dear community, As most of you know Jagex released the Free to Play version of the OSRS game again today. I am very excited, because this will create many new opportunities for botters. With the past couple of months being about many releases of OSBot to strengthen the bot's stability, we have managed to expand our user base again. I am very happy about this and we should thank the entire staff team for all of their efforts! Thanks to @Alek @Zach @Maldesto @MGI @Divinity @Dex @Noah @Oliver @Anne @Basic and all ex-staff members who have contributed over the past months! But not only Jagex is bringing new things. We will be bringing some very nice things to the table in the time to come. The first thing will involve an entirely new way of loading the OSRS client in OSBot that will lower chances of Jagex being able to flag players as bots based on the client. Right now all bots out there suffer from the same issue, Jagex is able to flag bot users based on the client. This is not only the case for OSRS but also for RS3. On top of this, it will allow us to become the first bot in history that will allow users to use a proxy per tab, instead of a proxy per bot application. This new way of loading the OSRS client will be implemented in the OSBot 2 client as an option to use. This will stand for this feature its BETA. You will be able to use the old loading and the new loading, so if there is a bug you can report it and we can have it fixed for the official release. On another note, we will be bringing forward a special collection of new scripts. First of all, we will make available a collection of VIP only scripts written by some of the best script writers that will be newly introduced to OSBot soon. Secondly, there will be a special script collection written by the same script writers that will guarantee an overall level of quality and maintenance. These scripts will get implemented and become available over the coming months. We hope you are just as excited as we are for this all to be deployed! Sincerely, Maxi & the OSBot team

Dear community, As of todays update we're experiencing some issues with items on several interfaces. We have done some research and patched a couple of things already, but as it is getting late at night we will continue tomorrow and have the patches released. Sincerely, The OSBot team

Dear community, This should be the last (hopefully) walking patch. In this patch the logic for using Area instances with the WalkingEvent is patched to work correctly again. Sincerely, Maxi & the OSBot team P.S. For whoever got the corrupt jar, please re-download. The initial upload of the jar went wrong. P.S.S. Your posts didn't get removed but the thread was reposted. It's one of those days lol.

No respect given. Besides the fact my father in law is currently dying from cancer, but he might now know. Regardless from that, someone with this attitude is not adding anything to OSBot.

What it is saying is that your client is missing a method that the script is trying to use. It has nothing to do with the RS update. Update your bot to the latest version 2.3.16 which was released a couple of days ago. The script writer has probably updated his script to use this method.

Dear community, In this release you will find patches made to the WalkingEvent and DynamicCircularPathFinder classes. The following things should be fixed: Issues mentioned in the release of 2.3.15 You can now use minDistanceThreshold accurately again when using WalkingEvent. This gives you control over whether you want to want to walk to a location exactly or that you are fine with a certain threshold that leads you towards the location with an x number of tiles inaccuracy. Sincerely, Maxi & the OSBot team.

Contacted you.

It's both but their systems have learned a lot.