There was an issue with the HitSplatListener (I think that was the name). We used to use it in legacy code a while back, then found a more efficient way. After some time the listener broke, nobody used it, and I believe I either deprecated it or deleted it.
Every time you add or remove a position from that area, you should be reconstructing that Area using the new positions in the list (after converting to an array). Or is your issue converting from a list to an array?
I see in your onPaint you have a fancy but useless mouse paint. How about adding a functional output which displays your current state? This way you can at least see which state it's stuck on.
Some additional tips:
Worry about making a properly functioning script, that will save you from more bans than bullshit tinfoil logic. If you are interested why, look into linear regression. It's something you will learn if you take a Statistics course in High School/University.
Use Java conventions for your brackets.
if(conditional) {
//Code here
}
Not:
if(conditional)
{
//code here
}
This doesn't execute:
new ConditionalSleep(20000, 25000) {
ConditionalSleep(timeout, recheck) Should be something like (20000,1000). The one parameter form does a recheck every 50ms.
Edit: Hid your old topic
Don't want to be rude, but you're recreating Grand Exchange API with methods that are very unstable and not particularly efficient.
You used third level static ids which are really prone to breaking on any update involving the Grand Exchange. Additionally that ConditionalSleep will never execute.
GrandExchange isSellOfferOpen()
We have hooks for this.
http://osbot.org/api/org/osbot/rs07/api/GrandExchange.Status.html
Should look something like this:
if(getGrandExchange().getStatus(GrandExchangeBox).equals(GrandExchangeStatus.FINISHED_SALE)
I'm going to count this as my Halloween release, so I hope you enjoy the spookiness. -Added Web Walking Link: Yanille Agility Obstacle (suggested by @Imateamcape and @Chris)
-Added Web Walking Link: Ardougne Agility Obstacle (suggested by @Molly) -Modified various Web Walking timeouts, should recover a bit quicker (various suggesters)
-Patched Store API not purchasing the correct amount of items
-Added Store method sell(int itemId, int amount) (suggested by @House)
-Added Level-7 Enchant spell (suggested by @Solzhenitsyn) -Added 6 new Banks --PISCARILIUS_HOUSE --LOVAKENGJ_HOUSE
--LOVAKITE_MINE
--SHAYZIEN_HOUSE
--ARCEUUS_HOUSE
--HOSIDIUS_HOUSE
Stay safe, check your candy for razor blades and firearms, and keep your bots running while you're out enjoying yourselves.
Work smarter not harder. I'd rather have a scripter that writes logic correctly the first time around than an "active" scripter that pushes 10 commits a day because the logic is consistently flawed.
You will not be able to modify any settings set by the botter, they have the higher privileges.
Edit: Example: breaks, human input, f2p/p2p world, etc.
You can have getters in your GUI class, then check it in your Main class.
Main:
if(GUI.clickedStart())
{
var1 = GUI.getVar1();
var2= GUI.getVar2();
GUI.dispose(); }