Khaleesi

What's wrong with this world ...

What do you mean? Try restarting the client or something Also check the console log of the client, it will show some info whats going on. Let me know when you get it fixed ^^ Sure Enjoy the trial Khaleesi

Yes I could change that I'll take a look at it ^^ Khaleesi

Check the console log of the client It will be explained why it logged off.

Click your name at the top of the screen, The navigate to "Client area" at the right bottom, Everything should be in there what you want to know

It has been added like 2 months ago... Recheck the GUI xD Ya Thats a mirror issue Ya I know about the issue. I'll get it solved asap! Khaleesi

Item id's never change, so you can use them if you want to Entities have their ID changed every update. This means, NPC's and objects will have swapped ID's. So you should use names. NOte: Jagex will be a bitch and call some npcs/gameobjects "null". You should use models to get those specific entities ^^ Khaleesi

Item id's never change, so thats not a problem. NPc's and gameobjects do change, so you should use names for those There also more advanced ways, like using models to search for entities ^^ Khaleesi

Auto-login is client related, I can't change that

Didn't they got fixed yet? Why does it always take 4-5 updates to fix one thing ... oh god

No it's the other way around. Mirror is slow in general. Its unstable and returns false info at some points. all we can do is wait and hope devs fix them Khaleesi

Was about to ask the same thing ^^

Are you sure you selected steel bars? If you are using mirror, ditch the mirror client please. It's broken and doesn't function stable

Ya it's due to the obstacle there ... they are weird and have very straneg shapes, making it impossible nearly to calculate the positions or just makes it unable to find it Another thing at falador is that this is a giant bottleneck to a lot of botters. Bann rate is insane at fally. Try to skip it If you would ditch mirror client and use injection it will be a looot better already I'll take a look at this issues. Clicking though the ground seems to me an issue with osbot which can't deal properly with objects being visible, but I'll take a look at it ^^ You got a few more hours Ya rooftops are better in general + you get mark of graces ;) I'll take a look at the tree, though I fixed that. Khaleesi

If you want to make a bug report, atleast use the right template and give me some more info ... It's useless to post: "gets stuck" or "doesn't work". Khaleesi

Ya it does, but it's not 100% working though. I'll take a look at wildy course tomorrow! it doesn't support potions ... I never ran out of energy on any course Don't really see the point though ... You got 24 hour trial Khaleesi

Got your zoom set to default? Works fine for me

Thx! will take a look at this

1) Some people can't use the other bank. It picks one of the 2 banks on the left randomly based on ur position. 2) It should do that ... atleast does it for me whne I test it. 3) I'll have to rewrite the whole core of the scrip to do that + combining banking tasks is hard, even some people can't even do it LOL ^^ Khaleesi

or this ^ depending in what situation you need the camera stop moving

It actually does it pretty randomly, sometimes it will be more then other times. I can lower it a bit though. Khaleesi

If you would only read my posts That means: As soon as the scripts gets updated by the SDN manager ^^ Khaleesi

Try: "camera.stop.moving.pleawse.you.slow.me.down"; ;) Just make custom InteractionEvents. and set the event so it doesn't use the camera InteractionEvent event = new InteractionEvent(entity,action) event.somecameraoption... script.execute(event); tada! You'll have to rewrite it some, typed on my phone .. Khaleesi

Whats the issue then? If you don't explain Anything, how do you expect to get helped? yes it's lifetime Are you using mirror mode? What course? What obstacle does it give this error? EDIT: Mirror is bit broken lately, use injection instead. Bug reports have been made to the devs. Khaleesi

One of my users reported this, it's the same walking issue: The positions of the path got messed up