SRL Archive - RS3 Outdated / Broken Scripts

Right guys, I haven't made a script in a long time, so here you go!

Update:

v1.1 - Fixed dtms and antiban. Runs smoother!
v1.2 is up! Willows supported, EOC Bonfire! Runs slightly more smoother!
v1.3 Should run much smoother, added a change in angle and a failsafe if you get stopped from lighting and if it cannot find you chopping. Feedback please!
v1.4: Fixed some basic compiling errors, now burns and chops properly

Download:
V1.4 [ATTACH]17872[/ATTACH]

With the come of the new EOC update, many scripts have been broken.
This now supports Maples and Willows in the Daemonheim Resource Dungeon.

Tell me if you guys want some more locations, IDK. I might update it for that.

Oooh, nice :). Am I really the first one to post here? :redface:

Your burn procedure could use some indenting :p

You are lol! I had a ton of downloads though. On the original script version 1.1
Nobody posted feedback though :(

Congratz!
~Rez

Edit: Yea, I just couldn't be bothered right now :p Ill spruce it up in the next update :p

Proggies are commented out in your script :p would have shown you an awesome 10 minute one but I just changed it now

:p I have no idea how to handle the proggies. Like especially the XP's. I know I could use the GetXP Function, but it didn't work for me. So took it out all together :D

Though, I have run both maple and willow parts for over 2hrs each, so I know they work for now.
~Rez

I'm on my phone now but I'll see if I can make one quickly :D

I'll edit this post unless you post after :)

You know I love you right? <3
~Rez

Here ya go :), still running

/////////////////////////Rez's MapleResourceDung!//////////////////////////
//Time Running: 20 Minutes and 40 Seconds
//Number of Logs chopped: 84 (243 P/H)
//Number of Logs burnt: 84 (243 P/H)
//Woodcutting XP Gained: 8400 (24387 P/H)
//Firemaking XP Gained: 3780 (35361 P/H)
//Number of Loads done: 3 (8 P/H)
////////////////////////////////////////////////////////////////////////////////

Two suggestions. you could use invmouse(invslot,action); for clicking your logs in your inv. This would be more failsafe then relying on the log to remain the same. the other one is you have a

repeat
  Until(InvEmpty);  

in your burn. what happens if you get a spin ticket, or other item in your inventory? You will just sit there till you log out. Also, what happens if you light a fire, but start adding logs to some other fire, and it goes out?

Great work!

Ooh, thanks Ether and BMWXi!

For^^^ The whole point of the dtm is so it doesn't randomly click a non log, in case it does something to throw off the script. Also, im pretty sure you don't get spin tickets for burning logs. I might be wrong though.
As for if the fire goes out, you are right if it goes out. But it can't, cause you are adding logs right? ;)
~Rez

I think log burning time is constant, so you should make the burn procedure do this:

Until(InvEmpty) Or (TimeFromMark > 80000);

replace 80000 with a bit more that the normal time. Sorry for not simba tagging, I'm on my phone.
Also I'm just going from memory, so your script may already have a failsafe for this. :p

From: BMWxi
I think log burning time is constant, so you should make the burn procedure do this:

Until(InvEmpty) Or (TimeFromMark > 80000);

replace 80000 with a bit more that the normal time. Sorry for not simba tagging, I'm on my phone.
Also I'm just going from memory, so your script may already have a failsafe for this. :p

Wait, I still don't understand the need for these. Like once you add a log to the bonfire, it makes it last longer. So why would it burn out, and just sit there?
Also, I don't think you get spin tickets, but if you do, Ill add something like this^^^ or something else as a failsafe.
~Rez

This needs a failsafe somewhere after it tries to light a fire. It failed to light a fire somehow and I caught it stuck with a full inventory not trying to chop or burn. The last in-game message showed that it had tried to light the bonfire "there is no bonfire around to add logs too" but the script didn't do anything after it failed to bonfire.

Edit: Script is still running, although it seems to take a while to decide/successfully begin chopping as well.

^^^Yea…Adding some new features+failsafes. Gonna release it this Friday? Maybe Saturday, at the latest.

From: Rezozo
Wait, I still don't understand the need for these. Like once you add a log to the bonfire, it makes it last longer. So why would it burn out, and just sit there?
Also, I don't think you get spin tickets, but if you do, Ill add something like this^^^ or something else as a failsafe.
~Rez

You get tickets from mining so I'd assume you'd also get them from wood cutti. ng. FindNormalRandoms will use them tho so nvm. And for the thing I posted, you would mark the time once you began burning logs, and the time would not reset until it had finished burning an inv. I'll make an example an post it

If you replace

Until(InvEmpty)

with

Until(InvEmpty) or (TimeFromMark(BurnWait) > 80000);

and add

MarkTime(BurnWait);

right before

Count:=Count+28;

and add

BurnWait

