SRL Archive - RS3 Outdated / Broken Scripts

Known Bugs & Issues

---

• Script will sometimes rotate too far while standing at the furnace
• Walk failsafe doesn't appear to work correctly

TODO List

---

• Everything that will be included in 2.0 :p

Setup Instructions
IMPORTANT: Failure to follow these instructions will result in a PEBCAK error!

---

1. Ensure that you have properly installed and setup Simba for RS3
2. Check that Simba is using Lape (in Simba, Script > Interpreter > Lape)
3. Check that your Display Mode is set to OpenGL OR DirectX (in RuneScape, Settings > Graphics > Custom > OpenGL/DirectX)
4. Set bank preset with (ONLY) the amount of ore required for one pack of bars
5. Empty the action bar
6. Remove ALL UI from the main screen and move the exp tracker to the chat box (as seen in the spoiler below *)
7. Download and run the attached updater script
8. Download Inc_Lude.simba and place it in the newly created Includes/Inc_Lude/ folder
9. Open the newly downloaded script (IncsSmelter_x.x)
10. Hit run, fill out the form, and click start
11. Do something productive with your life while the game is automated
12. Post any progress reports, bugs, and suggestions! :D

* Exp tracker in chat box:


Ore Number Chart:

{¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯|¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯|
|        PRIMARY NUMBERS        |    COAL NUMBERS   |
|-------------------------------|-------------------|
|  Bronze - 14  Steel      - 9  |  Steel      - 18  |
|  Iron   - 14  Mithril    - 5  |  Mithril    - 20  |
|  Silver - 28  Adamantite - 4  |  Adamantite - 24  |
|  Gold   - 28  Runite     - 3  |  Runite     - 24  |
|_______________________________|___________________}

Progress Reports

---

[spoiler=Progress Reports]

By Incurable - 22nd Nov, 2014
NOTE: Issue with recoveries debugged, should be fixed in 1.3 :D
 ??????????????????????????????????
 ?   Inc's Lumby Smelter v1.21    ?
 ??????????????????????????????????
 ? Bar Type      - Steel          ?
 ? Loads done    - 449            ?
 ? Smelted       - 4041           ?
 ? Smelted/hr    - 539            ?
 ? Profit        - 876897         ?
 ? Profit/hr     - 116859         ?
 ? Experience    - 1354           ?
 ? Experience/hr - 180            ?
 ? Recoveries    - 62             ?
 ? Breaks Taken  - 3              ?
 ? Break Time    - 56m 00s        ?
 ? Total Time    - 07h 30m 13s    ?
 ??????????????????????????????????

By Stopkiller - 20th Nov, 2014

By Stopkiller - 25th Nov, 2014
[/spoiler]

Change Log

---

Version 1.2.1
- Fixed an issue where findFurnace() would return false despite being successful

Version 1.2
- Fixed an issue with the proggy failing to print the total break time
- Fixed an issue where the profit/hr calculation would be incorrect after an uncertain period of time
- Added a workaround for the screen height lowering over time (Jagex anti-bot?)
- Added "Bar Type" to the progress report
- Added debugging to the break() calls in MainLoop() in an attempt to figure out what the shit is going on

Version 1.1
- Fixed an issue where the BreakHandler would break for milliseconds at a time, not minutes (thanks 3Garrett3)
- Added an optional "world" setting

Credit

---

• <3 @3Garrett3 - A hell of a lot of script testing and feedback
• <3 @slacky - Script feedback and function help
• <3 Coh3n - Thread layout
• <3 Everyone else who helped me with small bugs and ways to do what I needed

NOTE: You DO need to download Inc_Lude.simba and place it in Includes/Inc_Lude/. You do NOT need to download the map. If the map does not download for some reason when you run the updater, download it manually instead.

Map:

Congrats on release, looking forward to using it.. So, do you apply for members now ;)

Yay! Gratz

It seems to go on break for "0.00065 minutes" or so after every load, it logs out logs back in and home teles to lumby.

From: stopkiller
Yay! Gratz

It seems to go on break for "0.00065 minutes" or so after every load, it logs out logs back in and home teles to lumby.

That's… incredibly weird. o.O

I must have done something to break breaking before I uploaded it. I'll fix it tonight, thanks for the report!

Congrats an zee release! Like the thread layout as well.

Congratulations on the release!

Congrats on the release! :D

From: stopkiller
Yay! Gratz

It seems to go on break for "0.00065 minutes" or so after every load, it logs out logs back in and home teles to lumby.

Should be fixed, run the updater again and let me know! ;)

