SRL Archive - MSI Archives

Hey guys i'm not 100% sure if this is the right section for this but running MSI with the latest SRL developer SVN and SCAR 3.23Beta and when I try to start the script RunMe.Scar I get this error :

[Error]: Unable to find file './Core/Constants.simba' used from ''

Thanks and advance and sorry if this isn't the right place.

its a simba script

use simba and the srl through that

~shut

EDIT: http://wizzup.org/simba/article/2
then enable srl.sex from View -> Extensions

And don't forget http://wizzup.org/simbadoc/ every day we add a lot of useful documentation, so you may find additional help resources there.

I done all that you told me but when I run the script in SIMBA even after it told me it updated my SRL and plugins I still get an error.

Exception in Script: Unable to find file 'SRL/SRL/MSI/Setup.scar' used from ''

From: Hamish
I done all that you told me but when I run the script in SIMBA even after it told me it updated my SRL and plugins I still get an error.

Exception in Script: Unable to find file 'SRL/SRL/MSI/Setup.scar' used from ''

Sounds like you didn't download msi to the right file location. Make sure it's in the folder with 'core', 'misc' and 'skill',

Yeah it is. I'll try and redownload it. Thanks for all the help so far.

Ahh, more errors I dunno what iv'e done wrong but I don't care that much anymore, thanks for the help anyway. -_-''

From: Hamish
Yeah it is. I'll try and redownload it. Thanks for all the help so far.

Ahh, more errors I dunno what iv'e done wrong but I don't care that much anymore, thanks for the help anyway. -_-''

And this is why we need a script manager… which gladly is on the way :)

~RM

From: Rasta Magician
And this is why we need a script manager… which gladly is on the way :)

~RM

Woop, then people with no clue what to do like me can do it easier!

Gonna try this again, got this error when opening it with simba, got latest SRL Dev, MSI etc.

[Error] (40:1): Unable to register function function Mordaut_GetSlotNr(ScanningTime: Extended; ClientHDC: HDC): integer; at line 39

Enabled the SRL.sex thingy too.

Trying to open RunMe.scar

From: Hamish
Gonna try this again, got this error when opening it with simba, got latest SRL Dev, MSI etc.

[Error] (40:1): Unable to register function function Mordaut_GetSlotNr(ScanningTime: Extended; ClientHDC: HDC): integer; at line 39

Enabled the SRL.sex thingy too.

Trying to open RunMe.scar

Uhh…? Never seen that before. Lol. Have you moved your plugins properly?

Yeah I have, funny thing is, line 39 is just a piece of code like:

program MSIScript;

So I don't see why that would change anything.

From: Hamish
Yeah I have, funny thing is, line 39 is just a piece of code like:

program MSIScript;

So I don't see why that would change anything.

It doesn't open another file? Some file that has something to do with the Mordaut random perhaps?

Redownloaded SRL and MSI and it suddenly started to work, although only without reflection. It's a decent script but it keeps dropping my hatchet. =/

From: Hamish
Redownloaded SRL and MSI and it suddenly started to work, although only without reflection. It's a decent script but it keeps dropping my hatchet. =/

Well that's interesting. Can you post the debug (or PM it to me as the username appears there)?

From: Coh3n
Well that's interesting. Can you post the debug (or PM it to me as the username appears there)?

Theres nothing in the debug, it just chops until my inventory is full and then skips my hatchet as it is dropping but then when everything has been dropped it goes back and drops my hatchet.

From: Hamish
Theres nothing in the debug, it just chops until my inventory is full and then skips my hatchet as it is dropping but then when everything has been dropped it goes back and drops my hatchet.

Alright well that's obviously not suppose to happen. I'll look into it, thanks. :)

Try the latest version. All of the DTM related bugs should be gone. I hope anyway. :p

Cool, it works nicely now thanks for all the help.

Been watching it for a few loads and I noticed that if it's in the middle of doing anti-ban and the tree runs out it takes some time to notice a new tree and also if the tree has a very low log count like 4-5 it takes a bit to notice that it's gone because it would expect more logs. Of course these may be limitations of using a colour bot but I thought you'd like to know just in case they are optimizable.

Iv'e got a good few accounts I can auto on so give me a shout if you need some new MSI script tested i'll give it a test.

From: Hamish
Cool, it works nicely now thanks for all the help.

Been watching it for a few loads and I noticed that if it's in the middle of doing anti-ban and the tree runs out it takes some time to notice a new tree and also if the tree has a very low log count like 4-5 it takes a bit to notice that it's gone because it would expect more logs. Of course these may be limitations of using a colour bot but I thought you'd like to know just in case they are optimizable.

Iv'e got a good few accounts I can auto on so give me a shout if you need some new MSI script tested i'll give it a test.

