SRL Archive - MSI Bugs

The graphics at this mine have been updated, the rocks look completely different to any other rocks I've seen.. Just a heads up if someone wants to update this some time :) (the script doesn't mine at the moment)

It's been a known problem since it happened pretty much, Just haven't got to updating it yet.

I didn't know there was already a script for this spot. I did some surveying for this location and it seems about the same distance (roughly) as, say, a Varrock East miner, or maybe even Rimmington miner. The newer-style rocks are a bit tougher to detect via color, as 90% of the rock is the same color as the surrounding rocks, even ore-less rocks. Only a sliver of differential color will tell you if there's an ore inside or not. Object IDs / Tiles using reflection would be a huge advantage in cases like this.

I'm pretty sure they initially changed it to catch botters, as it's barely possible to tell if there is any coal available while playing legit anyway. I was using a reflection type bot there when they changed it and I got banned shortly after.

I think you might be on to something actually. They know it's not easy to visually detect (rocks of that sort) if they have an ore or if they're empty, so when reflection instantly clicks on a newly-spawned rock, that might throw up some flags. Good observation. :o

Looks like jagex is finally doing something to stop botters, first the tree update in draynor area, now this……what next?

From: Flight
I think you might be on to something actually. They know it's not easy to visually detect (rocks of that sort) if they have an ore or if they're empty, so when reflection instantly clicks on a newly-spawned rock, that might throw up some flags. Good observation. :o

I strongly believe it. I have botted three days straight with that account (which is my main) and nothing happened but I bot for 4 hours in LSW right after the update I failed to check out and I get a 14 day ban. I think it also might have had something to do with losing membership shortly before that…they don't seem to ban members as much :p

EDIT: this update was before the tree update

Yeah like NCDS said, this has been known since the day it happened. I've tried to updated it a couple times, but honestly I can't tell the difference so as a result I couldn't properly do it for Simba. I honesly stared at a coal rock that had ore and didn't have ore and I couldn't see the difference (that's with lowest details of course).

So, I doubt this one would be updated. Unless someone can get the right colors, we may as well remove it from our scripts.

That might be the best thing to do Coh3n. I couldn't even tell either. I was just shocked on how drastic they look.

I have a feeling fishing is next.

From: Overtime
That might be the best thing to do Coh3n. I couldn't even tell either. I was just shocked on how drastic they look.

I have a feeling fishing is next.

They can't make it that bad. The game would be ruined. If you and I can't tell the difference, I guarantee there are others. I think what they did with the trees was really, really smart (not to mention they look much better and are more realistic). The point is Jagex can't make everything look so a like that the actual players can't tell the difference.

I wouldn't be surprised if the Lumbridge update is temporary just to catch bots. There's no way they can do that for all rocks around RS. At least not for coal.

From: Coh3n
They can't make it that bad. The game would be ruined. If you and I can't tell the difference, I guarantee there are others. I think what they did with the trees was really, really smart (not to mention they look much better and are more realistic). The point is Jagex can't make everything look so a like that the actual players can't tell the difference.

I wouldn't be surprised if the Lumbridge update is temporary just to catch bots. There's no way they can do that for all rocks around RS. At least not for coal.

If I was them though I would have chosen a more populated spot like the guild though. I actually haven't been to LWS since the update but Ill go take a look now.

From: Yago
If I was them though I would have chosen a more populated spot like the guild though. I actually haven't been to LWS since the update but Ill go take a look now.

Maybe the guild mine is next, who knows.

Its possible to tell when there's ore just impossible to beat all the bots… Plus it would be hard detecting because the colors are really similar.

From: Yago
Its possible to tell when there's ore just impossible to beat all the bots… Plus it would be hard detecting because the colors are really similar.

Are you still talking about Lumbridge Swamp? I've seen other rocks and you can tell the difference (barely), but I can't even a little bit in Lumbridge Swamp. =\

I even tried updating the colors today to make the script work… again, and I couldn't make it work at all. Mithril and Adamant would work, just not coal.

So I'm not really sure if I should remove it or not. I suppose I could just take out the coal so people can still use it for adamantite and mithril.

Given the fact that now all other rocks are like this, you could probably leave it in :P

Yeah, but I'd like to get it to work. :(

From: Coh3n
Are you still talking about Lumbridge Swamp? I've seen other rocks and you can tell the difference (barely), but I can't even a little bit in Lumbridge Swamp. =\

You can tell the difference but it also depends on your camera angle.

It would be hard to get the color though. As its practically a minute, small stripe on the big rock…

