The Lua Environment (Advanced)

By default, the O3DE component entity Lua environment is a single Lua environment \(or `lua_State`\). This environment is bound to the BehaviorContext that is owned by the ComponentApplication. Because of this, it has access to all API operations that are reflected on startup.

Adding other VMs

You may add more ScriptContext instances using the ScriptSystemBus \(either call `AddContextWithId`, or create your own and call `AddContext`\). If you want your new context to be available for debugging, you must register it with ScriptDebugAgentBus::RegisterContext.

Reusing code

Lua provides the capability to load and execute scripts from other Lua files using the built-in Lua require function. It’s important to note that this function requires a special path format. The file path is delimited by periods instead of slashes, has no .lua file name extension, and is relative to the O3DE assets directory. For example, if you want to use the require function to give your scripts some common functionality from the project’s Scripts directory, you can use code similar to the following example.

local library = require("Scripts.MyLibraryFile")