ckibbi Posted February 9, 2018 Share Posted February 9, 2018 Until then, if the maximum fire runes in ur bank is 4995 he will put that into charge, 999 and wont check it again : > Quote Link to comment Share on other sites More sharing options...
wtf11 Posted February 9, 2018 Share Posted February 9, 2018 2 hours ago, ckibbi said: Until then, if the maximum fire runes in ur bank is 4995 he will put that into charge, 999 and wont check it again : > what does that even mean? Quote Link to comment Share on other sites More sharing options...
Harky91 Posted February 10, 2018 Share Posted February 10, 2018 On 08/02/2018 at 6:32 PM, FrostBug said: Yea, I pushed a fix, but a developer needs to update the SDN before changes are live. Usually done once a day Can you let us know when changes are live, if not already? Not on my PC atm to check Quote Link to comment Share on other sites More sharing options...
ckibbi Posted February 10, 2018 Share Posted February 10, 2018 11 hours ago, wtf11 said: what does that even mean? If you put maximum 4995 fire runes into your bank which is equal with 999stacks into the staff. and you put 999 stacks into ur staff aswell, and set the charge amount req. To recharge ur staff to 0 it wont keep checking ur charges of staff. ( you have to manually bank every 1998 charges shot via staff) Quote Link to comment Share on other sites More sharing options...
ckibbi Posted February 10, 2018 Share Posted February 10, 2018 9 minutes ago, ckibbi said: If you put maximum 4995 fire runes into your bank which is equal with 999stacks into the staff. and you put 999 stacks into ur staff aswell, and set the charge amount req. To recharge ur staff to 0 it wont keep checking ur charges of staff. ( you have to manually bank every 1998 charges shot via staff) WILL RUN FLAWLESSLY Quote Link to comment Share on other sites More sharing options...
myOSBaccount Posted February 10, 2018 Share Posted February 10, 2018 @FrostBugso today i had a few issues happening. when i first tried to run the script the first run went fine up until it opened the chest, then it just repeatedly tried opening it even after obtaining the loot (getting the message that the chest is empty over and over again). after starting over the script it hadn't happened again. i noticed at some point that when trying to enter the last tomb that would lead to the tunnel it clicked on it a few times, then left and reentnered the tomb and worked fine. when i wasn't checking it was apparently stuck without moving for 5 minutes so the script had stopped. then when i tried to start it up again it was stuck in a loop checking for charges like before. Quote Link to comment Share on other sites More sharing options...
killdabadboy Posted February 10, 2018 Share Posted February 10, 2018 Could i have a trial to test this out? i wanna buy it but wanna test how it works first 1 Quote Link to comment Share on other sites More sharing options...
FrostBug Posted February 10, 2018 Author Share Posted February 10, 2018 3 hours ago, myOSBaccount said: @FrostBugso today i had a few issues happening. when i first tried to run the script the first run went fine up until it opened the chest, then it just repeatedly tried opening it even after obtaining the loot (getting the message that the chest is empty over and over again). after starting over the script it hadn't happened again. i noticed at some point that when trying to enter the last tomb that would lead to the tunnel it clicked on it a few times, then left and reentnered the tomb and worked fine. when i wasn't checking it was apparently stuck without moving for 5 minutes so the script had stopped. then when i tried to start it up again it was stuck in a loop checking for charges like before. Alright; I'll be doing extensive testing over the next couple of days in prep for next client release anyway, so I'll see what I can find. The trident fix is live now for the record Quote Link to comment Share on other sites More sharing options...
myOSBaccount Posted February 11, 2018 Share Posted February 11, 2018 (edited) 17 hours ago, FrostBug said: Alright; I'll be doing extensive testing over the next couple of days in prep for next client release anyway, so I'll see what I can find. The trident fix is live now for the record are you sure? i ran it again just now and it's still repeatedly checking for charges Edited February 11, 2018 by myOSBaccount Quote Link to comment Share on other sites More sharing options...
FrostBug Posted February 11, 2018 Author Share Posted February 11, 2018 1 hour ago, myOSBaccount said: are you sure? i ran it again just now and it's still repeatedly checking for charges Works for me. Mind you the new Echanted trident is not yet supported Quote Link to comment Share on other sites More sharing options...
Harky91 Posted February 11, 2018 Share Posted February 11, 2018 52 minutes ago, FrostBug said: Works for me. Mind you the new Echanted trident is not yet supported Mine is also checking charges still Quote Link to comment Share on other sites More sharing options...
FrostBug Posted February 11, 2018 Author Share Posted February 11, 2018 Okay so it turns out the problem was something else entirely; specifically a change in how chatbox message event consumption works in client 2.4.162. I've fixed it now; which should deal with trident checking issues, but also fix a couple of other things (detecting full inv, already looted chest and a few other things) The fix will be live when the SDN updates. Sorry for the downtime. As a temporary workaround, keeping your tridents charged with less than 1000 charges should allow using it. 1 Quote Link to comment Share on other sites More sharing options...
Harky91 Posted February 11, 2018 Share Posted February 11, 2018 Thanks for working on this so speedily Look forward to it being live on SDN Quote Link to comment Share on other sites More sharing options...
myOSBaccount Posted February 11, 2018 Share Posted February 11, 2018 alright, thanks for the update Quote Link to comment Share on other sites More sharing options...
Sia Posted February 11, 2018 Share Posted February 11, 2018 by the way, is there no way to break & log out? Quote Link to comment Share on other sites More sharing options...