Seems fixed :) I'm gonna run it for 14+ hours while I'm at work so I'll let you know with a proggy :P

[ATTACH=CONFIG]24475[/ATTACH]

From: stopkiller
[ATTACH=CONFIG]24475[/ATTACH]

Thank you for the report, it would seem that I've got some fixing to do… 22 recoveries, a negative prof/hr, and no break time printed. o.O

EDIT: Did you stop it manually or did it finish successfully? Also, what ore did you smelt? It looks like steel judging by the report.

Finally, I've just realised that I didn't explain how to fill out the form properly in my OP, have you been following the instructions in the script?

Thanks. :)

Actually I was smelting Iron, using rings of forging. I told it to make 10,000 bars and it made almost 10,000. Yeah it stopped itself, I didn't manually stop it. It works, it just likes to tele to lumby lodestone a lot :P

I followed all instructions, only one I didn't follow is I put bars per pack to 28 since I was smelting iron bars with rings of forging.

From: stopkiller
Actually I was smelting Iron, using rings of forging. I told it to make 10,000 bars and it made almost 10,000. Yeah it stopped itself, I didn't manually stop it. It works, it just likes to tele to lumby lodestone a lot :P

I followed all instructions, only one I didn't follow is I put bars per pack to 28 since I was smelting iron bars with rings of forging.

That's fine, bars per pack is used to increment the number of bars that have been smelted and to accurately reflect that in the progress report (as well as to end the script when the desired amount of bars is done). The reason that I have the suggested number at 14 is because iron has a 50% fail rate at level 15, so it was just a quick estimate for the competition. I'm changing all of those things in future versions. So with that said, 28 is what you were supposed to do, and I'm glad it worked. :D

Version 1.2 will be up in an hour or two and it will fix a few bugs and add debugging to the main loop so I can see what's causing it to recover. Version 1.3 will be up later tonight and will include an accurate bar counter (including iron bars) without the need to put in how many bars you smelt per pack, among other things. :D

Version 1.2 is out, change log:

Version 1.2
- Fixed an issue with the proggy failing to print the total break time
- Fixed an issue where the profit/hr calculation would be incorrect after an uncertain period of time
- Added a workaround for the screen height lowering over time (Jagex anti-bot?)
- Added "Bar Type" to the progress report
- Added debugging to the break() calls in MainLoop() in an attempt to figure out what the shit is going on

IMPORTANT: Follow these steps to get the latest version. This only has to be done once (to update from 1.0 or 1.1 to 1.2, this will not be required for 1.2 to 1.3 and onwards for the foreseeable future):

1. Delete Inc_Lude.simba, IncsSmelter_updater.simba, and IncsSmelter_1.x.simba
2. Download the NEW version if IncsSmelter_updater.simba from the OP
3. RUN THE UPDATER BEFORE PROCEEDING TO STEP 4
4. Download the new version of Inc_Lude.simba from the OP and place it in Includes/Inc_Lude - If you do not also have a folder named "logs" inside the Inc_Lude folder, either you or myself have done something wrong… please let me know if the updater did not create that folder!

If you follow those steps then you will have 1.2 and the dreaded PEBCAK error will have been avoided.

Let me know if this fixes everything!

From: Incurable
Version 1.2 is out, change log:

Version 1.2
- Fixed an issue with the proggy failing to print the total break time
- Fixed an issue where the profit/hr calculation would be incorrect after an uncertain period of time
- Added a workaround for the screen height lowering over time (Jagex anti-bot?)
- Added "Bar Type" to the progress report
- Added debugging to the break() calls in MainLoop() in an attempt to figure out what the shit is going on

IMPORTANT: Follow these steps to get the latest version. This only has to be done once (to update from 1.0 or 1.1 to 1.2, this will not be required for 1.2 to 1.3 and onwards for the foreseeable future):

1. Delete Inc_Lude.simba, IncsSmelter_updater.simba, and IncsSmelter_1.x.simba
2. Download the NEW version if IncsSmelter_updater.simba from the OP
3. RUN THE UPDATER BEFORE PROCEEDING TO STEP 4
4. Download the new version of Inc_Lude.simba from the OP and place it in Includes/Inc_Lude - If you do not also have a folder named "logs" inside the Inc_Lude folder, either you or myself have done something wrong… please let me know if the updater did not create that folder!

If you follow those steps then you will have 1.2 and the dreaded PEBCAK error will have been avoided.

Let me know if this fixes everything!

I would suggest you make the update steps a bit less complex, a one step update would be much more convenient, I personally would never bother.

