Chris Posted May 4, 2017 Posted May 4, 2017 2 minutes ago, Alek said: Looks like its working pretty well for you, unless this is a bug report haha. Just letting ya know its working =P
k9thebeast Posted May 4, 2017 Posted May 4, 2017 Fight me bro. No good updates allowed on this bot. Making me fucking mad m8. GJ m8.
Adept Posted May 5, 2017 Posted May 5, 2017 (edited) Sweet update. Although I don't get what harm the moveRandomly() and moveSlightly() methods do. Why not leave them in and leave it up to the scripter whether to use them or not? Edited May 5, 2017 by Adept
Chris Posted May 5, 2017 Posted May 5, 2017 Update @Alek Compiled in .122 & script ran in .122 Interaction fails when it is a GroundItem using .interact("Take");. Issue: it will simply hover over the GroundItem Confirmed working in .121! Code: private Predicate<GroundItem> suitableLoot = g -> Constants.lootList.contains(g.getName()) && context.getMap().realDistance(g) <= 8; final Optional<GroundItem> lootable = context.getGroundItemStream().filter(suitableLoot).findAny(); if (lootable.isPresent()){ if (lootable.get().interact("Take")){ //stuff } } 1
Alek Posted May 5, 2017 Author Posted May 5, 2017 11 minutes ago, Chris said: Update @Alek Compiled in .122 & script ran in .122 Interaction fails when it is a GroundItem using .interact("Take");. Issue: it will simply hover over the GroundItem Confirmed working in .121! Code: private Predicate<GroundItem> suitableLoot = g -> Constants.lootList.contains(g.getName()) && context.getMap().realDistance(g) <= 8; final Optional<GroundItem> lootable = context.getGroundItemStream().filter(suitableLoot).findAny(); if (lootable.isPresent()){ if (lootable.get().interact("Take")){ //stuff } } Yep I'm aware of this already (I had updated the OP with this bug a few hours ago). I'm working on a fix, which is actually pretty difficult because there's a lot of back-end API missing for it. Edit: It effects RS2Object as well, not sure if that bug is more prevalent because stacks aren't common. 4
progamerz Posted May 5, 2017 Posted May 5, 2017 6 hours ago, Alek said: Yep I'm aware of this already (I had updated the OP with this bug a few hours ago). I'm working on a fix, which is actually pretty difficult because there's a lot of back-end API missing for it. Edit: It effects RS2Object as well, not sure if that bug is more prevalent because stacks aren't common. Umm i don't think so it effects RS2Objects cause i am using them and working much better than before, can i ask how it does effect RS2Objects?
Alek Posted May 5, 2017 Author Posted May 5, 2017 1 hour ago, progamerz said: Umm i don't think so it effects RS2Objects cause i am using them and working much better than before, can i ask how it does effect RS2Objects? It's for selecting stacks of objects in a menu. For instance if you have two guards to "Attack" in one menu. It shouldn't be working for stacked RS2Objects. 1
progamerz Posted May 5, 2017 Posted May 5, 2017 24 minutes ago, Alek said: It's for selecting stacks of objects in a menu. For instance if you have two guards to "Attack" in one menu. It shouldn't be working for stacked RS2Objects. Oh ok thanks for explaining 1
Alek Posted May 5, 2017 Author Posted May 5, 2017 New version 2.4.123 released, let me know how that works for you guys. 1
Chris Posted May 5, 2017 Posted May 5, 2017 15 minutes ago, Alek said: New version 2.4.123 released, let me know how that works for you guys. is the jar supposed to say .123 or just stay as .122? I'll test the jar i downlaoded though
Alek Posted May 5, 2017 Author Posted May 5, 2017 7 minutes ago, Chris said: is the jar supposed to say .123 or just stay as .122? I'll test the jar i downlaoded though Jar is supposed to say .123 Edit: UGH! Forum software.... I updated the link. 1
Tom Posted May 5, 2017 Posted May 5, 2017 55 minutes ago, Alek said: Jar is supposed to say .123 Edit: UGH! Forum software.... I updated the link. Darn forum software!
