Printable View
Hey Footballjds, thx for making this great bot, using it to finally max this awful skill.
One issue I've noticed is if it goes to 1 certain spot around the rift (red x in image), it 99% of the time doesn't find the rift and clicks the minimap again. I should probably note I've edited the script a little so I can use it without smart, I don't beleieve that's what is causing this though.
Attachment 23060
It does everything, but it has sort of a glitch. So, when it is looking for wisps, it sometimes right clicks it instead of left click and then it doesn't click Harvest.It also does this at times when it just gets to the rift.Sometimes, it doesn't even click the rift. Then other times, it clicks it but then right clicks some random thing and not the box that I chose to click. Sooo, idk whats going on
Once it's done getting wisps it just spams: .getPlayerPos() and doesn't acutally convert them
e: this is at bright wisps btw near varrock.
Try starting with a full inv, stood next to the rift.Quote:
Originally Posted by wilsonc91
any idea how i can make the script bypass the 6 hour? working flawlessly atm thought, ty.
Was working fine for a now i get an error during memory conversion:
-- .getPlayerPos(): result = {X = 178, Y = 154}, took 16 ms
-- .getPlayerPos(): result = {X = 178, Y = 154}, took 16 ms
-- .getPlayerPos(): result = {X = 178, Y = 154}, took 15 ms
-- .getPlayerPos(): result = {X = 178, Y = 154}, took 15 ms
-- TRSChooseOption._select():
---- Options found: [Cancel]
------ TRSChooseOption.close(): result = true
---- Failed to find any text matches
-- TRSChooseOption._select() result = false
-- .getPlayerPos(): result = {X = 178, Y = 154}, took 15 ms
-- .getPlayerPos(): result = {X = 178, Y = 154}, took 16 ms
-- TRSChooseOption._select():
---- Options found: [Cancel]
------ TRSChooseOption.close(): result = true
---- Failed to find any text matches
-- TRSChooseOption._select() result = false
-- .getPlayerPos(): result = {X = 178, Y = 154}, took 15 ms
-- .getPlayerPos(): result = {X = 178, Y = 154}, took 16 ms
-- TRSChooseOption._select():
---- Options found: [Cancel]
------ TRSChooseOption.close(): result = true
---- Failed to find any text matches
-- TRSChooseOption._select() result = false
-- .getPlayerPos(): result = {X = 178, Y = 154}, took 16 ms
At gleaming after getting a full inventory it will walk to the rift to convert and stand there doing nothing.
-- .getPlayerPos(): result = {X = 172, Y = 208}, took 15 ms
Anyone else having a problem where the proggy doesn't show up/ when it does it doesn't update? Anyone know how to fix this?
Also, if it's got the deposit crater for memories on screen when it's gathering memories and another player is depositing it sees the blue glow from the deposit and thinks it's a siphon location and keeps right clicking until the player/s move and stop depositing
As for the first, that's a DirectX bug (if you're using DirectX, that's an issue with the plugin, not with this script).Quote:
Originally Posted by JDBORED
-- WARNING: .getPlayerPos(): Didn't find enough matches accurately calc your postion
-- .getPlayerPos(): result = {X = -1, Y = -1}, took 63 ms
spams that over and over and as a result stands still
it also gives ME the problem where after a full inventory it spams getPlayerPos() instead of going to rift i say me cause its probably a user error
Quote:
Originally Posted by victordono
Dont worry. I am running into the same error. I am able to collect and get a full inventory. But after that, it breaks.
Using openGL. Also, the minimap is black, but I have selected FALSE in train without minimap.
are you in openGL mode?Quote:
Originally Posted by noxehhh
for me it just grabs the wisps then goes stand by the rift doing nothing :/ using opengl
stop and start script again. that fixes itQuote:
Originally Posted by luxrath
Having an issue with luminous wisps. Whenever I get a full inventory, It will keep running between rift and the coast.
This is what happens after a full inventory.
Quote:
-- .getPlayerPos(): result = {X = 170, Y = 178}, took 156 ms
---- Waiting while the player is moving...
-- .getPlayerPos(): result = {X = 70, Y = 106}, took 156 ms
-- .getPlayerPos(): result = {X = 262, Y = 174}, took 156 ms
---- Waiting while the player is moving...
-- .walkPath(): result = True
-- .blindWalk(): result = True
-- .getPlayerPos(): result = {X = 70, Y = 82}, took 156 ms
-- .getPlayerPos(): result = {X = 250, Y = 182}, took 141 ms
---- Waiting while the player is moving...
-- .walkPath(): result = True
-- .blindWalk(): result = True
-- .getPlayerPos(): result = {X = 206, Y = 166}, took 156 ms
-- TRSChooseOption._select():
---- Options found: [Walk here, Cancel]
------ TRSChooseOption.close(): result = true
---- Failed to find any text matches
-- TRSChooseOption._select() result = false
-- TRSChooseOption._select():
---- Options found: [Walk here, Cancel]
------ TRSChooseOption.close(): result = true
---- Failed to find any text matches
-- TRSChooseOption._select() result = false
-- TRSChooseOption._select():
---- Options found: [Walk here, Cancel]
------ TRSChooseOption.close(): result = true
---- Failed to find any text matches
-- TRSChooseOption._select() result = false
-- .getPlayerPos(): result = {X = 206, Y = 166}, took 172 ms
-- .getPlayerPos(): result = {X = 206, Y = 166}, took 156 ms
---- Waiting while the player is moving...
-- .walkPath(): result = True
-- .blindWalk(): result = True
-- .getPlayerPos(): result = {X = 70, Y = 74}, took 140 ms
-- .getPlayerPos(): result = {X = 218, Y = 154}, took 187 ms
---- Waiting while the player is moving...
-- .walkPath(): result = True
-- .blindWalk(): result = True
-- .getPlayerPos(): result = {X = 206, Y = 158}, took 140 ms
-- TRSChooseOption._select():
---- Options found: [Walk here, Cancel]
------ TRSChooseOption.close(): result = true
---- Failed to find any text matches
-- TRSChooseOption._select() result = false
-- TRSChooseOption._select():
---- Options found: [Walk here, Cancel]
I have something to add to this. The script works fine and all for me, however when it goes to back to the rift, it clicks far past, out into the desert, before doubling back to the rift. Not completely sure why, as there are no wisps in that direction and surely it would be more efficient to just stop at the rift. This becomes an even larger issue when the distance travelled causes a new area to load, which often results in the minimap glitch, thus preventing the script from continuing. If I start the script logged in beside the rift, it will click far east on the minimap too, before doubling back.Quote:
Originally Posted by Faxing Berlin
Reading from like 20 pages got me the answer and it´s running
mind sharing what you did?Quote:
Originally Posted by wister1
had direct x set on true, which should be false if using opengl which is what smarts uses, direct x is for browser. as for the rest just use the settings the walktrough says
SMART can also use Direct-X, that's why there is an option in the script for it.Quote:
Originally Posted by wister1
Direct-X Plugin topic: http://villavu.com/forum/showthread.php?t=107256
thanks for the info clarity, didnt knew, i just came back to rune and srl. Even so my problem seemed to be the true in directx which should be falseQuote:
Originally Posted by Clarity
You need to download the Direct-X plugin from the links in that topic into your plugins folder before you can use it :pQuote:
Originally Posted by wister1
thanks again :DQuote:
Originally Posted by Clarity
Is anyone else having an issue running this script after the update? I had it running for about 20-30 minutes... then it all of a sudden just stopped working. After I tried restarting Simba, it asked if I wanted to change any settings.. so I hit no. Started it back up, now it just waits after login...
[Or it does thisQuote:
------ Succesfully initialized via spawning a new client
---- initSmart()
------ smartSetupDrawing(): Succesfully setup SMART drawing
---- Waiting up to 5 minutes for RS to load...
------ __setInputBoxes(): Set username and password boxes
---- Client is ready.
---- Setup SRL in 37125ms.
-- setupSRL(): True
-- Start custom SPS setup.
-- .init()
---- Path exists (maps\incandescent_wisps.png)
---- Setup area "incandescent_wisps" in 4294967311ms
-- .init()
-- End custom SPS setup.
-- TPlayer.login()
---- TPlayer.loginToLobby()
------ XxXxXxXxXx ()
------ Entering username...
------ Entering password...
-------- Saving screenshot: IP_address.png
------ Found lobby screen
---- TPlayer.loginToLobby(): True
------ TRSLobby.findPlayButton(): result = True
---- TPlayer.loginToLobby()
------ XxXxXxXxXx ()
------ Entering username...
------ Entering password...
Anyone else getting this? Already reinstalled simba/ updated everything...Quote:
---- Waiting up to 5 minutes for RS to load...
------ TRSActionBar.__findButton(): Found the actionbar button @ {X = 566, Y = 398}
------ TRSActionBar.__find(): result = true (height = 75)
------ Dynamic interfaces have been set.
---- Client is ready.
---- Setup SRL in 125ms.
-- setupSRL(): True
-- Start custom SPS setup.
-- .init()
---- Path exists (maps\incandescent_wisps.png)
---- Setup area "incandescent_wisps" in 4294967312ms
-- .init()
-- End custom SPS setup.
-- TPlayer.login()
---- Already logged in
---- Logged in:
-- TPlayer.login(): True
---- TRSMinimap.clickCompass(): Clicked compass
---- TRSGameTab.__initTabs(): Setup gametab properties
Excellent script, my paint problems aside.
Successfully gone 89-99 with very few issues.
Thanks!
was working finve earlier, now struggling to convert energys
I think the main problem of struggling to convert energys is caused by the update of the minimap icons, disabling the script of locating the energy rift.
I've been running the script flawlessly for the last three days, each time 8-10h (could've kept going, but stopped because I didn't want to bot for inhuman times). I'd bet it's something to do with your setup, although without more information I can't say for sure :\Quote:
Originally Posted by armys2hunt
The script at radiants will start to turn in the memories at the rift but it wont choose which way to turn them in.
---- Options found: [ConveM memories Energy RiM, Walk here, Examine Energy RiM, Cancel]
---- Found option "memories Energy" in "ConveM memories Energy RiM"
-- TRSChooseOption.select() result = true
Sometimes after collecting a full inventory the bot runs away from rift and basically back and forth for awhile before actually converting memories, is this part of antiban ?
it has some problems with brilliant wisps (lvl 80 ones). It fails alot while trying to click rift, sometimes he clicks on minimap like 3-4 times before finally being able to click on it, i think it might be because of the recent change to minimap icons.
Im getting better exp/hr in lustrous (lvl 70) than brilliant because of this, like 42k/h in the first ones vs 38k/h in brilliant
lvl 70 wisps are problematic for me... Bot cant detect when inv is full, and will continue to try and harvest when full up on memories
EDIT: began running it on "dont use minimap" mode and it works fine now. must be the icon update
Had a similar problem with level 80 wisps while running directX, script would bring player to rift but not convert. Don't use minimap solved the problemQuote:
Originally Posted by luxrath
I tried to use minimap but doesnt worked , what else did u changed?Quote:
Originally Posted by a ghetto boy
Quote:
Originally Posted by luxrath
_no_minimap is an unused variable...it has not been implemented, and you could delete it completely and the script can still be compiled.Quote:
Originally Posted by a ghetto boy
The symbol change doesn't affect the sps walking significantly as it has deformed tolerance.
hmmmm... after playing around with it some more it seems like running the script until it failed to convert, stopping and restarting the script w/o closing the SMART window is what solved the issue. I just assumed _no_minimap was helping because that was the last thing I changed.Quote:
Originally Posted by riwu
its broken after todays update, its stuck in a loop of opening bag tab and closing
yup can confirmQuote:
Originally Posted by wister1
3rd confirmation with meQuote:
Originally Posted by luxrath
any confirmation that it is now working since it was aparently fixed with a simba fix