From: Frement
I would suggest you make the update steps a bit less complex, a one step update would be much more convenient, I personally would never bother.

This only needs to be once, I made a bunch of changes today so the updater and include need updating. Tbh though, if someone cbf taking 2 minutes to follow 4 steps then it's their loss, not mine. :p

EDIT:

Quick update to version 1.2.1 (version 1.21 in script + version.txt, an unintentional side effect of not wanting to make this 1.3, lol), only one change.

Version 1.2.1
- Fixed an issue where findFurnace() would return false despite being successful

To update from 1.2 to 1.2.1, just run the updater again. If you haven't followed the steps from earlier at all and still have version 1.0 or 1.1, follow them, it should automatically download 1.2.1 instead of 1.2.

After smelting a good 15k iron bars, I took a look through the debugging info in simba, it seems that almost all of the recoveries were caused by
"ERROR: Failed to find enough good bank chest edges
TRSBankscreen.__openChest(): result = false
TRSBankscreen.__openChest()"

The rest were caused by failing to find the furnace but I didnt update to 1.2.1 before I ran this so.
Here is a link to imgur album
http://imgur.com/a/S2nFn

the ones after the proggy were some ones I picked from your logs folder, the first one is fail to find chest, the second one is fail to find furnace

From: stopkiller
After smelting a good 15k iron bars, I took a look through the debugging info in simba, it seems that almost all of the recoveries were caused by
"ERROR: Failed to find enough good bank chest edges
TRSBankscreen.__openChest(): result = false
TRSBankscreen.__openChest()"

The rest were caused by failing to find the furnace but I didnt update to 1.2.1 before I ran this so.
Here is a link to imgur album
http://imgur.com/a/S2nFn

the ones after the proggy were some ones I picked from your logs folder, the first one is fail to find chest, the second one is fail to find furnace

@Incurable, This seems like exactly the problem you thought it was. The flag is still there in one of the pictures on the way to the furnace, so the fix you thought of should work for that. The other one (not finding bank) may be due to the angle not being proper? You'd have to look a little deeper into that one I think.

From: stopkiller

Nice proggy!

That's a lot of recoveries, but 40 in 18 hours isn't as bad as it could be. I'm 99% sure that I know what's causing useBank() to fail, and findFurnace() shouldn't be failing any more. Can you do me a favour and check Inc_Lude/logs for the screenshots from that run and estimate how many of them are for useBank(), how many are for findFurnace(), and whether there's any others? If you could post a couple of the weird ones that would be good too (eg, useBank() failing while standing at the chest).

Thanks mate, with your help I'll have it fixed and release 1.3 tomorrow! :D

PS: Please don't get banned, my scripts are by no means perfect and an 18 hour run is huge. >.<

The error in the images is listed as "inc_sm_error_walkPath_BankToFurn"

From: stopkiller
-snip-

Sorry I didn't see this until now, if you could quote or mention me in your posts then I'll get a notification for it and notice it straight away. >.<

Anyway, I really dislike the frequency of those screenshots based on the times, but thank you so much for posting so much detail. I'll fix it in 1.3 tomorrow, hopefully. In the mean time, please be careful about using this script, it's obviously stable enough to run for hours, but only because it has a solid recovery system built into it that allows it to recover so often. :unsure:

I tried it with the original client, didn't work.

---- ERROR: Failed to find enough good bank chest edges
-- TRSBankscreen.__openChest(): result = false
================================================
DEBUG: REPORT - useBank() failed
DEBUG: REPORT - Saving a client screenshot to "C:\Simba\Includes\Inc_Lude\logs"
---- Saving screenshot: inc_sm_error_usebank.png
DEBUG: REPORT - Screenshot saved continuing...
================================================

Is the SRL chest finder function outdated maybe?

From: Torol
I tried it with the original client, didn't work.

---- ERROR: Failed to find enough good bank chest edges
-- TRSBankscreen.__openChest(): result = false
================================================
DEBUG: REPORT - useBank() failed
DEBUG: REPORT - Saving a client screenshot to "C:\Simba\Includes\Inc_Lude\logs"
---- Saving screenshot: inc_sm_error_usebank.png
DEBUG: REPORT - Screenshot saved continuing...
================================================

Is the SRL chest finder function outdated maybe?

What do you mean by "the original client"? Also, check the screenshot that it saved, if the bank chest isn't visible then wait for version 1.3 (writing it now, will release tomorrow), else make sure that you've got the latest version of SRL (at the top of Simba, SRL > Check for Update). Ashaman88 made improvements to it a week ago and I haven't had a single issue with it since.