Really unfortunate. :(

I'm not really sure of another alternative other than reflection.

From: Coh3n
Really unfortunate. :(

I'm not really sure of another alternative other than reflection.

I haven't checked the Coal Rocks anywhere else other than Ardounge, but I have a very accurate DTM for coal rocks that I'll be experimenting with today. Try this out and see if it works for you.

CoalRockDTM := DTMFromString('mQwAAAHicY2ZgYEhjZGBIBuJUIF4G5C8F4pVALCcny8DHxwvGyIARCQMBALqyA9c=');

You probably already know but I'm working on a proto-type miner, quite different than what's been used in other scripts. If it works then that's grand, it'll start out already able to accurately find and track the new rock types.

That's interesting. I don't have time to test it out now, so in the meantime if you have a test script I could simply run that would be easier. I've never really seen anyone use DTMs for object finding so I'm interested to see if it works.

It only detects Mith for me, no Addy, experimenting with colors also atm…..

I've gotten mine to work but I've a few issues I need to take care off. In my script, while I'm animating (mining) I'll grab the nearest Coal Rock's DTM and save the x/y coordinates of that rock. This is assuming it's the rock we're currently mining. And as long as the DTM still exists in that specific x/y then the ore still exists. It has, surprisingly, worked 'okay' so far, but I have an issue of missing the closest DTM if it's clicked once and then blocked by my players sprite as I move closer to the rock, so it searches for another.

I wonder if camera rotations would be a possible solution to this, as we have DTMRotated, or something like that?

From: Flight
I wonder if camera rotations would be a possible solution to this, as we have DTMRotated, or something like that?

I don't think so unless DTMs are 3D… So I guess not. What You might have to do is rotate the camera and get a new DTM. So check for a player animation then if true rotate and check animation again and if that's true after rotating then find the new DTM. Problem is the player animates even after the ore is gone if someone beat him to the ore.

From: Yago
I don't think so unless DTMs are 3D… So I guess not. What You might have to do is rotate the camera and get a new DTM. So check for a player animation then if true rotate and check animation again and if that's true after rotating then find the new DTM. Problem is the player animates even after the ore is gone if someone beat him to the ore.

Yeah I explained this already. This is how my reflection mining scripts are set up, but it's a bit harder with color.

First off I start by finding the nearest Rock DTM, when I click and arrive at the rock I find the 'new' nearest DTM and get the x/y coordinate of it, this assumes it's the rock we're currently mining on. So as long as it exists, there's ore in that rock and as long as our character is animating while rock is still filled, we wait… I seem to be having some trouble with the 'IsMoving' function which uses color pixelshift. I'll work on it a bit more in the morning to see why it's giving me false positives.

From: RAM
It only detects Mith for me, no Addy, experimenting with colors also atm…..

Okay, if you get some working colors I'll update. :)

Coal 3355698 alot of misclicks, but it works, also scavenges dropped ores….
Addy 14153942 needs a little extra wait for lower level miners…
Mith seems fine….

{ MSI Phoenix Player Report }
{—————————————————————-}
{ Time Running: 6 Hours, 3 Minutes and 9 Seconds }
{—————————————————————-}
{ }
{ Player 1: Coh3n }
{ Location: Lumbridge swamp west mine }
{ Time: 05h 49m 22s }
{ Active: False }
{ Reason: }
{ }
{ Script: Lumby Swamp West Miner }
{ Time: 05h 49m 22s }
{ Skill: Mining }
{ Exp: 52,310 }
{ Level: 77 }
{ Loads: 26 }
{ Item: Coal ore }
{ Amount: 210 }
{ Item: Mithril ore }
{ Amount: 430 }
{ Item: Adamantite ore }
{ Amount: 78 }
{ }
{—————————————————————-}
{—————————————————————-}
[6:03:10]: Thank-you for using MSI Phoenix scripts!
[6:03:10]: Successfully executed.

Wow RAM, thanks! That's actually awesome. I'll make the updates right away.

E: Did you change anything else? Because when it misclicks the coal it will wait for the rock to be mined, and since the rock isn't there it'll just wait until it times out.

Coal Colors := [2171426];
Mithril Colors := [16624810];
ADAMANTITE(SP?) Colors := [13100486];

Changed max wait time for Addy to 15000;

Still running atm……

Status: /~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\
Status: | SRL Randoms Report |
Status: | www.villavu.com |
Status: |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Status: \~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~/
{—————————————————————-}
{ MSI Phoenix Short Report }
{—————————————————————-}
{ Time Running: 13 Hours, 23 Minutes and 38 Seconds }
{—————————————————————-}
{ }
{ Totals: }
{ - Players: 1 }
{ - Player Time: 12h 59m 40s }
{ - Randoms Solved: 0 }
{ - Randoms Failed: 0 }
{ - Loads: 101 }
{ - Experience: 137,825 }
{ - Rocks Mined: 2,287 }
{ }
{—————————————————————-}
{—————————————————————-}

{—————————————————————-}
{ MSI Phoenix Player Report }
{—————————————————————-}
{ Time Running: 13 Hours, 23 Minutes and 38 Seconds }
{—————————————————————-}
{ }
{ Player 0: Coh3n }
{ Location: Draynor Village bank }
{ Time: 12h 59m 40s }
{ Active: True }
{ }
{ Script: Lumby Swamp West Miner }
{ Time: 12h 59m 40s }
{ Skill: Mining }
{ Exp: 137,825 }
{ Level: 78 }
{ Loads: 101 }
{ Item: Coal ore }
{ Amount: 1,558 }
{ Item: Mithril ore }
{ Amount: 622 }
{ Item: Adamantite ore }
{ Amount: 107 }
{ }
{—————————————————————-}

Has anyone used DTMs for object finding before, or am I the first pioneer? :norris:

I think that'd be too good to be true. ;)

From: RAM
Coal Colors := [2171426];
Mithril Colors := [16624810];
ADAMANTITE(SP?) Colors := [13100486];

Changed max wait time for Addy to 15000;

Still running atm……

Were you using the same tolerance and cts modifiers that already are in place? I'd like to get this updated for everyone asap if we can.

And why did you change the Addy max wait to 15000? You said you needed it to wait longer for lower level miners, but you lowered the number so it won't wait as long. And 15 seconds isn't long for mining..

E: RAM, I made the changes in your last post and it's working well for me. I'll push right now. :)

E2: Done, thanks a ton RAM. :)

