Leaderboard
Popular Content
Showing content with the highest reputation on 02/22/15 in Posts
- 
	6 points
- 
	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 team4 points
- 
	4 points
- 
	4 points
- 
	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, Maxi3 points
- 
	3 points
- 
	3 points
- 
	Just posting my old work I done around 2 years ago on osbot. Note that this work was done 2 years ago and doesn't represent my current skill/experience.2 points
- 
	2 points
- 
	2 points
- 
	2 points
- 
	add -> !cow.isUnderAttack() You should be useing a Filter instead, this code willc ause the script to pause it the closest cow in underattack. use this: NPC cow = script.npcs.closest(new Filter<NPC>() { @Override public boolean match(NPC npc) { return npc != null && (npc.getName().equals("Cow") || pc.getName().equals("Cow calf")) && !npc.isUnderAttack() && npc.getHealth() > 0; } }); You could also check death animation from the cow are check if the cow is over 0 health so it prevents clicking deaths cows. Goodluck2 points
- 
	Use of a filter would be appropriate here A filter is a way of it only accepting a entity if it meets all the criteria. Currently your only criteria is for the entity to be named "Cow" which, even with the checks underneath will still find any cow at all. The only reason you dont attack one whilst fighting is because of some of the checks underneath. Your check in filter form would look like: NPC cow = npcs.closest(new Filter<NPC>() { @Override public boolean match(NPC npc) { return npc != null && npc.getName().equals("Cow"); } }); Which checks would return the same but you only want to find a cow not in combat so you'd need to add more checks NPC cow = npcs.closest(new Filter<NPC>() { @Override public boolean match(NPC npc) { return npc != null && npc.getName().contains("Cow") && !npc.getName().contains("Dairy") && !npc.isUnderAttack() && npc.isAttackable() && npc.getHealth() > 0; } }); This check checks for the name, and would allow inclusion of the little cows but excludes dairy cows after it has identified the fact its a cow it moves on to check: Is the npc under attack? is the npc able to be attacked by your player? is its health > 0? (avoid clicking on cows which are dying) you can add as many checks to this as you like. Sorry if my explanation is bad2 points
- 
	Perhaps what you might find easier is having a handful of pre-recorded paths, maybe 2 or 3, each slightly different, and when walking the path it would pick a random one of the three each time. As far as randomisation goes, that's not a too bad way of doing it, and its nice and simple too Apaec2 points
- 
	2 points
- 
	I forwarded this and someone will look into it as soon as possible! Please make sure that you restarted the client or clicked the refresh button!1 point
- 
	Thanks, I use to run a service just like you during my spare time but times changed. I will probably set up a free shop sometime soon during my free time of course.1 point
- 
	Holy crap dude this is jus awesome, can't find one that is any better than the other1 point
- 
	1 point
- 
	1 point
- 
	Sorry to say I won't buy this script, because I already have APA's, love your range guild script though.1 point
- 
	1 point
- 
	1 point
- 
	1 point
- 
	You can't make a joke about something that doesn't exist. 0/0 didn't laugh. I don't get it you guys.1 point
- 
	1 point
- 
	1 point
- 
	1 point
- 
	1 point
- 
	Just bought the script, looks very nice Could post a progress here later if its allowed :P1 point
- 
	1 point
- 
	1 point
- 
	1 point
- 
	thank you for rushing it, i will look out for future bugs and will inform you, also will post a proggy when i can get to it.1 point
- 
	just bought this , it looks like a great script ! btw , ill post feedback if i encounter anything1 point
- 
	1) you are not generating a path, you are generating a position, a single position. 2) you are making the x and y positions have a variance, if you happen to generate a random position that is not walkable, then the if statement will not execute. 3) if the position is too far to walk to then it will do nothing. LocalWalker will not take you cross regions without a path unless the region is cached, then it might (depends on client implementation). If you are trying to walk a path, you need to give it a path. This will walk from one single point (the player) to the sudo random position that you are generating within the same region. If that is what you want to do then this will kind of work maybe sometimes.1 point
- 
	Dude you still need to tell us why Karamaja Banking doesn't work its the whole purpose why I bought your script. and paid for VIP1 point
- 
	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.1 point
- 
	1 point
 
		 
       
       
       
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	 
	