multiplayer support?
Is it possible to add multiplayer support?
I'm new to minetest. I'm trying setup a server to have a gathering inside qiskit blocks.
For some reason it is always crashing, even when joining a localhost server.
Thx
Hi Omar. I’ve seen students do that, but haven’t done it myself. You might check the Minetest site for information.
Regards, James (Jim) Weaver
On Dec 7, 2020, at 4:24 AM, Omar Costa Hamido [email protected] wrote:
Is it possible to add multiplayer support?
I'm new to minetest. I'm trying setup a server to have a gathering inside qiskit blocks.
For some reason it is always crashing, even when joining a localhost server.
Thx
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.
Hi James :)
I've been able to figure out setting up vanilla minetest servers.
But for some reason when I try to host a qiskitblock server I get this crash:

All the best, Omar
btw, the techspot link is nice to have direct access to the compiled minetest mac app. But unfortunately it seems to only be hosting the lastest version: 5.4. Luckily it seems to be able to launch qiskitblocks in single player mode. It's just the multiplayer mode that is tricky rn.
To work around the error I wrote this little patch for q_command/init.lua:
2512,2515c2512,2517
< local player_inv = minetest.get_player_by_name("singleplayer"):get_inventory()
< local player_inv_main_size = player_inv:get_size("main")
< player_inv:set_size("main", 0)
< player_inv:set_size("main", player_inv_main_size)
---
> for _,player in ipairs(minetest.get_connected_players()) do
> local player_inv = player:get_inventory()
> local player_inv_main_size = player_inv:get_size("main")
> player_inv:set_size("main", 0)
> player_inv:set_size("main", player_inv_main_size)
> end
This makes the game playable in multiplayer. However, I assume it has unintended side effects even though I don't have any further knowledge of the QiskitBlocks code. Nevertheless, we tried to play in multiplayer. We were two players and played through escape rooms 1-14 (level 1). In the 15th room we somehow managed to loose the necessary blocks. I don't remember exactly how it happened. I think one player took the blocks from the chest, placed them on the circuit and later jumped through the portal while the other player was in room 14.
Even though the game is not optimized for multiplayer, we enjoyed tackling the puzzles together. Situations like the one described above can be remedied with the help of the /give command or creative mode.
Sweet!
On Sun, May 2, 2021, at 5:11 AM, Hiradur wrote:
To work around the error I wrote this little patch:
2512,2515c2512,2517 < local player_inv = minetest.get_player_by_name("singleplayer"):get_inventory() < local player_inv_main_size = player_inv:get_size("main") < player_inv:set_size("main", 0) < player_inv:set_size("main", player_inv_main_size)
for _,player in ipairs(minetest.get_connected_players()) do local player_inv = player:get_inventory() local player_inv_main_size = player_inv:get_size("main") player_inv:set_size("main", 0) player_inv:set_size("main", player_inv_main_size) end
This makes the game playable in multiplayer. However, I assume it has unintended side effects even though I don't have any further knowledge of the QiskitBlocks code. Nevertheless, we tried to play in multiplayer. We were two players and played through escape rooms 1-14 (level 1). In the 15th room we somehow managed to loose the necessary blocks. I don't remember exactly how it happened. I think one player took the blocks from the chest, placed them on the circuit and later jumped through the portal while the other player was in room 14.
Even though the game is not optimized for multiplayer, we enjoyed tackling the puzzles together. Situations like the one described above can be remedied with the help of the /give command or creative mode.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JavaFXpert/QiskitBlocks/issues/19#issuecomment-830776734, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACLZ5WQFU3QTDDWXDXQFCDTTLUJMRANCNFSM4UQFNBNQ.