SRL Archive - MSI Suggestions

At the moment I am using the miner so get 99 mining hopefully =). I am power mining iron ore and have noticed that while gone I have probably dropped multiple uncut diamonds, which are 10k+ each, which means if I have dropped 10 diamonds, I have lost 100k that I could have made for free… I am just suggesting that someone make an ExcludeDropArray for items such as Gems while mining and nests while woodcutting and stuff like that… Thanks! and also thanks to Coh3n for everything you do!

Moved to the proper forum. ;)

And yes, I agree with this. We would need item records for the items you wish to keep however, such as diamonds. If you check out the how-to guide in the MSI Tutorials section I'm sure you could make it yourself. :)

I absolutely agree with this. Also, (not sure if this is a problem any more, or if it was the result of something failing) I ran a miner, with a rune pic in my inventory, and then walked my char. to a new location, and started a powerchopper. It dropped the pickaxe.

From: nickrules
I absolutely agree with this. Also, (not sure if this is a problem any more, or if it was the result of something failing) I ran a miner, with a rune pic in my inventory, and then walked my char. to a new location, and started a powerchopper. It dropped the pickaxe.

I have no idea why that would happen. IIRC, it happened to someone else also. Either way, if there's an ExceptionsArray then it can be added to/set during runtime which will be helpful with tools and such.

E: I've added this to the MSI Core TO-DO List.

Okay, so some general planning:

• Should probably have an ExcludeDropArray for each player, meaning it would have to be added to the MSI_Players type. Alternatively, it could be a global variable set by the user and would be common for every player.
• Would be an integer array and it would take the constants for MSI items.
• Would need to be reset/added to during runtime in the appropriate functions.

Anything I've forgotten, didn't interpret correctly?

From: Coh3n
Okay, so some general planning:

• Should probably have an ExcludeDropArray for each player, meaning it would have to be added to the MSI_Players type. Alternatively, it could be a global variable set by the user and would be common for every player.
• Would be an integer array and it would take the constants for MSI items.
• Would need to be reset/added to during runtime in the appropriate functions.

Anything I've forgotten, didn't interpret correctly?

Seems this would best fit in the MSI_Players type as different players could be using different scripts etc.

Also, how would you feel about a SetDropArray function that searches the inventory for items the user has specified not to drop. Then, returns a TIntegerArray of the InvSlots that are to be dropped and then simply call SRL's DropArray procedure.

You had a rune pickaxe, started a powercutter and you were surprised that it dropped your pickaxe?

What the hell were you doing woodcutting with a pickaxe in your inv?

~RM

From: NCDS
Seems this would best fit in the MSI_Players type as different players could be using different scripts etc.

Also, how would you feel about a SetDropArray function that searches the inventory for items the user has specified not to drop. Then, returns a TIntegerArray of the InvSlots that are to be dropped and then simply call SRL's DropArray procedure.

That makes the most sense since all our item interaction is basically inventory slots. It would just be another function just like MSI_FindAllToolSlots. We may be able to combine them so we could call like CombineIntArray(MSI_ExcludeSlots(TOOLS), MSI_ExcludeSlots(DropArr)) or whatever.

From: Sir R. Magician
You had a rune pickaxe, started a powercutter and you were surprised that it dropped your pickaxe?

What the hell were you doing woodcutting with a pickaxe in your inv?

~RM

Lol wow, didn't even realize that's what he said…

Committed.