Problem with consistently accessing lua tables

[zeuner]

This is probably easy for the more experienced developers, nonetheless I didn't find an easy answer:

I noticed that the lua scripting is inconsistently accessing data depending on the context where the access is from:

I have some tables in local variables which get initialized from "init.lua".

Now, when I access them from scripts triggered from "ScriptApiServer::on_chat_message", everything works fine.

But when I access the same variables from "ScriptApiEnv::environment_Step" (for example due to "minetest.after"), they end up being used uninitialized.

What causes this, and what is the recommended way to access data tables from all contexts where lua scripting may be used?

Thanks in advance!

[Nathan.S]

Locals are local, so they'll only exist where you have defined them. If you want to use the same variables, with the same data, in multiple areas put them in a global table.
something like this;

Code: Select all

mod.table={['variable'] = value}

[sorcerykid]

If all your related functions are defined within the same script (i.e. init.lua), they can easily share variables that are local to that script. Simply declare the variable(s) as local myvar at the head of the file, rather than within each specific function.

[rubenwardy]

Note that some variables should not typically be stored between callbacks. ObjectRefs may expire, resulting in their methods returning nil