believe me, that is no limitiation of a colour bot :P
we even had solvers for the impossible randoms
it will just need a little bit of tweeking :)
just give it a little while and someone will fix it, because it doesn't sound like a hard problem to fix

~shut

From: Coh3n
Try the latest version. All of the DTM related bugs should be gone. I hope anyway. :p

Lol nope, I was doing powerchopping, and it count any log to the progressreport. I was cutting willows btw.

From: Hamish
Cool, it works nicely now thanks for all the help.

Been watching it for a few loads and I noticed that if it's in the middle of doing anti-ban and the tree runs out it takes some time to notice a new tree and also if the tree has a very low log count like 4-5 it takes a bit to notice that it's gone because it would expect more logs. Of course these may be limitations of using a colour bot but I thought you'd like to know just in case they are optimizable.

Iv'e got a good few accounts I can auto on so give me a shout if you need some new MSI script tested i'll give it a test.

The script doesn't expect any amount of logs from a tree. It just checks for colours around the point you clicked. Does it take a while to notice the tree's gone everytime? Because it seems to be working fine for me…

And the antiban thing can be easily fixed.

From: BobboHobbo
Lol nope, I was doing powerchopping, and it count any log to the progressreport. I was cutting willows btw.

You mean it didn't count any logs?

Amazing script, going 2h, 15 mins and still going nicely. Does the breaks it take count into the timer btw?

Yeah Coh3n i'm not sure how to put it but if a tree finishes quickly it seems to take some time to pick a new one, maybe there would be a way for it to find tree's faster so it's not standing there for a few seconds when there is a tree right next to him.

From: Hamish
Amazing script, going 2h, 15 mins and still going nicely. Does the breaks it take count into the timer btw?

Yeah Coh3n i'm not sure how to put it but if a tree finishes quickly it seems to take some time to pick a new one, maybe there would be a way for it to find tree's faster so it's not standing there for a few seconds when there is a tree right next to him.

Yeah that's odd, it shouldn't wait, but I think once I adjust the antiban thing, that should improve. I've working on a few tweaks right now, so expect an update soon.

E: Updated.

Just gonna post here so I don't have to make a whole new thread.

I have the woodcutting script running in the background with SMART and i'm checking up on it now and again and I keep finding it with the report abuse tab open with my username and part of my password typed in, like it's trying to log into it. Not sure how it gets into this tab but it keeps happening.

It would be cool if it hovered over the next tree when it's chopping just to speed it up.

Edit: Realised theres a new version, I updated it now and I will see if it happens still.

From: Hamish
Just gonna post here so I don't have to make a whole new thread.

I have the woodcutting script running in the background with SMART and i'm checking up on it now and again and I keep finding it with the report abuse tab open with my username and part of my password typed in, like it's trying to log into it. Not sure how it gets into this tab but it keeps happening.

It would be cool if it hovered over the next tree when it's chopping just to speed it up.

Edit: Realised theres a new version, I updated it now and I will see if it happens still.

I heard of that happening ages ago with some scripts. I'm guessing the same problem arose again in SRL. Let's hope it doesn't happen again. Could have just been a fluke.

Also, and the object thing. I'm not sure what's going on, but it doesn't seem to be working as well as it used to for some reason. It seems to take longer to detect whether the tree has been cut down, and it likes to click the tree every ~7 seconds or so.

From: Coh3n
I heard of that happening ages ago with some scripts. I'm guessing the same problem arose again in SRL. Let's hope it doesn't happen again. Could have just been a fluke.

Also, and the object thing. I'm not sure what's going on, but it doesn't seem to be working as well as it used to for some reason. It seems to take longer to detect whether the tree has been cut down, and it likes to click the tree every ~7 seconds or so.

Seems to still be happening with the report abuse thing. Don't mean to always be moaning i'm just trying to help this out! :P

From: Hamish
Seems to still be happening with the report abuse thing. Don't mean to always be moaning i'm just trying to help this out! :P

Don't be sorry, feedback is always appreciated. :) Were you watching when it happened? What was the script doing? Do you happen to know what the debug box said?

The script doesn't stop it just keeps running but it has the report box open. I think it seems to happen after the script finishes from taking a break. I'm not 100% sure though.

From: Hamish
The script doesn't stop it just keeps running but it has the report box open. I think it seems to happen after the script finishes from taking a break. I'm not 100% sure though.

I have no clue why that would happen. After taking a break it just logs back in (which is does at the beginning of the script), so there should be no errors. =\

Also noticed a couple of times that it seems to examine like 4 willow logs in a row. Kind of weird nothing serious though just thought you'd like to random it up a bit more =P

From: Hamish
Also noticed a couple of times that it seems to examine like 4 willow logs in a row. Kind of weird nothing serious though just thought you'd like to random it up a bit more =P

I think that's the antiban in SRL. It just moves the mouse over a random area on the main screen and if there's an option to examine, it will. I think you just got really unlucky. :p