From: Incurable
What do you mean by "the original client"? Also, check the screenshot that it saved, if the bank chest isn't visible then wait for version 1.3 (writing it now, will release tomorrow), else make sure that you've got the latest version of SRL (at the top of Simba, SRL > Check for Update). Ashaman88 made improvements to it a week ago and I haven't had a single issue with it since.

I just commented out the smart-related lines (that should not cause any problems, should it?)

From: Torol
I just commented out the smart-related lines (that should not cause any problems, should it?)

I don't believe so. I'm quite sure that I've already fixed the issue you're having, but if you check your screenshot then I'll know for sure. :)

From: Incurable
I don't believe so. I'm quite sure that I've already fixed the issue you're having, but if you check your screenshot then I'll know for sure. :)

Sure, here it is:

From: Torol
Sure, here it is:

Err, did you blur everything intentionally? The black I can understand, but why blur everything too? :p

What version of the script are you using? The camera is zoomed in, but I fixed that in 1.2… also, have you got the latest version of SRL?

From: Incurable
Err, did you blur everything intentionally? The black I can understand, but why blur everything too? :p

What version of the script are you using? The camera is zoomed in, but I fixed that in 1.2… also, have you got the latest version of SRL?

I didn't blur anything, thats the RS graphics on Direct X minimum for me, the black squares were intentional of course :p
It says it's version 1.21, I don't know why it zooms, I was surprised too. The SRL is up to date too. Well, I guess I will try it again with the 1.3 when it comes out!

From: Torol
I didn't blur anything, thats the RS graphics on Direct X minimum for me, the black squares were intentional of course :p
It says it's version 1.21, I don't know why it zooms, I was surprised too. The SRL is up to date too. Well, I guess I will try it again with the 1.3 when it comes out!

I totally believe you, so don't take this the wrong way, but if you can double check your graphics settings then we can rule out that "blur" as being a problem. Is it actually blurry, or are my tired eyes just playing tricks on me?

Also, if the screen lowered itself over time then I would assume my fix didn't work, but there shouldn't be anything to make it zoom in, lol. I'm going to bed now, but I'll add checking the camera fix to my todo list.

Thanks for the bug reports btw, I appreciate it!

From: Incurable
I totally believe you, so don't take this the wrong way, but if you can double check your graphics settings then we can rule out that "blur" as being a problem. Is it actually blurry, or are my tired eyes just playing tricks on me?

Ive had this issue on my laptop when i use DX/OGL (i cant remember which one)

From: Torol
I didn't blur anything, thats the RS graphics on Direct X minimum for me, the black squares were intentional of course :p
It says it's version 1.21, I don't know why it zooms, I was surprised too. The SRL is up to date too. Well, I guess I will try it again with the 1.3 when it comes out!

From: Incurable
I totally believe you, so don't take this the wrong way, but if you can double check your graphics settings then we can rule out that "blur" as being a problem. Is it actually blurry, or are my tired eyes just playing tricks on me?

Also, if the screen lowered itself over time then I would assume my fix didn't work, but there shouldn't be anything to make it zoom in, lol. I'm going to bed now, but I'll add checking the camera fix to my todo list.

Thanks for the bug reports btw, I appreciate it!

Based on Turpinator's reply above, it could be a DX problem on the computer. I don't know if Inc has OGL loading support in his script, but it should be standard because his script is recent. There is no specific reason to use DX or OGL in this script I don't think, now that OGL map problem is supposed to be fixed.

Torol, can you try switching graphics modes, it might fix the blur problem you're having. If the script won't run you'll have to bug Inc in the morning (damn Aussies) to make his script load the standard SMART plugins (both DX and OGL). I don't think this will have a huge effect on the bugs you've reported but it's gotta make the script a bit more accurate I'd have to say.

From: Turpinator
Ive had this issue on my laptop when i use DX/OGL (i cant remember which one)

I had no idea that DX/OGL could blur the screen. :confused:

From: 3Garrett3
I don't know if Inc has OGL loading support in his script, but it should be standard because his script is recent. There is no specific reason to use DX or OGL in this script I don't think, now that OGL map problem is supposed to be fixed.

There's nothing in my script that specifies DX vs OGL, so I assume that either one will work just fine.

Torol, can you try switching graphics modes, it might fix the blur problem you're having. If the script won't run you'll have to bug Inc in the morning (damn Aussies) to make his script load the standard SMART plugins (both DX and OGL). I don't think this will have a huge effect on the bugs you've reported but it's gotta make the script a bit more accurate I'd have to say.

