Token

@jason257 I've edited your post to comply with our forum rules, discussing other communities is not allowed. Have you tried enabling the randomize bot/break times option?

You have to do it if you want to recover the account, if the account is locked before validating email, it's quite hard to unlock. Idk about bans but it should either make no difference or lower the ban rates.

I'm afraid I'm not currently handling trials on any scripts

Did it continue fine afterwards?

Try the graphic objects introduced in the dev build .60, the effect is a graphic object on the target

Have you ran other scripts previously in the same client? Are you using multiple bot tabs? Does it work if restarting the client? Could you send me an image of your GUI settings?

Uninstall all versions of java (both jdk and jre) and then install the correct one (java 8 )

Account sharing is against the rules

It may require a newer version of windows for mirror mode, try on windows 10

@xlNick are you using a mac?

It doesn't use phials, I'm afraid I'm not currently handling trials on any scripts

Add some runtime limits to simulate sleep patterns, break every dream, change settings to lower interactions per time unit, try mirror mode, all of them should probably make it invincible lol

New record

So what you describe is constructing a path by chaining paths between obstacles, this can easily be achieved with the LocalPathWalker. There are many implementations available for findPath, some of them are like this LocalPathFinder lpf = new LocalPathFinder(getBot()); lpf.findPath(entity); // path from player's position to an entity lpf.findPath(startPosition, endPosition); // path between 2 positions lpf.findPath(endPosition); // path from player's position to a position lpf.findPath(startPosition, entity); // path from a position to an entity You you will probably need the last one. Start with player position and build a path to the destination position, if none is found, iterate through all entities that can be reached and determine whether the position past that entity (use rotation/orientation do determine the position after the entity) can get you closer to the destination. If it still doesn't reach the destination, iterate through all entites that can be reached from the position after the first entity and do the steps above for n iterations. Then simply add up all the paths to create the main path (include the entities that have to be interacted with on the way). There is no need for flags for the above as there are many high level methods already provided in the API that wrap everything needed, but the main problem you will encounter here is that the game only loads in 104x104 blocks, meaning that you can't dynamically access information about entities or flags outside the loaded region without having all this preprocessed and cached. You can do this around fred's house to open gates/doors, but varrock is not loaded and you can't find doors around the castle for example. I strongly suggest you take a look at webwalking, it may save you a lot of time by just calling getWalking().webWalk(destination); Which will automatically walk anywhere on the map, handle all obstacles (not just doors and gates). This can also walk between planes, use teleports, enchanted jewelry, spirit trees, gnome gliders, ships and pretty much everything available in runescape. OSBot's webwalker has been continuously developed for the last 4 years and provided support for advanced scripts like questing, slayer, automated farms and many more. It already has information about obstacle requirements everywhere on the map, including things like passing through the Al Kharid gate depending on whether the user has coins in inventory or the quest completed to pass for free, and would take the longer path otherwise. PS: See WebWalkEvent in the API docs for advanced usage and configuring options like teleports

Entities do not have flags (including players), only positions have flags. You may be familiar with an API where it was presented wrong, but every position has corresponding flags that describe access to that certain position, eg. it cannot be walked from south, south east, north, it is completely blocked, blocked only from south etc. These are all coded in the bits of that number (the position/tile flag). Mentioning what you are trying to do with this would probably be better as you may not need these at all.

I’ve edited your post to conform with the forum rules (discussing other communities is not allowed). Those are the flags for a position, if something is on the position, they will have values to indicate that. What exactly are you looking for?

getMap().getRegion().getClippingPlanes()[POSITION.getZ()].getTileFlags()[POSITION.getLocalX(getBot())][POSITION.getLocalY(getBot())] PS: Flags can only be accessed for the loaded region which is 104x104, throws indexoutofboundsexception otherwise as the localx/localy will not be from 0 to 103. Check that the positions localx and localy are within bounds.

@DylanSRT may want to reply once in a while

Use mirror mode and attach to the official game client

I believe it should be fixed lmk if you are still having issues

Sorry for the delay, I've reverted some recent updates, is it working now?

No, idk what's the issue lol. The code is totally different for Stealth NMZ and FruityNMZ.

Not really, that's the dev version, not stable yet

The new version is up now, is it still happening? What's printed in the logger if it still does happen?

I haven't had any issues with the break manager