FrostBug

You should read the FAQ. It's possible obv. but with low def you're gonna burn thru your food in the tunnels. If you can run barrows on it yourself tho, then the script can do it too

I would not recommend it if it doesn't meet the recommended stats

Started

You probably have a misconfiguration somewhere. Follow the guide found in the first post. If that does not solve your problem, fill in the bug report template. I can't help you with this little information in any case

Like I've said before: You can't. It seems like ~60% think it's a must, and ~40% want it gone.. so I'll probably add a checkbox

that might be fun.. +1 It would be full of botters tho

Starting one now

Please read the Feature Guide in the first post, and ensure that your autocasting is properly configured

Switched over as well when it started logging me into skype, without an option to log off.. It does have an option to unlink it of course; granted you will have to delete your skype acc... I was :salty:

Starting a trial. Tho you're probably gonna have a bad time with 1 def. Glad it's running now; but it's thanks to @MGI I believe. Definitely strange. You're right tho, it finds your portal just fine; but for some reason gives an error when determining its model height. I haven't seen it before, but I will definitely go take a look Each user is only allowed one osbot account

It does, yes. I'll update the OP

Depends more so on your magic/range levels than melee stats. Check out the FAQ I'll take a look at it

Scrolling within the bank is broken in the mirror client. Ensure that your potion (and all dose variations of it) are located in a seperate tab, to remove the need for scrolling. That, or use super restores in place of prayer potions

Well, mirror seems to work fine for me. And for some other people as well. Those of you who still experience problems running mirror will have to use standard. I won't be searching for mirror related needles in the haystack anymore. Not for a while at least. Mirror is a beta product on the side; and I am tired of wasting hours upon hours searching for problems that I cannot reproduce. @@frozen8 I expanded the ClanWars area a bit, and added an extra startup check on the drain listener; I think your startup problem was probably caused by the script not properly stopping in your previous run.

Version 1.3.4 - Added a workaround for mirror mode position issue - Decreased prayer restoration threshholds a bit - Prayer management now takes the time until next prayer-drain into consideration _______ This update should fix mirror problems (hopefully), as well as decrease the number of ppots used in general. It will be live as soon as the SDN manager reviews and accepts the changes.

Pretty sure there isn't. Unfortunately I suppose you could make delta comparisons of the ground items available and see if the loot appeared around the same time as your target died

Not sure what you want me to fix. I don't even know what "Karil's wall" is. Please use the bug report template found in the OP

oh.. right :E Might try to have it look at the tomb object coordinates instead; but for all I know, everything in the region could be loaded with incorrect coordinates .. Would be great if I could actually debug this; but it has yet to happen to me For anyone with these problems. The only current solution is to use the standard client. Until I either figure out a viable workaround, or the problem is fixed with a new mirror client version

Stop spamming Okay, so at least the region seems properly loaded. Was this right after the bug occured?

As has also been discussed before; Bank scrolling doesn't work on the mirror client. Place your items on a seperate tab to work around it

try this /* * Rotate the camera to an entity; Based on angle calculations */ public void cameraToEntity(Entity e) { cameraToPosition(e.getPosition()); } /* * Rotate the camera to a Position; Based on angle calculations */ public void cameraToPosition(Position p) { Position pos = myPosition(); int angle = 90 + (int) Math.toDegrees(Math.atan2(-(p.getY() - pos.getY()), p.getX() - pos.getX())); int yaw = angle < 0 ? Math.abs(angle) : 360 - angle; CameraYawEvent evt = new CameraYawEvent(yaw); execute(evt.setBlocking()); } EDIT: or just try to set whatever camera event you're using to be blocking (Event#setBlocking) before executing it.

Well shit Sorry to hear it Could you try using the "Entity debugger" then, and hover over the player?

I really have no idea what those coordinates are; or where the mirror client gets them from. they don't seem to even partially match the actual tomb or mound coordinates. Could you try enabling the clients position debugger in the client settings (While inside of the tomb after getting the error)?

Using a 32 or 64bit java install?