From: Flight
Has anyone used DTMs for object finding before, or am I the first pioneer? :norris:

I think that'd be too good to be true. ;)

Pretty sure it's been done before ;), but keep experimenting :)

From: NCDS
Were you using the same tolerance and cts modifiers that already are in place? I'd like to get this updated for everyone asap if we can.

Yes

From: Coh3n
And why did you change the Addy max wait to 15000? You said you needed it to wait longer for lower level miners, but you lowered the number so it won't wait as long. And 15 seconds isn't long for mining..

E: RAM, I made the changes in your last post and it's working well for me. I'll push right now. :)

E2: Done, thanks a ton RAM. :)

seems like the wait time for Addy was only 6 seconds or so before…

my ant iban and anti random calls are set to 30 seconds each and priorities are set to default 0, but was thinking with experimenting with this number to make Addy a priority as it misses it quite a bit, I also noticed when there is multiple colors for each ore, it misclicks more often….

Thanks for posting proggies in Proggy section :)

From: RAM
seems like the wait time for Addy was only 6 seconds or so before…

Odd, maybe just the tracking wasn't working properly. It was set to 65 seconds for me.

From: RAM

my ant iban and anti random calls are set to 30 seconds each and priorities are set to default 0, but was thinking with experimenting with this number to make Addy a priority as it misses it quite a bit, I also noticed when there is multiple colors for each ore, it misclicks more often….

Yeah right now I have coal set to 30 and mith to 70 for priority. If mith isn't found it'll look for coal. So if you were to set coal to 10, mith to 45, and addy to 45, it'll look for addy and mith first most of the time.

From: Coh3n
Odd, maybe just the tracking wasn't working properly. It was set to 65 seconds for me.


Yeah right now I have coal set to 30 and mith to 70 for priority. If mith isn't found it'll look for coal. So if you were to set coal to 10, mith to 45, and addy to 45, it'll look for addy and mith first most of the time.

OK, that makes sense, I was trying to decipher the code…. so it looks for the lowest ore then works it's way up ? Coal, Mith, Addy, didn't know I could set priorities in 3 (or more ?IE, ALL ores in Rimmy?)

Always seems to miss the one Addy rock to the south, going to try and set Priorities to 10,30,60 and bump up the tolerance on Addy….

From: RAM
(or more ?IE, ALL ores in Rimmy?)

No as we don't have a script record that mines at all of rimmington mine anymore. We did at first, but it was then split up to the way it is now. I'm sure you could throw one together to support all the rocks again though, if you'd like. ;)

It really probably wouldn't be a bad idea to have that honestly.

