Alek Posted January 6, 2018 Posted January 6, 2018 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 13
Alek Posted January 7, 2018 Author Posted January 7, 2018 6 minutes ago, El_Maestro said: Zeah is overrated anyways Remember to credit me in your slayer script for giving you all these links (also better credit MGI).
RDM Posted January 7, 2018 Posted January 7, 2018 the free-est post count and likes recently. I see what you're really up to Alek
Butters Posted January 7, 2018 Posted January 7, 2018 Lol each morning I get up and have to update all osbot clients Thanks for the fixes and improvements 1
spectre007 Posted January 7, 2018 Posted January 7, 2018 hi Alek after client update script wont start https://imgur.com/a/Xzw7r
Alek Posted January 7, 2018 Author Posted January 7, 2018 10 hours ago, spectre007 said: hi Alek after client update script wont start https://imgur.com/a/Xzw7r 4 hours ago, TeeVii said: need another update. no scripts starting Scripts are starting, please don't spread rumors. Ask the script writer why your scripts aren't working.
spectre007 Posted January 7, 2018 Posted January 7, 2018 (edited) 4 minutes ago, Alek said: Scripts are starting, please don't spread rumors. Ask the script writer why your scripts aren't working. already asked but this error occured after the client update . Thanks for the reply ! Edited January 7, 2018 by spectre007
Alek Posted January 7, 2018 Author Posted January 7, 2018 19 minutes ago, spectre007 said: already asked but this error occured after the client update . Thanks for the reply ! I read the error log and its a script error, not a client error. Once again please don't make assumptions