@Torol, yeah, please do that. ^

From: Turpinator
Ive had this issue on my laptop when i use DX/OGL (i cant remember which one)

That's… strange. I use a laptop too. Did you fix that?

From: Incurable

@Torol, yeah, please do that. ^

Yeah I'm trying

From: Torol
Yeah I'm trying

What happens when you use OpenGL instead of DirectX?

From: Incurable
What happens when you use OpenGL instead of DirectX?

The bank-finder function works in SMART with OGL, but the script itself is not accurate enough. It looks for the bank/furnace, but when not finding it it teleports instead of walking closer to the object. However it's maybe just my computer, as Garrett said so you can't fix it.

From: Torol
The bank-finder function works in SMART with OGL, but the script itself is not accurate enough. It looks for the bank/furnace, but when not finding it it teleports instead of walking closer to the object. However it's maybe just my computer, as Garrett said so you can't fix it.

Nah, it's not your PC, the current version has too wide of a range for the compass angle and it causes it to fail. It should be fixed in 1.3, but it's taking longer than I thought it would. I'll release 1.2.2 when I get home from work to fix that issue. For now, don't use the script unless you're babysitting.

From: Incurable
There's nothing in my script that specifies DX vs OGL, so I assume that either one will work just fine.

There might not be anything in your script, but maybe he was reading the setup instructions like a good boy…

From: Incurable

3. Check that your Display Mode is set to DirectX (in RuneScape, Settings > Graphics > Custom > DirectX)

From: Turpinator
There might not be anything in your script, but maybe he was reading the setup instructions like a good boy…

Oops… no idea why I said to do that, haha!

EDIT: Fixed, thanks!

UPDATE: In light of the issues with this script, I've temporarily removed the attachments from the main post. I'm not happy with the amount of recoveries that the script is doing, and I'm (slowly) working on fixing everything for the next version. I'm also making several improvements to the script such as:

• DTM counting for ore/bars
• Improved run time (will run until you're out of ore, no need to specify)
• Added failsafes
• Rewritten banking functions (split it in two)
• Inc_Lude updates and separate auto-updater

There's probably some stuff that I've forgotten, but because of the number and size of the changes that I'm making, version 1.3 is now known as version 2.0. It should be out in a few days at most, but in the mean time, if you already have a copy of it on your computer, use is at your own risk (more than usual, obviously). I won't be supporting this script until then, but if you find any bugs that aren't on the known bugs list, then please post a detailed bug report.

Thanks!

UPDATE 2 (03/03/2015): Do not expect this script to come back any time soon, it will be a few months at least. I'm very bus IRL and just don't have the time to spend on scripting. I recommend BMWxi's script, it's (almost :stirthepot:) better than mine anyway, so you shouldn't have any problems with it.

Looks really good honestly, I'll have to give it a try when once I get my new account up and going.

Thanks for this Inc :)

From: Incurable
UPDATE: In light of the issues with this script, I've temporarily removed the attachments from the main post. I'm not happy with the amount of recoveries that the script is doing, and I'm (slowly) working on fixing everything for the next version.

Such a nub.

JK I hope you have it fixed by the weekend (tomorrow) so you can help me do my mercher but if you don't then I can help debug anything with you on this first. I still have 3k mith that I need to smelt on my merch tester so I can get a bit more cash money freed up.

@Incurable I managed to resolve my problem with the dx… I forgot that I've set the graphics card settings to performance for some reasons, so I put it back and it's not blurry now. I just thought you would like to know… :)

does this support port phast. smithing steel bars into cannon balls?

Would love if this got back online. Feel free to ask the community for help:)

From: Pompus
Would love if this got back online. Feel free to ask the community for help:)

Be patient ;)

Edit: This means it is still in the plans, but I wouldn't hold your breath (as he's very busy IRL right now).

Thank you for the heads up. My face is turning blue already! haha no. I understand. Good excuse to keep practicing and learning myself :)

From: Pompus
Thank you for the heads up. My face is turning blue already! haha no. I understand. Good excuse to keep practicing and learning myself :)

You'd be surprised at just how easy this script was to make, the only reason that it got complicated is because I love adding random crap to my scripts to make them more human, and half of it doesn't work. :redface:

—

UPDATE 2 (03/03/2015): Do not expect this script to come back any time soon, it will be a few months at least. I'm very busy IRL and just don't have the time to spend on scripting. I recommend BMWxi's script, it's (almost :stirthepot:) better than mine anyway, so you shouldn't have any problems with it.

@Justin can you move this to outdated for now? Thanks.