Made an Origin that spawns in the Atum, then, it can never respawn. :V
Darkmega18 opened this issue ยท 9 comments
As the name says on the tin. I've made an origin which spawns originally in the atum, despite the atum's starting spawn not being set in configs.
When I equip it I will spawn in the atum, but getting killed results in a lack of existence forever because it won't let me respawn. Being normal or anything else when being in overworld then going to atum and dieing just spawns where it's meant to spawn. But even once becoming my nomad origin and dieing not in the atum I proceed to not exist anymore again.
Minecraft: 1.16.5
Origins forge: Origins-1.16.5-0.7.3.5-forge
Forge: 36.1.24
Atum: Atum-1.16.5-2.2.5
[and many other mods...]
Afterwards, there the only thing I have saying something might be wrong in the console is related to a message saying:
Render thread: Couldn't find component for entity "Darkmega18"
I'm not sure whats going on, or if it's related to atum itself perhaps.
on a reload, I remain stuck dead it seems. ._.
I'll try to see what I can come up with, but in the meantime, try to use Atum's config option if you want to spawn in the world.
thats the thing, I'm trying to split up some of the specialized origins to different dimensions or locations in the world. like merlings starting in oceans, atum types in atum, ender types in end, so-on and so forth. it's just weird it started happening with these specifically. but I'll make a cross post of the issue to atum and see if they have an idea?
edit:
on a reload, I remain stuck dead it seems. ._.
scratch that, it seems to have woken up and worked somehow eventually after a force restart with no touching of the files yet... but it's still an odd issue. which has happened most of the time.
well, girafee basically just passed it straight back. so uh... yep. :V Hope you can figure something out.
I seem to have a similar issue with the blazeborn. So it may be simpler than I imagined.
The issue disappeared after I edited something with my Nomad related to a broken shiver effect cause of commas... but then I went and made the Efreet, who also spawns in atum, and I happened to die to some random shenanigans with an apotheosis boss and now I'm experiencing the same issue again. I'm not sure if I got lucky, or if it's continuing.
also, when I go "return to main menu" it ends up in a broken state of forever saving the game until I end task/process when this occurs.
I'm lost on it.
My guess would be that I'm trying to spawn you in an unloaded dimension, but forge dimension loading is a mess.
I'll try to see what I can come up with, but in the meantime, try to use Atum's config option if you want to spawn in the world.
So I'll be honest, I don't have high hopes for this to work, but the bug I fixed was basically preventing you from spawning on non-solid blocks, such as soul sand. If you had such a spawn point, this might be fixed.
I assume non-solid blocks also include sand layers? Atum is covered in them so that may have contributed.
well, thats actually not a bad shot. it does cover a lot of edges around biomes etc with sand layers for looks. and spawn point isn't always exact right? so every time I try, it could just be spawning me near a layer of blocks that it gets tripped up on. so, we'll see is all I'm saying. thanks for your efforts. cause I honestly actually doubt it's related to unloading. cause while dead I can literally watch my killer walk off into the sunset and the sun go down/come up. :V