From: RAM
OK, that makes sense, I was trying to decipher the code…. so it looks for the lowest ore then works it's way up ? Coal, Mith, Addy, didn't know I could set priorities in 3 (or more ?IE, ALL ores in Rimmy?)

Always seems to miss the one Addy rock to the south, going to try and set Priorities to 10,30,60 and bump up the tolerance on Addy….

If you don't set the priority, it'll look for a random ore that's in the mine (or a random ore that you set as the player's rocks). For priority, they don't have to add to 100. You can set Addy to 5000 if you want it to look for it first 99% of the time. It'll look for addy first, then whatever is next when the array is "rearranged".

From: NCDS
No as we don't have a script record that mines at all of rimmington mine anymore. We did at first, but it was then split up to the way it is now. I'm sure you could throw one together to support all the rocks again though, if you'd like. ;)

It really probably wouldn't be a bad idea to have that honestly.

I think he meant LSW Mine because Rimmington doesn't have Coal, Mith, or Addy. Also, yeah now that there's multiple relocation point support, one script for all of Rimmington mine probably wouldn't be hard.

From: Coh3n
If you don't set the priority, it'll look for a random ore that's in the mine (or a random ore that you set as the player's rocks). For priority, they don't have to add to 100. You can set Addy to 5000 if you want it to look for it first 99% of the time. It'll look for addy first, then whatever is next when the array is "rearranged".


I think he meant LSW Mine because Rimmington doesn't have Coal, Mith, or Addy. Also, yeah now that there's multiple relocation point support, one script for all of Rimmington mine probably wouldn't be hard.

Nope, meant Rimmy…Gold, Tin, Copper, Clay….that's 4…OK, so it does start to look for the lowest level ore first though ?..Coal–>,Mith–>, Addy–>, so 10,500,5000 would net me ?….Addy 99%, Mith 9%, and Coal 1% ?

So Rimmy Multi-miner would just need a few more points, enhanced array….

Edit:, never did get the chance to tweak Addy, when I tried setting the priorities in the array to 3 digit set, IE, 10,30,60 it just added it to the previous 20,80, for a result of 80,20,10,30,60 …….and it kept crashing when i tried to save…have to go in and manually edit I guess…..Or just delete player and re-enter info…

Status: /~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\
Status: | SRL Randoms Report |
Status: | www.villavu.com |
Status: |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Status: | SRL Logs : 1 |
Status: \~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~/
{—————————————————————-}
{ MSI Phoenix Short Report }
{—————————————————————-}
{ Time Running: 8 Hours, 39 Minutes and 10 Seconds }
{—————————————————————-}
{ }
{ Totals: }
{ - Players: 1 }
{ - Player Time: 08h 16m 39s }
{ - Randoms Solved: 0 }
{ - Randoms Failed: 0 }
{ - Loads: 64 }
{ - Experience: 75,005 }
{ - Rocks Mined: 1,342 }
{ }
{—————————————————————-}
{—————————————————————-}

{—————————————————————-}
{ MSI Phoenix Player Report }
{—————————————————————-}
{ Time Running: 8 Hours, 39 Minutes and 10 Seconds }
{—————————————————————-}
{ }
{ Player 0: Coh3n }
{ Location: Lost }
{ Time: 08h 16m 39s }
{ Active: False }
{ Reason: Failed to setup player }
{ }
{ Script: Lumby Swamp West Miner }
{ Time: 08h 16m 39s }
{ Skill: Mining }
{ Exp: 75,005 }
{ Level: 79 }
{ Loads: 64 }
{ Item: Coal ore }
{ Amount: 1,082 }
{ Item: Mithril ore }
{ Amount: 253 }
{ Item: Adamantite ore }
{ Amount: 7 }
{ }
{—————————————————————-}
{—————————————————————-}
[8:39:15]: [Coh3n ] —— All players inactive
[8:39:15]: Thank-you for using MSI Phoenix scripts!
[8:39:15]: Successfully executed.

Connection timed out….

New Addy Colors := [13100486, 15072730, 13953738];

Increased Tol to 10

Seems to be working better… Priorities set to 10,600,6000

Status: /~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\
Status: | SRL Randoms Report |
Status: | www.villavu.com |
Status: |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Status: | Certers Solved : 1 |
Status: | Reward Box Missed : 1 |
Status: \~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~/
{—————————————————————-}
{ MSI Phoenix Short Report }
{—————————————————————-}
{ Time Running: 13 Hours, 42 Minutes and 58 Seconds }
{—————————————————————-}
{ }
{ Totals: }
{ - Players: 1 }
{ - Player Time: 13h 33m 33s }
{ - Randoms Solved: 1 }
{ - Randoms Failed: 0 }
{ - Loads: 97 }
{ - Experience: 149,465 }
{ - Rocks Mined: 2,476 }
{ }
{—————————————————————-}
{—————————————————————-}

