SRL Archive - MSI Bugs

Hi guys, me again. Love MSI, and want to contribute bug reports until I can wrap my head around the code. But until then…

Something strange is happening with the priority autoing in the player form. Currently, I am using the Varrock East Miner. I have all three rocks (Tin, Copper, and Iron) checked off, and I input the following string into the priority box: "5, 5, 90".

I go to save the Player data, and next time I run MSI, the string has become "5, 90" - I'm assuming this also means the script has gotten the input "5, 90" instead of "5, 5, 90".

I know the priority setting thing works with 2 different objects, but I don't know if this problem directly relates to the number of objects, or what… I'll report back if I find this happens with 3 or more objects consistently.

Thanks for the information, I'll add it to my bug list. :) Keep up the great reporting! Loving it!

Just my way of saying thank you for the hard work :)

There's probably a ClearSameIntegers call somewhere in the form. Try setting it to 5, 6, 89 and see if it stays the same. By the way, they don't have to add to 100. The higher the number, the higher chance it has of being looked for first. You could set it to 5, 100, 100000 if you wanted.

Should anything be done with this? Or is it basically resolved?

From: Coh3n
There's probably a ClearSameIntegers call somewhere in the form. Try setting it to 5, 6, 89 and see if it stays the same. By the way, they don't have to add to 100. The higher the number, the higher chance it has of being looked for first. You could set it to 5, 100, 100000 if you wanted.

Yes, that worked fine. As long as you don't put in the same numbers, you are fine.

@Kyle: Yes, I think this is basically resolved.

This is why it's clearing the same numbers, which I kinda understand, yet kinda don't.

            if (script_Edits[EDIT_PRIORITY].Text = '') then
              Priority := []
            else
              Priority := StrToIntArr(script_Edits[EDIT_PRIORITY].Text);

            ClearSameIntegers(Priority);

I'll mark this as resolved for now, since there isn't a "real" issue.

Yeah, I'm not sure of the purpose behind clearing the same numbers, but I suppose it might have something to do with the actual mechanics behind priority autoing.

Yeah, that's what I was thinking. Just haven't dug down into it yet.

Actually, I can't think of why I added it. Would make sense for Exceptions, but if you just removed the call I'm sure it would work just fine.