FrostBug

Yeah the gfx is quite outdated. Unfortunately don't have the designer at hand anymore.

What a hero

Sure; It's much like single-way flicking really. What you can do is create "cycles" of prayer flicks based on an enemy of choice (preferably the most dangerous one; or the one you're attacking). If the chosen enemy has a 4 tick attackspeed, create a 4 tick cycle. You'll want to monitor each attacking enemy; keeping track of when (timestamp) they last attacked. With this you will know when they'll next attack also, granted you know their attackspeed. With this information you can "plot" out the cycle by mapping each attacking enemys next attack to a tick (if multiple attack on same tick, pick the most dangerous one). Once you have the cycle generated, all you have to do is execute the flicks. I'd recommend creating a blocking event that executes the full cycle, to avoid interruption.

try deselecting all enabled quickprayers before starting the script (if any are enabled already)

Thanks. Looks like a problem loading image resources; will take a look at it when I get home. Could I get you to put spoiler tags or something around these long pastes?

Thanks; could I get you to PM me the log file also (will have additional information)? It's located in the OSBot directory under Data\FrostCaves\Logs

Post or PM log

What prayers are you using

Try ensuring your client zoom is at default Yes; altho currently does not make use of the Dragon c'bow spec

naw, just chinchompas

public class Clue { private final static String[] PEOPLE = {"Tom", "FrostBug", "NormieNurd", "Moldy" }; private final static String[] PLACES = {"Library", "House", "Place", "OtherPlace" }; public static void main(String[] args) { String person = PEOPLE[(int)(Math.random() * PEOPLE.length)]; String place = PLACES[(int)(Math.random() * PLACES.length)]; System.out.println("Murder at " + place + " by " + person); } } Like that?

CBA to read all of that sorry. If you could give a summary of what you're supposed to make with this, that'd probably help

What even is a 'game of clue' ?

Same way as normally, through the client settings.

Committed fixes for trident recharge issue and buffing against tunnel creeps Will be live next time SDN is updated

You can still override motion events in BotMouseListener subclasses You use checkMouseEvent as a sort of multiplexer like so: public void checkMouseEvent(MouseEvent e) { switch(e.getID()) { case MouseEvent.MOUSE_PRESSED: //Code break; case MouseEvent.MOUSE_RELEASED: //Code break; case MouseEvent.MOUSE_CLICKED: //Code break; } } But remember to consume the events that you process, if you don't want them to be propagated

Client version 2.5 is out now, so be sure to update Script should be up to date and compatible with it within about 5 minutes EDIT: Script is now updated for client 2.5.1

Hmm.. It should. I'll check it out. As a quick update, the new major client version 2.5.X comes out later today. I've already committed the script changes required to be compatible with 2.5, so as soon as it goes live, this script should run on it fine. 2.5.X changes/improves lots and lots of things, and should hopefully also put and end to the message listener instability we've been seeing recently. I've been testing extensively on 2.5.X since yesterday and things are looking good.

If it still occurs my guess would be instability with the client message listener. Been running 3 hours now tho and nothing wrong yet. In any case I won't be pushing any more updates for 2.4.162. The new major version (2.5.X) goes live tomorrow, and this version changes all listeners

Isn't a castlewars script. It uses the clanwars portal tho

Try again now. Changes just went live a little bit ago. Restart client / refresh script list and try again

Ah, thanks for letting me know. I had assumed they all restored prayer You can use the standard osbot break settings

Okay so it turns out the problem was something else entirely; specifically a change in how chatbox message event consumption works in client 2.4.162. I've fixed it now; which should deal with trident checking issues, but also fix a couple of other things (detecting full inv, already looted chest and a few other things) The fix will be live when the SDN updates. Sorry for the downtime. As a temporary workaround, keeping your tridents charged with less than 1000 charges should allow using it.

Works for me. Mind you the new Echanted trident is not yet supported