Jeryn99
commented
3 years ago There is always a log. There may be no crash report but logs for servers are extremely long due to people talking and things going on and etc. Something like players being all kicked due to something happening cannot go wrong without being logged unless forced to act this way. The next time this happens, stop the server and upload latest.log immediately. Do not start the server again without uploading the file first, as the log will be over-written otherwise.
I've known about the armor issue for a while but very little. 1.14.4 is a legacy support version for me and opening it to look at old code is pointless without a very indepth description of the problem, which, when I asked people to make an issue on, it just never happened. The sooner I get an issue created on here, the sooner it is fixed.
Thank you for making the issue, it'll get fixed when you give me a log + when I have some free time that I want to use on a outdated version.
I have noticed alot recently that that on multiplayer servers the regeneration energy has way too much damage output. As it will destroy all armour on a player if they are too close, no matter how strong, the only armour able to withstand it is non survival obtained unbreakable armour. And I have also noticed it times out everyone online if someone is too close to the regeneration, I would offer logs, but when it happens there are no logs about it happening. Since the server does actually crash, only kicks everyone online off. This is for the 1.14.4 version of Regeneration Mod. My apologies if I didn't explain it overly well, nor the best at describing issues, let me know if you need some more clarification.