Dyrone Posted May 27, 2015 Posted May 27, 2015 I was thinking about doing this although i think it would be better to just smith safer until 85 and just safe on rune bars Really not worth to do rune bars and risk that much money on a botted account even if it is mirror mode, better to do mithril/steel/adamantite. 1
kushad Posted May 27, 2015 Posted May 27, 2015 (edited) Khaleesi I not sure if its your script not saying it is but majority of the time my guy is logged not because of inactivity of exp but because of randoms 'solving randoms taking too long' something along those lines ill get a pic when i can but then after that it logs and the script keeps running. Pretty sure its the client though? Edited May 27, 2015 by kushad
Khaleesi Posted May 27, 2015 Author Posted May 27, 2015 Khaleesi I not sure if its your script not saying it is but majority of the time my guy is logged not because of inactivity of exp but because of randoms 'solving randoms taking too long' something along those lines ill get a pic when i can but then after that it logs and the script keeps running. Pretty sure its the client though? uhm what do you mean by solving randoms? You mean the extra tasks of blast furnace? Khaleesi
kushad Posted May 27, 2015 Posted May 27, 2015 uhm what do you mean by solving randoms? You mean the extra tasks of blast furnace? Khaleesi I will try get a pic of it sorry i not making sense
Terced Posted May 27, 2015 Posted May 27, 2015 Khal basically im not sure what the problem is, i can only run the script for a couple of hours before I find my guy logged out. I disabled the report thing aswell...
Khaleesi Posted May 27, 2015 Author Posted May 27, 2015 Khal basically im not sure what the problem is, i can only run the script for a couple of hours before I find my guy logged out. I disabled the report thing aswell... You'll have to babysit and see what the problem is, can't fix it if I don't know what's broken.
Terced Posted May 27, 2015 Posted May 27, 2015 (edited) You'll have to babysit and see what the problem is, can't fix it if I don't know what's broken. i think it may be the anti-ban option because the other night i found it logged out after an hour twice, then i turned off the anti-ban and it ran all night Edited May 27, 2015 by PlatedDesigns
LeBron Posted May 27, 2015 Posted May 27, 2015 i think it may be the anti-ban option because the other night i found it logged out after an hour twice, then i turned off the anti-ban and it ran all night So you used anti-ban, it didnt work out well, you turned it off and it was flawless but you still turned on anti-ban?
kushad Posted May 27, 2015 Posted May 27, 2015 they are running still but...not sure if this going be problem later on http://gyazo.com/2622e3eed60cb8aa8619f5a51d978471
Khaleesi Posted May 27, 2015 Author Posted May 27, 2015 they are running still but...not sure if this going be problem later on http://gyazo.com/2622e3eed60cb8aa8619f5a51d978471 Show me a full screenshot including your RS screen please.
Lil Ugly Mane Posted May 27, 2015 Posted May 27, 2015 Show me a full screenshot including your RS screen please. Script seems to be running fine now that I've turned off anti-ban, just wondering I have an account running and overnight it will hit 60 smithing, will the script detect this and stop paying the foreman?
Dyrone Posted May 27, 2015 Posted May 27, 2015 Script seems to be running fine now that I've turned off anti-ban, just wondering I have an account running and overnight it will hit 60 smithing, will the script detect this and stop paying the foreman? AFAIK yeah it should. 1
Terced Posted May 27, 2015 Posted May 27, 2015 So you used anti-ban, it didnt work out well, you turned it off and it was flawless but you still turned on anti-ban? Re-read my post, think you misread itAlso khal, I got a message saying 'could not find the data orb, activating run manually,please report this bug'
Khaleesi Posted May 27, 2015 Author Posted May 27, 2015 Re-read my post, think you misread it Also khal, I got a message saying 'could not find the data orb, activating run manually,please report this bug' It's the client sending the message ... not a big deal