Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EvilCraft crashing Minecraft possibly due to failure in spawning blood #139

Closed
cl0ck-byte opened this issue Oct 19, 2022 · 1 comment
Closed
Labels
Mod issue Caused by a bug in the mod, not the pack

Comments

@cl0ck-byte
Copy link

cl0ck-byte commented Oct 19, 2022

User no. 1's crash log

ATM version is 0.1.5
Player no. 1 killed a glow squid and crashed. Possibly because of dropped ink sack item that blocked spawning of EvilCraft's blood stain block?

User no. 2's crash log

Note that it's ATM version 0.1.3
Player no. 2 is unable to describe what exactly is happening, says that crashes occur randomly, independent of their actions.
They didn't kill any mobs during the time when crash occured.

The only thing that could be useful is that it's happening in one particular area, so there might be some room for bats to spawn, and one could suffocate in a wall while being on the same X/Y/Z level as where blood wanted to spawn (Or just another bat in the same area), but that's probably next to impossible.

More crash logs from the same user: no 3; glowing ink sac, no 4; another bat, no 5; and another bat and probably unrelated crash mentioning Create's Flywheel renderer/engine from the same day, same exception description but there's no mention about EvilCraft.

Something I noticed is that bats tend to spawn at y level between 2 and 3 and aren't spread out as much, so there might be a structure that's killing them?

Edit: Here are pictures of that place and all player locations on the map marked with waypoints when they crashed due to a bat. My theory is that bats die on the pointed dripstone and EvilCraft tries to spawn blood and fails.

Bug wasn't reported to EvilCraft's issue tracker yet due to their policy regarding bugs that occur within other modpacks.

@Mitchell5200 Mitchell5200 added the Mod issue Caused by a bug in the mod, not the pack label Jan 18, 2023
@Mitchell5200
Copy link
Contributor

Mod at fault identified, and mod dev contacted,
Duplicate of #307, #447, #553, #580, #649
Note, it's not Evilcraft at fault in these crashes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Mod issue Caused by a bug in the mod, not the pack
Projects
None yet
Development

No branches or pull requests

2 participants