453 posts
Location
Holland
Posted 16 January 2016 - 02:41 PM
so the bug is really simple, when you say for example "set shell.allowed_disk_startup false", it will "unset" the value instead of setting it to false. which makes it so the computer reads the default value because it doesnt exist (true in this case). so you will have to use the settings API or edit the .settings file right now to be able to disable any form of default "true" value, the startup settings for example
Edited on 16 January 2016 - 01:43 PM
724 posts
Location
Kinda lost
Posted 16 January 2016 - 05:00 PM
Darn that one went right by everyone.
In set program lines: 31-32 are:
local oldValue = settings.get( sValue )
if value then
And should be:
local oldValue = settings.get( sName )
if value ~= nil then
Problem duplicated to git here:
https://github.com/dan200/ComputerCraft/issues/85
453 posts
Location
Holland
Posted 16 January 2016 - 05:48 PM
thanks for backing me up :)/>
7083 posts
Location
Tasmania (AU)
Posted 16 January 2016 - 11:22 PM
Heh, I'd spotted the removal behaviour. Didn't figure out the consequences. Should've kept reading, I guess! :lol:/>
724 posts
Location
Kinda lost
Posted 16 January 2016 - 11:36 PM
Will be resolved in 1.78 according to git.
524 posts
Location
Cambridge, England
Posted 18 January 2016 - 08:22 PM
Yep, this is solved