Closed mrbid closed 2 years ago
This appears to be a "race condition" in a limited manner. Both, skinsdb
and i3
use register_on_joinplayer
to set up their data. However, skinsdb
triggers a formspec update which requires i3
to be initialized already - which is yet not the case. This is also why optional dependencies seem to magically fix things for you.
replaced with
table.insert(core.registered_on_joinplayers, 1, function(player)
Should fix this particular issue.
@mrbid is the given patch makes it work for you ?
Good news, this certainly seems to have fixed it, so far the second login has not crashed the server.
Thank you, I am very happy to have i3 working on my servers. It is a very good inventory and everyone involved in its development has done a really great job.
Any other niggles I may have can be changed in a fork, for example, no API to add auxiliary buttons to the bottom bar with home, settings, etc, and if I am a creative user there seems to be no way for me to see crafting recipes which is a bit annoying to have to keep revoking creative to see them but, it's not the end of the world. But I guess it would be nice to have a little button to toggle between recipe view and creative.
Guys you can't just close this issue, we need to workout why this is happening. The skinsdb and 3d_armor mods are the latest versions. Why is this happening? Minetest server and client 5.5.0.
I will connect to a server on a fresh boot (from an account with creative), everything is fine, I will disconnect and reconnect with the same account and on the re-connect it throws me this error right as my player joins the game. Every time without fail.
Removing skinsdb solves this problem.