Alek

Damn are people really this spoiled by web walking? This room is a puzzle (I know you are talking in general), I would literally have to write in code that solves the puzzle for the scripters. Our API is enough spoonfeed, just don't be lazy and use "door.interact()". /endrant Nothing personal but damn man! Edit: If you are particularly lazy take a look at the DoorHandler API, ugh.

Figure out if it's a high dpi display, also what's your resolution?

Lots of tinfoil and stuff that will break within 2 weeks Edit: Not a bad try though

Im laughing so hard right now

have you guys seen this meme lately?

Edited your topic title; unfortunately I'm getting very frustrated with the amount of people blaming the new client version. Not your fault but its very overwhelming.

50 att, 1 def, 15 pray, 70 str, 71 range, 65 hp

Please read the comments I made above, I stated that this is a script issue and not a client issue. Contact the script writer.

I dont think you know how much of an anti-tinfoiler I am. I bot about 5-10 tasks/day while I do other things. One time I ran it for about 20+ tasks, but I only did that once.

did u like how my character looks? hes in all black and very scary first slayer master is low, but i gained like 6 str levels and a few hp levels

Are all of your scripts Czar scripts? I'm running scripts right now just fine.

A wilderness script would be something like a wilderness boss killer, green dragon killer, edgeville looter, Resource Area script, lava dragon killer, etc. Although there is an obelisk that is in the wilderness, the core functionality of this script revolves around crafting orbs. If this was an orber that only crafted orbs in the wilderness, then it would not be allowed. This is also entirely based on discretion. Remember to give Nimmogel constructive criticism on his new script

I read the error log and its a script error, not a client error. Once again please don't make assumptions

Scripts are starting, please don't spread rumors. Ask the script writer why your scripts aren't working.

Remember to credit me in your slayer script for giving you all these links (also better credit MGI).

Had to do a fix today because of an option change to Veos for travelling to Zeah. To make the release more meaningful, @MGI grabbed all the data for me to create the door links for Stronghold of Security floor 1. I did have some of the links already manually added for my Macro Slayer script, but figured I'd just give you guys the whole enchilada. I'll work on the rest of the floors when I add Mazchna to my script. Changelog .152: -Added all Stronghold Security floor 1 links to web walking (reaches first room on floor 2) -Patched Veos travel to "Great Kourend" (emergency fix) -Added new surge spells Changelog: .153: -Patched an issue with Chatbox API and private messages that aren't separated

How do you know this?

Sounds about right, ill try looking this up.

This is not correct because I can skip the second level on Combat Level 56.

Someone find me the exact combat levels required to skip through the portals on each floor of Stronghold of Security. Also I'll need to know how you found out about the required levels and any sources you discovered to make the claim. Edit: I essentially need 4 numbers. Thanks!

You're welcome my children

Changelog: -Added PathPreferenceProfile setAllowCharters(boolean) -Added PathPreferenceProfile setAllowGliders(boolean) -Patched Chatbox API errors with clan chat -Added Chatbox API clan chat support -Modified web walking teleport code -Added 10 Web Walking links to support mining guild --Fixes issue with traversing through these default links -Web walker requires > 75% of region traversal to trigger teleports

Don't handle doors if you are using web walking. Right now it looks like you're trying to web walk to the area first and then open the door? Since these are static areas and I'm sure you're not traversing the map, save 1-2GB of member and don't use web walking. If the door is in the same region as the bank (I sure as hell hope it is), then on the script start grab the door object. Create a WalkingEvent and set the break condition to if the door is closed. If the door is closed, WalkingEvent will break, then you can handle the door. Additionally: You aren't disposing your GUI, this is lost memory. Dispose of your GUI and keep your variables contained in the script (aka no more GUI.getArea). Also your script will break within a month with all those static ids.

They've been doing this for years to destroy pures and specific account builds. Last time it was dying while autocasting on ancients, it would switch to a defensive stance (even if at duel arena). Not sure if they changed this.