{—————————————————————-}
{ MSI Phoenix Player Report }
{—————————————————————-}
{ Time Running: 13 Hours, 42 Minutes and 58 Seconds }
{—————————————————————-}
{ }
{ Players: 1 }
{ Location: Draynor Village bank }
{ Time: 13h 33m 33s }
{ Active: True }
{ }
{ Script: Lumby Swamp West Miner }
{ Time: 13h 33m 33s }
{ Skill: Mining }
{ Exp: 149,465 }
{ Level: 80 }
{ Loads: 97 }
{ Item: Coal ore }
{ Amount: 1,725 }
{ Item: Mithril ore }
{ Amount: 542 }
{ Item: Adamantite ore }
{ Amount: 209 }
{ }
{—————————————————————-}

From: RAM
Nope, meant Rimmy…Gold, Tin, Copper, Clay….that's 4…OK, so it does start to look for the lowest level ore first though ?..Coal–>,Mith–>, Addy–>, so 10,500,5000 would net me ?….Addy 99%, Mith 9%, and Coal 1% ?

So Rimmy Multi-miner would just need a few more points, enhanced array….

Right.

From: RAM

Edit:, never did get the chance to tweak Addy, when I tried setting the priorities in the array to 3 digit set, IE, 10,30,60 it just added it to the previous 20,80, for a result of 80,20,10,30,60 …….and it kept crashing when i tried to save…have to go in and manually edit I guess…..Or just delete player and re-enter info…

Do you mean in the player file it added to make 80,20,10,30,60? I have no idea how that could happen. The file is completely cleared before saving. =\ Oh and thanks for the Addy update. :)

addy & mith was working fine for me.. 2 days ago? or yesterday I forgot

From: Coh3n
Right.


Do you mean in the player file it added to make 80,20,10,30,60? I have no idea how that could happen. The file is completely cleared before saving. =\ Oh and thanks for the Addy update. :)

Yep, had to go in and manually edit, try and see if you can replicate the problem by adjusting your priorities and saving, saving both before and after you close the window, if it doesn't crash right away, usually will within 10 minutes of running, and then, yet again, it could just be me :redface:

One more question on the priorities, when you increase the number, does it also increase how many times it clicks on it ? because i think i noticed it more with higher numbers ?

From: RAM

One more question on the priorities, when you increase the number, does it also increase how many times it clicks on it ? because i think i noticed it more with higher numbers ?

That shouldn't make a difference. We use a function (MSI_RearrangeArray) for Priority autoing which simply arranges the array randomly with the influence of the users set priorities. The array is then passed to the Object finding functions which is where the finding and clicking is handled.

Hopefully that brief explanation helps clear it up a bit. :redface:

From: RAM
Yep, had to go in and manually edit, try and see if you can replicate the problem by adjusting your priorities and saving, saving both before and after you close the window, if it doesn't crash right away, usually will within 10 minutes of running, and then, yet again, it could just be me :redface:

No idea why it crashes for some people and not others, but I was able to reproduce your issue and I've pushed a fix, thanks. :)

https://github.com/SRL/MSI/commit/eb729fcf9459c33ce91e0bc26437479391a9aa39

From: NCDS
That shouldn't make a difference. We use a function (MSI_RearrangeArray) for Priority autoing which simply arranges the array randomly with the influence of the users set priorities. The array is then passed to the Object finding functions which is where the finding and clicking is handled.

Hopefully that brief explanation helps clear it up a bit. :redface:

If it's "Randomized", then how do the priorities influence it ? :redface:

From: Coh3n
No idea why it crashes for some people and not others, but I was able to reproduce your issue and I've pushed a fix, thanks. :)

https://github.com/SRL/MSI/commit/eb729fcf9459c33ce91e0bc26437479391a9aa39

Glad to help :) TY

From: RAM
If it's "Randomized", then how do the priorities influence it ? :redface:

For instance, if you have addy set to a higher priority than coal, most of the time the script will search for addy first, because of how the function sorts the array. However, sometimes it will still search for coal first.

The higher priority you set for addy, the more chance you have of the script searching for addy first, but it will still randomly search for another ore first sometimes.

That help at all? :)

OK, I think I finally understand :)