Maxi
-
Posts
1430 -
Joined
-
Last visited
-
Days Won
82 -
Feedback
0%
Posts posted by Maxi
-
-
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 updatedSincerely,The OSBot team-
5
-
-
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
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
-
16
-
-
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
-
5
-
-
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.
-
2
-
-
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.
-
4
-
-
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.
-
4
-
We will be looking into it together with Apaec.
-
I woke up to alot of notifications
Contacted you.
-
1
-
-
It's both but their systems have learned a lot.
-
It's definitely something they might look at if you bot at night. But they won't use that to ban you by itself, but I can imagine it definitely ticks a box somewhere.
-
We will be starting a reality series on it soon, VIP only.
-
2
-
-
Dear community,
We wish you all the best in 2015, may it be a year full of beautiful moments, cheering and laughing. I want to shout out thanks to our staff for all the hard work they have done last year and we will dive in to 2015 with a couple of nice updates planned.
I want to give a special shout to @Zach, @Maldesto and @Alek for their loyalty and commitment. Thank you guys!
Sincerely,
Maxi and the OSBot team
-
3
-
-
-
Firstie
-
1
-
-
The issue has been resolved: http://osbot.org/forum/topic/63499-solved-todays-downtime/?p=699605
-
Dear community,
Today we have experienced DNS amplification attack, a kind of DDOS attack. Because we were on CloudFlare's plan for the last couple of weeks, CloudFlare got overrun by the traffic and re-routed traffic and our SSL certificate expired. The forums were directly routed to one of our reverse proxies again, instead of being behind CloudFlare, it caused a warning on most browsers that the website was no longer secure. The bot also suffered from the absence of the SSL certificate, rendering the bot to a non working state.
Zach immediately warned me and we tried to solve the issues as fast as possible. Everything should be back to normal. We apologise for the inconvenience and wish you a happy botting continuation.
Sincerely,
Maxi and Zach
-
7
-
-
We are working on the solution. We suffered from an DNS amplification attack. We will have it all back up and running asap.
-
The time spent on that project, will remain spent on that project. I, nor anyone, can reverse that. His focus will be with the '07 client and might shift in time to other projects. The '07 client needs priority right now.
Nice, does he plan on being active in the community?
That is a question you will have to ask him.
-
-
Is he now moving on from RS3 to the oldschool client?
Yes.
-
3
-
-
MGI has not been developing on the oldschool client previously.
-
1
-
-
Dear community,
As of last month there have been a couple of issues arising with @Laz. For his and our own privacy I can't tell much about it, but I'm informing you that he has been removed from the development team. We want to thank him for all his work done and hopefully we can work out everything in a nice manner with him.Although I've moved from development to managing on the top level, I've been keeping in close contact with both @Zach and @Alek. Despite the unfortunate circumstances with @Laz, it was my responsibility to find someone to replace him. With that said, I'd like to introduce @MGI as our newest lead developer. @MGI (also known as Mangis and mgi125) will be working alongside @Alek to improve on the bot. @MGI has a big history in RS related projects and his knowledge of programming is very special.We hope to announce the plans that @Zach, @Alek, and @MGI will be working on once they are ready for release.To finish my post, I would like to thank @Zach, @Maldesto, @Alek and all the other staff members for their hard work over the past time.Sincerely,Maxi-
8
-
-
Dear community,
To show how the auto updater works for who has downloaded 2.2.11, here we go.
Also the following things have been patched in this update:
- Bank.withdraw(#) with x amounts has been fixed to return proper values at all times
- Prayer.set(#) has been patched
- ItemContainer.contains(#) has been patched to accept multiple filters
I have also made some updates to the tracker here: http://osbot.org/forum/tracker/project-3-osbot-2/
My current situation has improved so I'll be able to devote some time again on fixing issues with OSBot, so please keep using the tracker and I'll have a look at the issues.
You can find the download to v2.2.12 here: http://osbot.org if you didn't get a chance to download v2.2.11 which contains the auto updater.
Sincerely,
Maxi & the OSBot team
-
8
.
|Since 2009| Making Rice's Graphics Shop |Over 1,000 Orders Completed|
in Shops
Posted
Can you make me an avatar, something related to OSBot and my position?