You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have several worlds that crash from mod "luscious" at seemingly random intervals, but it's possible that I installed the mod after creating the world and playing in it for awhile. However, in this particular case I followed the directions and created a new world and put in some tool mods, "luscious", and "Universal geometry realm (a.k.a. flexrealm)". This world always crashed as it was being loaded. I was only ever able to load the world by disabling "luscious".
When I was getting the error (prior to disabling "luscious"), the log file showed the same thing each time I tried to load the world. First there would be the following line:
and then the following (all starting with "ERROR[Main]"):
ServerError: AsyncErr: Lua: finishGenRuntime error from mod 'luscious' in callback environment_OnGenerated(): C:\Program Files\Minetest\bin..\mods\luscious\init.lua:142: attempt to get length of local 'heatmap' (a nil value)
stack traceback:
C:\Program Files\Minetest\bin..\mods\luscious\init.lua:142: in function <C:\Program Files\Minetest\bin..\mods\luscious\init.lua:137>
C:\Program Files\Minetest\bin..\builtin\game\register.lua:429: in function <C:\Program Files\Minetest\bin..\builtin\game\register.lua:413>
Each time I start the world it loads and the progress bar moves, but as soon as it is ready to switch over to the in-game view then it crashes. The log file shows the same error lines as shown above, the only difference being the coordinates of the initial emerge area, though it's always the same size area. It got far enough to create the "luscious" directory within the world's directory, but never created any map files.
Perhaps "luscious" doesn't work well with "Universal geometry realm (a.k.a. flexrealm)" (it does do some strange, though really interesting, things). So, I created another world that only had "luscious" (created and enabled "luscious" prior to first click of "Play Game"). This time it can load the world, but it crashes rather quickly (though back to random timing, just all still within the first 30 seconds) with the errors noted in Issue #2 . For this world it has created some map files in the "luscious" directory (only 27 though). The log file shows the following messages:
ServerError: AsyncErr: ServerThread::run Lua: Runtime error from mod 'default' in callback LuaABM::trigger(): Runtime error from mod 'default' in callback node_on_construct(): C:\Program Files\Minetest\bin..\mods\luscious\init.lua:22: attempt to perform arithmetic on local 'p2' (a nil value)
stack traceback:
C:\Program Files\Minetest\bin..\mods\luscious\init.lua:22: in function 'cmpy'
C:\Program Files\Minetest\bin..\mods\luscious\init.lua:49: in function <C:\Program Files\Minetest\bin..\mods\luscious\init.lua:31>
[C]: in function 'set_node'
...st\bin..\games\minetest_game\mods\default/functions.lua:554: in function <...st\bin..\games\minetest_game\mods\default/functions.lua:534>
Minetest version:
5.3.0 (portable / official release)
Running on:
Microsoft Windows 10
Home Edition
Version 1909+
OS Build 18363.1082
I have several worlds that crash from mod "luscious" at seemingly random intervals, but it's possible that I installed the mod after creating the world and playing in it for awhile. However, in this particular case I followed the directions and created a new world and put in some tool mods, "luscious", and "Universal geometry realm (a.k.a. flexrealm)". This world always crashed as it was being loaded. I was only ever able to load the world by disabling "luscious".
When I was getting the error (prior to disabling "luscious"), the log file showed the same thing each time I tried to load the world. First there would be the following line:
and then the following (all starting with "ERROR[Main]"):
Each time I start the world it loads and the progress bar moves, but as soon as it is ready to switch over to the in-game view then it crashes. The log file shows the same error lines as shown above, the only difference being the coordinates of the initial emerge area, though it's always the same size area. It got far enough to create the "luscious" directory within the world's directory, but never created any map files.
Perhaps "luscious" doesn't work well with "Universal geometry realm (a.k.a. flexrealm)" (it does do some strange, though really interesting, things). So, I created another world that only had "luscious" (created and enabled "luscious" prior to first click of "Play Game"). This time it can load the world, but it crashes rather quickly (though back to random timing, just all still within the first 30 seconds) with the errors noted in Issue #2 . For this world it has created some map files in the "luscious" directory (only 27 though). The log file shows the following messages:
Minetest version:
5.3.0 (portable / official release)
Running on:
Microsoft Windows 10
Home Edition
Version 1909+
OS Build 18363.1082
Using texture pack:
Artelhum
Game:
Minetest Game
The text was updated successfully, but these errors were encountered: