Moving from 0.10 to 0.11: What do I do without LUAU_PATH env var?

[StormLight14]

The bevy_mod_scripting crate which adds Lua and Luau scripting to Bevy games used mlua 0.10 until recently. Previously, i set the LUAU_PATH environment variable to assets/scripts/?.luau;assets/scripts/?.lua for require() to properly work in my scripts.

I notice that in mlua 0.11 this no longer seems to exist and when i search the repo for LUA_PATH and LUAU_PATH I get nothing.

Is there something I can do as a user of bevy_mod_scripting to set the path or does it require changing something in bevy_mod_scripting's code itself?

This file is where bevy_mod_scripting does Lua::new() if this is where it would be required to change something? Although I'm not totally sure.

Sorry if it's a dumb question I'm not very good at this stuff :3
ty in advance for any help

[MLuc24]

There is no replacement env var, because 0.11 swapped the whole mechanism rather than renaming it. The changelog entry is "New require-by-string for Luau (with Require trait and async support)" — that is Luau's own upstream resolution scheme, and it has no notion of a search-path variable.

What replaced it is a trait the host application implements or picks:

pub fn create_require_function<R: Require + MaybeSend + 'static>(&self, require: R) -> Result<Function>

with FsRequirer as the filesystem implementation shipped in the box — that is your old TextRequirer, renamed in this release. Resolution is relative rather than path-list based: one changelog entry notes require "resolves included Lua files relative to the current directory", and aliases come from .luaurc configuration files. You can see that in the trait's own documentation, where jump_to_alias is described as receiving "an exact path from a configuration file".

So the shape of the answer for you depends on something in bevy_mod_scripting rather than in mlua: whether it installs FsRequirer::new() or its own Require implementation.

If it uses the stock one, you are not blocked. Put a .luaurc next to your scripts declaring an alias for your script directory and require through that, and relative requires between your own scripts work without any configuration at all. That is entirely on your side of the line.

If it supplies a custom requirer — quite likely for an engine that loads scripts through its own asset system rather than straight off disk — then no file you write will change the resolution, because that implementation decides. In that case it is a change in their code, and the useful thing to open on their tracker is not "please restore LUAU_PATH" but "please expose the requirer, or accept a script search path in the plugin config", since the trait gives them a clean way to do it.

Worth grepping their source for create_require_function before filing anything — that call, and what it is handed, answers which of the two you are in.

[StormLight14]

yo thanks even if it was ai response :3
.luarc alias in the same directory worked, i had it in the project's root directory and that wouldnt work

[StormLight14]

... never mind it's using the one i had in root? why does it magically work now? who knows, well thanks anyway still

[StormLight14]

So if someone else gets this issue: just use a .luaurc file with an alias pointing towards whatever path you originally had the env variable set to.