This does not appear to be the case (0.12.29). The global table seems to not be loaded yet (it exists but is empty) when the migration scripts run.FreeER wrote: I believe (but I am not 100% certain) that lua migration scripts can also access and modify the glob table (so if you previously had a glob.whatever variable that stored an integer and you needed to change it to be a table of integers you could use 'if glob.whatever then glob.whatever={new_index=glob.whatever} else glob.whatever={new_index=default_value} end'.
the lua migration format is exactly the same as the control.lua.
So I guess that means that script.on_configuration_changed is where you have to do it if you're modifying anything in global. I think.