0.3.3-a | Pizza or Bread crafting with create:mechanical_mixer > crash Server

[zukkl]

Two similar situations:

Trying to make pizza or dough with the mechanical mixer from Create causes the server to crash.
The same applies to different types of flour in the mixer at the same time

My guess:
You can top the pizza, or just make a Margaritha pizza from cheese, dough, tomato sauce. Create does not understand which recipe is wanted, as both are an option. A filter does not help.

My crash log:
https://mclo.gs/AwSINCH

To get the server running again:
(troubleshooting on linux with Problem by crafting with Mechanical Mixer with tf:food/*)

1. if your server is crashed and if present ‘./world/session.lock’, remove it.
   MAKE SURE THAT THE SERVER IS REALLY NO LONGER RUNNING!
2. if the port is still open ‘ss -tulpn | grep PORT’, close it again with the attached PID using ‘kill PID’.
3. if you have started the server and the session.lock was still active befor you started, check the crash reports, which could refer to ./logs/kubejs/startup.log.
   3.1 Interestingly, the gtceu.yaml file is overwritten again if the server was started in session.lock mode. Check this with the command: cat YOUR-PATH/config/gtceu.yaml | grep -iE ‘highTierContent|enablePlatformConverters’ and change them now, if you need it.
4. upload the crash report from ‘./crash-reports/your-latest-crash.server.log to https://mclo.gs/. Above you can see which block has to be removed you'll find it on the top of document.
5. if point 4. does not work, search in the crash log in the editor with Ctrl + F or with nano with ctrl + w for the following line: ‘Block location: World: (’
   Alternatively, use this console command:
   cat ./crash-reports/YOUR-CRASH-server.txt | grep ‘Block location: World: “ | sed -n ”s/.Block location: World: (([^)])).*/\1/p’ | head -n 1
6. put the command into the clipboard ‘setblock YOUR-coordinates minecraft:air’
7. start the server and spam the command continuously after the recipe initialisation. Good luck.

If you have still installed the voicemod, and you started the server also session.lock is active, it is possible, that this task will not shut down. >> show with ss -tulpn also your voice-mod port. thats still an zombie-task.

and the most important thing: no backup - no pity