into the global variables, it will bun the logs until your inventory is empty or 80 seconds has elapsed since the start of the burn procedure. 80 seconds might not be the right amount of time though.

From: BMWxi
You get tickets from mining so I'd assume you'd also get them from wood cutti. ng. FindNormalRandoms will use them tho so nvm. And for the thing I posted, you would mark the time once you began burning logs, and the time would not reset until it had finished burning an inv. I'll make an example an post it

Yea, the script works fine if you get a spin ticket while chopping, itll just click it and move on. What is the point of marking the time? I was thinking of something similar to the isChopping function, to check for pixel shift, when chopping.
~Rez

From: Rezozo
Yea, the script works fine if you get a spin ticket while chopping, itll just click it and move on. What is the point of marking the time? I was thinking of something similar to the isChopping function, to check for pixel shift, when chopping.
~Rez

It would be only if for some reason if it stopped while burning, or got a strange rock(p2p) while burning.

Oh yea, strange rocks. What is that even used for, is that even worth keeping? Should I keep a drop on that? Adding functionalist for the Spin Ticket soon.
~Rez

From: Rezozo
Oh yea, strange rocks. What is that even used for, is that even worth keeping? Should I keep a drop on that? Adding functionalist for the Spin Ticket soon.
~Rez

Idk, it's a p2p d&d that gives you xp wben you bring it to varrock museum. Probably just drop.

Yea, I think Ill do that. Thanks!
~Rez

Another bug that I noticed is that occasionally it will get blocked from view by maple branches so pixelshift gets confused and looks for a new tree. Not script breaking, just something to note :p

Yea, I thought about that. For now, Im looking for the best possible angle so as to see the colors properly ( or get new ones) as well as see the player properly, with enough trees in view.
~Rez

I'd go with horizontal and random camera rotation if no tree is found.

Hmm, That might be good. Ill look into that! Thanks :D
~Rez

What I do for a burn failsafe is look for the invcount to decrease. if you don't burn a log, your invcount does no go down. For your convince, I have posted my burn procedure. Please note, my burn procedure does not take strange rocks into account, as I am F2P. Feel free to use stuff from the procedure as long as credit is given where credit is due.

Procedure Burn;
Var
  I,IC,K:integer;
Begin
  K:=0;
  Wait(RandomRange(BurnWait,1000));
  if bankscreen then
    exit;
  I:=0;
  repeat
    inc(I);
  until ExistsItem(I)
  if ExistsItem(I) then //tinderbox start
    begin
      invmouse(I,1); //clicking log
      wait(randomrange(100,200));
      mmouse(400,400,200,200);
      mouse(200,430,25,25,true);
      wait(BurnWait+Burnwait+Random(1000));
    end;
  I:=0;
  repeat
    inc(I);
  until ExistsItem(I)
    if ExistsItem(I) then  //adding to bonfire
    begin
      invmouse(I,1); //clicking log
      wait(randomrange(100,200));
      mmouse(400,400,200,200);
      mouse(300,430,25,25,true);
      wait(BurnWait+Burnwait+Random(1000));
    end else
      burn;
    I:=invcount;
    K:=0
    repeat
    inc(K);
    wait(burnwait);
    if invcount<I then
      begin
        I:=invcount;
        K:=0;
      end;

    if K>2 then
      Burn;
    if IsChatBoxTextAnyLine (threelet,clBlue) then    //name detection (replace threelet with 'ohn' if your username was JohnDoe
        begin
          writeln('Someone said your name, logging out to be safe');
          logout;
          TerminateScript;
        end;
    until invcount=0
  if invcount=0 then
    writeln('Burned correctly') else
    Burn;
End;           

I will give full credit too you for the idea, as I don't think I will take parts from your script.
:D
Basically, I try to do things the simplest way possible, to my understanding. Yours is slightly complicated. But I will take the idea for checking if there is one less log in the inventory!
Ill add a check for strange rocks in between to drop.
~Rez

To anyone who could help, anyone got a current picture, in game(fixed min) of a strange rock? If you could get that screen shot, I would love you <3
~Rez

you probably could do a simple uptext check for the strange rock. I suppose my burn procedure is a bit complicated, but if it an't broke, don't fix it right…

Amen to that^^^
I think Ill do that for the strange rock, or maybe just search for something of that color in the inventory every now and then.

Added the function for firemaking, sure fire for now :)
Currently implementing a safe way of turning the angle if not chopping. The only problem is I need a pre defined way of checking, a good enough algorithm, so that it looks calculated, but is random.
For now, im trying SetScreenMouse('Random', random(10)+1);
Ill see how it goes :p
Got a party today and tomorrow, but I will probably release it tomorrow in the morning :)
~Rez

Updated! Tell me how it is! Could anyone help a guy out with the progress report? My latest one is updated, tell me how that is. Still adding the feature for Strange Rocks.
~Rez

