Molly

bump

Sure, you have one now.

bump

bump

It does not.

I'll setup a vm with debian 8 when I get home from work tonight and try to figure out what the issue is.

My apologies, between a couple long shifts at work and some family issues that came up I anticipated not being able to look into this problem for a couple days. I just fixed the bug and pushed a new version. Fix will be live in version 8.0.

Let me know what version of Debian you are running so I can setup a vm with it and investigate the issue.

bump

bump

bump

861

bump

bump

You both have trials now. Could you post a picture of what the logger and paint says when this bug occurs?

I am not sure, it looks like the client should now be correctly launching the script since no errors are being thrown. Is the client not showing up? If it is what does it do? You may need to post in the general help section with this as I'm not familiar with running OSBot on debian if this does turn out to be an issue with the client launching the script. I believe you have my flax spinner script as well, would you mind trying to boot that with cli on debian and let me know if that runs. Sure, you have one now.

In your cli file on debian whenever you use the characters ( or ) use \( and \) instead. For example, rather than (Super_strength-1-3) put \(Super_strength-1-3\). Let me know if that fixes the issue for you. As for the suggestion with the checkboxes so you can use them to select all the items to loot and then add them in one click, you should be able to click an item in the list and then while holding the CTRL key select your next, and so on till you click to add them all to your loot list. You have one now.

bump

bump

bump

Sure, you have one now.

Sure, you have one now.

bump

You have one now.

I'm not sure what would be causing the issue when launching with explv manager, if you are able to run the script via cli without using explv manager then my guess is that the manager is the root of the issue. The problem with saving loot on debian looks to be because access to the settings file is not being allowed, looks the same as the issue reported HERE which unfortunately does not look to be resolved. You mentioned cli parameters in relation to this but from the sounds of it this is occurring not when you launch from CLI but rather when you launch the script normally, is that the case? I have updated the script just now so that when launched from CLI there should be nothing in the script running that will access the settings file, the live version will be 7.3. Hopefully that fixes this problem. It's on my to do list, though has been for some time, unfortunately I'm not currently doing updates to scripts other than bug fixes and maintaining their functionality as they are due to my busy schedule.