[Worked: 3 H, 39 M, 27 S, XP: 153385, XP/HR: 41937]
Working fine!
Printable View
[Worked: 3 H, 39 M, 27 S, XP: 153385, XP/HR: 41937]
Working fine!
So far its great, except for one problem. Sometimes when converting, it will only convert a few memories before trying to harvest from a spring or wisp again. Otherwise its pretty good.
anyone can help me with this problem?
smartImage.debugATPA(ATPA);
[Worked: 27 H, 44 M, 11 S, XP: 1612755, XP/HR: 58146]
Nearly 99 xD yay
Can someone help me find the values for the gleaming wisps?
I guess I just need to go learn how to do the ACA colors and script in general...
Only been using it for around 20 minutes so far, but I'm impressed.
Went straight to the enriched spring as soon as it came onto the screen, no issues finding the rift, clicks it very quickly, good antiban. If it carries on without any issues I will definitely be using this to 99.
Chronicle support would be nice but I guess I can try and add that bit in myself, although I'm a bit rusty because I haven't edited any scripts in a couple of years now.
Thanks for the great script!
Got me from about 82-98 so far, getting around 75k/h at 98. Very satisfied.
great script
Try updating the vibrant wisps with these values.Code:
wispsVibrant: //NEEDS UPDATING *******************************************
begin
with self do
begin
wispName := 'ibrant';
mapName := 'vibrant_wisps';
imgurURL := 'http://i.imgur.com/E1X9HBT.png'; //needs image
color := 10193756; //needs color
tolerance := 24; //needs tolerance
hueMod := 0.38; //needs hueMod
satMod := 0.57; //needs satMod
enrichedColor := 15258754; //needs color
enrichedTolerance := 12; //needs tolerance
enrichedHueMod := 0.22; //needs hueMod
enrichedSatMod := 2.59; //needs satMod
siphonLoc := Point(144, 102); //needs Location
riftLoc := Point(131, 96); //needs riftLocation
menuOption := self.wispName;
end;
with riftDiv do
begin
wispName := 'Convert memories';
color := 5762996;
tolerance := 12;
hueMod := 0.36;
satMod := 1.29;
case Players[0].integers[riftOption] of
toEnergy: menuOption := 'to energy';
toExp: menuOption := 'to experience';
toBonusExp: menuOption := 'to enhanc';
end;
end;
end;
I couldn't quite get it working, as I'm new at this, but hopefully I got it started.
If someone could show me how to find the correct values, I would appreciate that.
Currently, the mouse goes from one wisp to the other very quickly and doesn't click on them. Any way to fix this?
Have a look at the ACA tool (Auto Color Aid). We use this to gather the best color settings for certain objects. It's a more advanced color picker that averages all your chosen colors into the 'most fitting.' You select colors simply by clicking on the pixel you want.Quote:
Originally Posted by chickenfoot911
I did, in fact I used ACA for these values. However, I'm not exactly sure how to choose the correct colors or tolerances.Quote:
Originally Posted by Clarity
The mouse goes to the wisps, but because they move, it doesn't click them.
I totally misread your post, of course you already used ACA - silly me!Quote:
Originally Posted by chickenfoot911
Do you mean the wisps are already in totally different places once the mouse has reached? If so, you could increase the mouseSpeed variable throughout the script.
Or, is it accurately moving toward the wisp location, and then doing nothing except try to mouse over another one?
If the mouse is correctly locating wisps, that suggests that your color values are OK.
Do you have mouse hover text enabled in RS settings?
The siphon logic appears to be (comments line by line):
Simba Code:function TDiv.siphonWisp: Integer;
var
i: Integer;
p: TPoint;
begin
if not(self.getPoint(p)) then Exit(resultNoWisps); //If it doesn't find a point from the color search, it skips this function entirely
mouseSpeed := 30; //Increase mousespeed
Mouse(p.rand(RandomRange(-8, 8)), MOUSE_MOVE); //Mouse to the wisp point with a randomness of (-8, 8) px
mouseSpeed := 20; //Change back mousespeed
if isMouseOverText([self.wispName], 100) then //If the mouse hover text matches the wisp name, then do the following
begin
GetMousePos(p.x, p.y); //Retrieve mouse coordinates
Mouse(p, MOUSE_RIGHT); //Right click
if chooseOption.select([self.menuOption]) then Result := resultSuccess else Result := resultWispMoved; //If it successfully picks the siphon option, result is set to 'resultSuccess'
minimap.waitFlag; //Wait for the flag to go away
end;
if Result = resultSuccess then //If it
waitWhileSiphon;
smartImage.clearArea(mainscreen.getBounds);
end;
I'm sure you understand most of it without the comments, but it's helpful to talk it out to figure out the problem.
If the mouse is arriving at a point that used to be a wisp, that means that self.getPoint() likely succeeded, and the problem isn't there.
Mouse overtext could be failing if it reaches the point, and then decides that the text isn't a match. Or, mouse overtext is succeeding, but self.wispName was never properly assigned. In this case, self.wispName is 'ibrant';
Perhaps the waitTime in mouseOverText (the 100 value) needs a slight increase, maybe to 200 or 300.
Have you properly filled out declarePlayers()?
Simba Code:procedure DeclarePlayers;
begin
{...}
integers[divLocation] := wispsIncandescent; //CHANGED TO wispsVibrant?
{...}
end;
Maybe a short GIF of the problem you are experiencing would shed a lot more light than speculating on the script logic :)
I understand most of it, but not all of it (without the comments)Quote:
Originally Posted by Clarity
I've been learning a lot of web development (JavaScript, PHP, Perl) but not all of it applies here. there's a lot of pre-defined libraries and functions I don't understand.
It would be awesome to have someone kind of guide me through making my first script, I have an idea or two of what i want to make.
That's a good catch with the declarePlayers form, I forgot to set it to vibrant so I'll mess with it more in the morning, and see if that fixes the problem.
I figured the riftLoc coordinates were the coordinates on the SPS map of the divination rift (minimap location) and the siphonLoc was the general area we want to siphon in?
Other than that, I just need more practice choosing colors and finding the right tolerance values, etc.
That would be the reason why it was failing then. Because it was set to the wrong wisp, it was constantly hovering over the Vibrant Wisps, seeing that the mouseOverText didn't match 'ncandescent', and moving onto another one endlessly.Quote:
Originally Posted by chickenfoot911
This also means that your vibrant colors weren't assigned either, so I guess incandescents (or whatever wisp you had incorrectly set) already have some similar colors to vibrants!
No worries about being new to this. You'll pick it up quickly. Feel free to post any more questions you have about anything on the forums :)
Thanks, you've been very friendly and helpful. I'll post an update tomorrow!Quote:
Originally Posted by Clarity
EDIT: I just ran a quick test once I updated the wispsVibrant in DeclarePlayers, and it started actually working. However it spazzed out and started clicking on the "Claim Treasure Hunter Key" tokens in my inventory, so I'll have to wait until tomorrow to spend those to get them out of my inventory. :)
I just tested these values, and they work for the Vibrant wisps so far (I've only run it maybe 10 minutes long)Code:wispsVibrant: //NEEDS UPDATING *******************************************
begin
with self do
begin
wispName := 'ibrant';
mapName := 'vibrant_wisps';
imgurURL := 'http://i.imgur.com/E1X9HBT.png'; //needs image
color := 10193756; //needs color
tolerance := 24; //needs tolerance
hueMod := 0.38; //needs hueMod
satMod := 0.57; //needs satMod
enrichedColor := 15258754; //needs color
enrichedTolerance := 12; //needs tolerance
enrichedHueMod := 0.22; //needs hueMod
enrichedSatMod := 2.59; //needs satMod
siphonLoc := Point(144, 102); //needs Location
riftLoc := Point(131, 96); //needs riftLocation
menuOption := self.wispName;
end;
with riftDiv do
begin
wispName := 'Convert memories';
color := 5762996;
tolerance := 12;
hueMod := 0.36;
satMod := 1.29;
case Players[0].integers[riftOption] of
toEnergy: menuOption := 'to energy';
toExp: menuOption := 'to experience';
toBonusExp: menuOption := 'to enhanc';
end;
end;
end;
But other than that, when I get to 70, I'll test the next level of wisps and post those values as well.
To use this, replace lines 524 to 555 with this code. Enjoy.
EDIT: Babysit this script until I find better values and upload a better SPS image.
After running it for about an hour, it got lost and ran to the coast to click on water.
@chickenfoot911 I have updated your colours and SPS map, ran for a couple of hours without fail. (Don't forget to delete your 'Vibrant_wisp.png' sps image in C:\Simba\Includes\SPS\img\runescape_other.
*Edit* It has been working flawlessly today with a light creature and scrolls, getting 45k+ xp an hour at vibrants.Code:wispsVibrant:
begin
with self do
begin
wispName := 'ibrant';
mapName := 'vibrant_wisps';
imgurURL := 'http://imgur.com/download/N4paaUz';
color := 6575923;
tolerance := 20;
hueMod := 0.06;
satMod := 0.14;
enrichedColor := 15258754;
enrichedTolerance := 12;
enrichedHueMod := 0.22;
enrichedSatMod := 2.59;
siphonLoc := Point(158, 218);
riftLoc := Point(202, 174);
menuOption := self.wispName;
end;
Not sure if it is the script or me but can't use Muspah, it spams the hotkey for the pouch even with a familiar. While it is using the rift, it constantly right clicks to convert into exp.
Thanks for the great script too @TomTuff. Repped.
Just another heads up guys, copy my colour above for Lustrous wisps, as the lustrous colour just sits and spams the light creature.
Can anyone teach me how to update values? I would like to add the values of gleaming, vibrant, lustrous and elder as BottingFTW your SPS map image seemed to not download for me?
Quote:
Originally Posted by BottingFTW
Worked for me, no idea why.
Updated the link, tested the download 5 times worked everytime, ensure you delete the previous file.
For your own colours, here is a link dude.Code:wispsVibrant:
begin
with self do
begin
wispName := 'ibrant';
mapName := 'vibrant_wisps';
imgurURL := 'http://imgur.com/download/N4paaUz/Vibrant_wisps';
color := 6575923;
tolerance := 20;
hueMod := 0.06;
satMod := 0.14;
enrichedColor := 15258754;
enrichedTolerance := 12;
enrichedHueMod := 0.22;
enrichedSatMod := 2.59;
siphonLoc := Point(178, 190);
riftLoc := Point(202, 174);
menuOption := self.wispName;
end;
https://villavu.com/forum/showthread.php?t=71074
What do I do about the map thing tho?Quote:
Originally Posted by BottingFTW
The updated script section I posted will download the new image for you. Ensure you delete the previous Vibrant_Wisps.png file in C:\Simba\Includes\SPS\img\runescape_other.
thanks for a great script, working well so far, 10 hours in
Thanks for the great script, added the blank ones in myself with maps if anyone is interested.
I am interested in the blank ones, would be awesome if you could help me. Thanks! <3Quote:
Originally Posted by no192
Same! could you please share it?
I too am interested
I've tried to post it twice, it hasn't been approved by the mods yet, posted them 2 days ago.
[edit]Ill try not using simba code (the tag).[/edit]
[edit2]just posted, waiting for mod approval[/edit2]
Just wanna say thanks for the script. Works flawlessly :D
Thank you :) Where will we be able to see it when a mod has approved it?Quote:
Originally Posted by no192
Can I please have some help I'm trying to add bright wisps I think the colors are correct but once its full it runs completely a different direction to where the rift is.
wispName := 'right';
mapName := 'bright_wisps';
imgurURL := 'http://imgur.com/download/5AeIaPL/Bright_wisps';
color := 10987364;
tolerance := 24;
hueMod := 0.39;
satMod := 0.53;
enrichedColor := 12489068;
enrichedTolerance := 17;
enrichedHueMod := 0.20;
enrichedSatMod := 0.51;
siphonLoc := Point(856, 335);
riftLoc := Point(894, 265);
menuOption := self.wispName;
end;
Wow, I am very happy to see that this script ended up getting lots of use!
Thank you VERY MUCH to everyone who posted progress reports and even to those who just gave the script a look. I was very happy with this script when I wrote it and got 99 with it, and I'm glad you were all able to use it too!
Thanks to @The Mayor for updating some scripts as SRL functions changed.
Does anyone know if this script is working currently? Can't test it myself, but I could help someone fix it up maybe if someone was so inclined?
You're script is working just fine :), all the supported wisp colonies work wonders. I've also added the colours and map for vibrant and lustrous, I could also add the rest of the locations and post it. And yeah thank you once again :)Quote:
Originally Posted by TomTuff
[Worked: 10 H, 10 M, 43 S, XP: 629908, XP/HR: 61885] Little proggy :). Awesome script only Muspah is little wierd. Spams spawn new familiar every second and also right clicks after every energy deposited. Without familiar perfect script.
Very nice script! getting those div gains ;)
Hey!
I've got a problem at luminous, it keeps walking south-east after converting memories, one time it just walked SE like always and then straight to the west and end up spam cliking on the minimap.
something is wrong, when I can't see the rift and got full backpack it fails and walks away (not always) or walks too far to east. It happens every time and it's really unnatural behaviour.Quote:
---- Found option "uminous" in "Harvest Luminous wisp"
-- TRSChooseOption.__select() result = True
[Worked: 0 H, 16 M, 52 S, XP: 0, XP/HR: 0]
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 32 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 16 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 16 ms
---- Waiting while the player is moving...
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 32 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 32 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 32 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 32 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 31 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 32 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 32 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 32 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 16 ms
-- sps.blindWalk(): result = True
[Worked: 0 H, 16 M, 53 S, XP: 0, XP/HR: 0]
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 31 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 16 ms
---- Waiting while the player is moving...
-- sps.getPlayerPos(): result = {X = 74, Y = 74}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 74}, took 16 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 74}, took 31 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 74}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 74}, took 16 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 70}, took 31 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 70}, took 16 ms
-- sps.getPlayerPos(): result = {X = 82, Y = 114}, took 15 ms
-- sps.getPlayerPos(): result = {X = 82, Y = 114}, took 31 ms
-- sps.getPlayerPos(): result = {X = 82, Y = 114}, took 16 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 16 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 31 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 16 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 31 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 16 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 16 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 70}, took 31 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 70}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 31 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 16 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 110}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 110}, took 31 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 110}, took 16 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 16 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 31 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 86}, took 16 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 86}, took 32 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 86}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 32 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 102}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 106}, took 15 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 106}, took 16 ms
-- sps.getPlayerPos(): result = {X = 74, Y = 106}, took 16 ms
-- sps.getPlayerPos(): result = {X = 82, Y = 102}, took 31 ms
-- sps.getPlayerPos(): result = {X = 82, Y = 102}, took 16 ms
-- sps.getPlayerPos(): result = {X = 82, Y = 102}, took 16 ms
-- sps.getPlayerPos(): result = {X = 82, Y = 74}, took 31 ms
-- sps.getPlayerPos(): result = {X = 82, Y = 74}, took 15 ms
Please fix this bot, I started to learn some coding but it will take me too much time to figure this out, which I don't have. After correcting rift coordinates it works better, but still crashes.
I'm having an issue with the bot repeatedly opening and closing the backpack every ~5 seconds. Everything should be set up correctly, from the interface to the graphics settings.
The following is printed to the console whenever the bot does this:
-- TRSChooseOption.__select() result = True
-- TRSGameTabs.openTab(2)
---- Opening tab via gametab navigation bar
-- TRSGameTabs.openTab(2): result = False
Any help is appreciated, thanks!
Wrong interface or graphic settings, it doesn't happen to me, can you provide a screenshot of your interface when you try to start the bot?Quote:
Originally Posted by Choomah
Sure, here's my interface: http://puu.sh/nw20Y/270c00b78b.jpgQuote:
Originally Posted by scob
And my graphics setup (have tried with OpenGL and DirectX): http://puu.sh/nw2aj/5f464e5c6a.jpg
Did you lock your interface customisation settings in interface window? Everything else seems to be right, I've got the same settings. Also try to change camera settings in control menu (classic - rs3) and try to set a "old School preset" preset in quick load layout menu and try to play with interface settings, hide slay counter, reset your script and s.m.ar.t etc. This bot has loads of errors atm but this one shouldn't appear
I resolved the issue-- my interface transparency was not entirely opaque. Thanks for the help!