i'm having trouble getting the script to run properly. I'm cutting willows, and it seems to find them and cut the first tree, but after i cut the tree down it doesn't do anything. Also, when i have a full inventory it automatically tries to add to a fire, and never creates one. What could be going wrong?

Thank you for your feedback. A new version is now uploaded, that should fix it.
~Rez

Added the banner:

Made by DannyRS. Thank you so much!
~Rez

Thanks for the update, everything is running smoothly now. I noticed I can't have an axe in my inventory though, or else the inventory will never be empty and it wont realize when the burning is done. Do you know of any changes i could make to account for that?

Edit: I figured it out, it just took changing (InvEmpty) to (invcount=1).

From: Rezozo
Updated! Tell me how it is! Could anyone help a guy out with the progress report? My latest one is updated, tell me how that is. Still adding the feature for Strange Rocks.
~Rez

Progress report is kinda simple, i see two basic ways of doing it, count logs you aquire/burn with invincreasing count or a full inv * xp of an inv,

Or use a XP bar grabber if your lazy like me :)

I can help with anything you need tomorrow after college if you like :)

I wanna try the XP counter. It looks cooler. Also, when I tried it (in the very first version of my script), it didn't work. But I think that was on the skills tab, not the popup counter itself…Oh well.
ttyl
~Rez

I only go with the xp counter for skills that you have no other exact way of counting, like combat. For yours just add 28 to the amount of logs burnt/logs cut every time it burns an inventory. You could try using the bar, it is 100% accurate, but it is annoying for the user to set up if they don't need to.

Logs := Logs + 28

From: BMWxi
I only go with the xp counter for skills that you have no other exact way of counting, like combat. For yours just add 28 to the amount of logs burnt/logs cut every time it burns an inventory. You could try using the bar, it is 100% accurate, but it is annoying for the user to set up if they don't need to.

Logs := Logs + 28

Lol, I thought of doing that, but the XP counter one looks cool :(
What if I make the script set it up for him? That shouldn't be bad right?
~Rez

From: Rezozo
Lol, I thought of doing that, but the XP counter one looks cool :(
What if I make the script set it up for him? That shouldn't be bad right?
~Rez

Yeah, that should be fine. Nice banner btw, DannyRS has some skill :D

Thanks to him again :D
Il get to adding that tomorrow maybe. Anything else I should add, hopefully you guys would post that here.

Suggestion one from me (Thinking about doing): Adding ChopNBurn and Banking in Draynor or some other nice place. For now, adding one place shouldn't be too hard.

Good night guys!!!
~Rez

From: Rezozo
Thanks to him again :D
Il get to adding that tomorrow maybe. Anything else I should add, hopefully you guys would post that here.

Suggestion one from me (Thinking about doing): Adding ChopNBurn and Banking in Draynor or some other nice place. For now, adding one place shouldn't be too hard.

Good night guys!!!
~Rez

May as well bank in Daemonhiem, Tele there and run back. Or Al Kharid is pretty close too.

I was thinking of adding some other place besides the resource dungeon. I want to keep that bonfire only, don't want to crash those maples right? ;)

Might also add varrock oaks, then move on to yews? Also need to check up on some TuTs of the progress reports, and using the XP bars.
~Rez

Dang man.. I was going to make this, but also add fletching them into longbows and dropping using the action bar… Beat me to it. Danggggg

<3 Still love ya.

Hmm, do you know if my thing here even works anymore? :p
Cause if it doesn't, or if you really want to, you could take over for me, or just take this code and add on your part for a new program.

Idk, I stopped playing RS all together, so I have no real interest in this. Forgot most of pascal already :p
~Rez

dose this work as of now ?

From: happy hippo
dose this work as of now ?

Truthfully? I don't know. I don't really play RuneScape anymore, much less script making
Test it out I guess, though im sure there were definitely some new updates that would render some parts here unusable.
~Rez

From: Rezozo
Truthfully? I don't know. I don't really play RuneScape anymore, much less script making
Test it out I guess, though im sure there were definitely some new updates that would render some parts here unusable.
~Rez

aww thats a pity i tried it out and it dosent burn the logs. script is wayy to complex to try implement a burning procedure, would thee any hope of an update to working condition in the near future?

From: happy hippo
aww thats a pity i tried it out and it dosent burn the logs. script is wayy to complex to try implement a burning procedure, would thee any hope of an update to working condition in the near future?

Hmm, I haven't really done pascal in sometime. However, I specifically remember keeping this script the most simplest I could, with the simplest of functions etc. In fact, the 'function' part should still work. You say the burning doesn't work, does everything else work? I would take a look at it later, after my exams are over, if it helps.
~Rez

From: Rezozo
Hmm, I haven't really done pascal in sometime. However, I specifically remember keeping this script the most simplest I could, with the simplest of functions etc. In fact, the 'function' part should still work. You say the burning doesn't work, does everything else work? I would take a look at it later, after my exams are over, if it helps.
~Rez

Yeah Man That Would Be Cool Thanks

burning is still broken