EndureCoreNas Posted May 1, 2016 Posted May 1, 2016 It was working fine just a bit ago, but updated osbot and ran a script and it shows: [ERROR][bot #1][05/01 11:38:48 AM]: Blocked permission: ("java.io.FilePermission" "C:\Users\PC\OSBot\khal\images" "read") [iNFO][bot #1][05/01 11:38:48 AM]: Terminating script Khal Blast Furnace... [iNFO][bot #1][05/01 11:38:48 AM]: Successfully updated signature. [iNFO][bot #1][05/01 11:38:48 AM]: Script Khal Blast Furnace has exited! [iNFO][05/01 11:38:48 AM]: Started script : Khal Blast Furnace
Anivia Posted May 1, 2016 Posted May 1, 2016 It was working fine just a bit ago, but updated osbot and ran a script and it shows: [ERROR][bot #1][05/01 11:38:48 AM]: Blocked permission: ("java.io.FilePermission" "C:\Users\PC\OSBot\khal\images" "read") [iNFO][bot #1][05/01 11:38:48 AM]: Terminating script Khal Blast Furnace... [iNFO][bot #1][05/01 11:38:48 AM]: Successfully updated signature. [iNFO][bot #1][05/01 11:38:48 AM]: Script Khal Blast Furnace has exited! [iNFO][05/01 11:38:48 AM]: Started script : Khal Blast Furnace i got same error using khal agility/Tabber as well
Lemons Posted May 1, 2016 Posted May 1, 2016 (edited) The new stable version of OSBot (2.4.58) added permissions to scripts, so they can only read/write to "OSBot/data". Please wait until these scripts are updated for the new permissions. Edited May 1, 2016 by Lemons
EndureCoreNas Posted May 1, 2016 Author Posted May 1, 2016 Ahh thank you for clearing that up. Hopefully it's done quickly~.
Alek Posted May 1, 2016 Posted May 1, 2016 The new stable version of OSBot (2.4.58) added permissions to scripts, so they can only read/write to "OSBot/data". Please wait until these scripts are updated for the new permissions. It was added a few updates ago, this version only changed widget debugger and command line args.
EndureCoreNas Posted May 1, 2016 Author Posted May 1, 2016 It was added a few updates ago, this version only changed widget debugger and command line args. Does this mean the update has nothing to do with it?
Lemons Posted May 1, 2016 Posted May 1, 2016 It was added a few updates ago, this version only changed widget debugger and command line args. Yeah, more of meant the recent push from the dev to stable is why users will be experiencing this. Its easier to understand for them :p
