small issue with the .spk inside the .zip file when using the plugin manager script names: needs to be label BOF hide licenses rather then hide licenses if you are going to use the script type: package update. in its current state when you attempt to use it says unable to find old .spk to update even thou i have one label BOF hide licenses 1.01 it is trying to find hide licenses to update.
might be just easier to change script type: other ship command if the .spk contains all the files needed so anyone can use the .spk or go manual.
sent you the file with the fixed .spk
so you want me to test those other scripts as well.
None of us is as smart as all of us. ~Ken Blanchard
As far as the other scripts go - you are obviously having fun, and I don't want to be a spoilsport....... there aren't that many left that you haven't broken....
possible bug. i had no licenses at the time when i used these commands. when i selected option "H"ide a response came up saying license hidden for "." and i selected option "R"estore it said License restore for " " 100cr taken from your account. so how is it taking 100cr if there weren't any licenses hidden in the first place? not that 100cr is a lot
"F"orge does not work. says it is an unrecognizable command (tried both F and f)
None of us is as smart as all of us. ~Ken Blanchard
Sounds like there could be a logic error - I will check it out after I have done a few jobs....
The Forge part requires an input of 'FA', 'FB', 'FS' etc to forge Argon, Boron etc. I could add an incoming message to select the license to be forged when 'F' is entered on it's own.
ok got it with the Forge. when you get to the input string text it only lists H R L F then starts to describe each one (runs out of space for descibing F)
None of us is as smart as all of us. ~Ken Blanchard
Yup, that is the problem - a limited number of characters for the input 'help'. - and you are not the first to have fallen foul of it...
I decided against adding an incoming question - instead I have made a separate 'pop-up' message that appears without having to look at the messages (yes, the one described in the MSCI as being "generally a very bad thing to do unless the message is of critical importance." and "a good way to ensure that your script will never be signed").
In spite of all the counts against it, I think that it saves a lot of hassle - the error is displayed, and you can easily rectify it without having to look at the messages and get back to the command... and calling poor old BOF a lot of rude names (most of which have been well earned)...
I am also improving some of the messages, and tidying it up a bit - also testing that it works - there was a logic error that has now been rectified.
Latest version is now available.
I corrected the error found by draffutt - player has no licenses
I have also changed the messages to be more informative, and added a 'pop-up' message when 'F' for forge is entered on its own.