if i want it to click on drop logs do i do chooseoption('rop')? cause thats not working for me someone help plz
Printable View
if i want it to click on drop logs do i do chooseoption('rop')? cause thats not working for me someone help plz
Post your script ?Quote:
Originally Posted by Brianb
First you need to move the mouse there , ;)
Hope this helps ..SCAR Code:Mouse(x, y, 3, 3, False);
Wait(100 + Random(100));
ChooseOption('rop');
~Eerik~
if you have already made it rightclick then you will want it to wait because SCAR is to fast for the rs client
so once you have made it rightclick make it wait 400+random(400) before calling ChooseOption
that way it will have time for the menu to appear
~shut
(400 + random (400)) is a bit too much imo .. but it depends on connection speed , too .Quote:
Originally Posted by Shuttleu
~Eerik~
i use 400+random(400) all the time and it seems fast and reliable to meQuote:
Originally Posted by heavenzeyez1
never missed a ChooseOption ever :D
~shut
tbh i'm using (100 + random(51)) and i've never failed , it's like almost 6 times faster , too ? :OQuote:
Originally Posted by Shuttleu
But nvm , what matters, is that it won't miss it . ;)
~Eerik~
Lol. I use Wait(75);
I don't see a need for randomness =]
I'm a fast clicker.
without randomness you will get banned very quicklyQuote:
Originally Posted by TheVoiceInYourHead
something you should note
always use randomness
ALWAYS!!!
~shut
Have you ever been banned for not using randomness?
yes for stuffff like Mouse(234,234,0,0,true); and Wait(100) ect.
So you've been banned for that?
Show me proof where JaGex said: "You have been banned for not using random mouse movements."
My main was banned exactly for that reason , so Sshh. :) (Well , they didn't write it , but i know what i did . ;) , ALWAYS use randomness . :)Quote:
Originally Posted by TheVoiceInYourHead
~Eerik~
No, you don't know what you did.
You assume that's what you did. When in reality, it wasn't your fault at all.
well if it wasnt his fault then why did he get banned?Quote:
Originally Posted by TheVoiceInYourHead
~shut
If you're using a script, it's not your fault.
but...Quote:
Originally Posted by TheVoiceInYourHead
1. if he made the script himself then it was his fault for not using randomness
2. he used the script at his own risk, so if he didnt use it then he wouldnt have got banned, therefore it was his fault
but anyway lets not turn this into an argument
~shut
procedure droplogs;
begin
if (findcolor(x, y, treeininvcolor, 0, 0, 1000, 700)) then
begin
mouse(x, y, 5, 5, false);
wait(5000+random(500));
chooseoption('rop');
end;
end;
still doesn't work
why don't you use dtm's, its alot more reliable, or just use the srl drop function that works pretty good for me
ok whats the srl drop function? :)
ok i made a whole new script just for you guys
program New;
{.include srl/srl.scar}
var
x, y:integer;
begin
setupSRL;
if (findcolor (x, y, 4358821, 552, 210, 730, 459)) then
mouse(x, y, 5 ,5, false);
wait(2500+random(500));
if chooseoption('rop') then
writeln('script succesfull')
else
writeln('not found')
end.
and this was the debug box:
Successfully executed
Successfully compiled (3357 ms)
SRL Compiled in 16 msec
not found
Successfully executed
Successfully compiled (3325 ms)
SRL Compiled in 15 msec
not found
Successfully executed
any help?
There's actually a built-in scar function in the inventory scar script. I'm finding it now.
ED: Here's something quick I cooked up:
SCAR Code:program New;
{.include SRL\SRL.scar}
const
LogColor = ''; //Color of the log you want to drop.
var
x, y: Integer;
begin
SetupSRL;
ClickAllItems(LogColor, 'color', 'Drop', 120, [0]);
end.
You just need to change the const LogColor to the color of the log. Make sure it's a unique color only to that type of log. I recommend using DTMs though.
If you want to use Bitmaps, however, use this:
SCAR Code:program New;
{.include SRL\SRL.scar}
const
LogName = ''; //Normal, Oak, Willow, Maple, or Yew
var
x, y, LogBMP: Integer;
begin
SetupSRL;
case LowerCase(LogName) of
'normal': LogBMP := srl_GetBitmap(56);
'oak': LogBMP := srl_GetBitmap(57);
'willow': LogBMP := srl_GetBitmap(58);
'maple': LogBMP := srl_GetBitmap(59);
'yew': LogBMP := srl_GetBitmap(60);
end;
ClickAllItems(LogBMP, 'bitmap', 'Drop', 120, [0]);
end.
did it move the mouse to the log? If not then its your colors, not the srl chooseoption thingy
imo, if you're not going to use scar's drop function, I would use like a DDTM with a case situation for the main log color so that way you don't have to have multiple dtm's or bmp's, just my opinon though.
bobbohobbo has a good walking DDTM tut that you could probably figure out how to use them from that Here
Like:
Also don't pick too high of a tolerance or it may end upCode:function FindLog(LogUsed:String;var cx, cy; x1, y1, x2, y2: integer) boolean;
var
(your variables for the ddtm)
begin
case logused of
'log': logcolor:= 5;
'oak': logcolor:= 6;
end;
setarraylength(logsp,2);
dtmMainPoint.color:= logcolor;
(all the rest of the mp junk too)
(then just leave all your subpoints alone and just make sure
that the color is black.)
(add this to the bottom)
Log:=AddDTM(TempTDTM);
result:=findDTM(Log,rx,ry,x1,y1,x2,y2);
freeDTM(Log);
dropping a log it's not supposed to which isn't bad if you want to drop all. You
could also use this if you wanted to burn logs or fletch them.
then all you need to do is add it into whatever procedure you need it to do such as your burning and fletching or just droping instead of that findcolor that you used you would use the function you made.
Lol. You don't need a DDTM for a static object. Especially with logs, because all logs are the same shape, just the main point are different colors. I suggest using plain old DTMs or the DropTo function =]
If you use a DDTM you don't have to make a bunch of dtm's you only have to make one DDTM and then use the case to assign the midpoint color, which is what I suggested.