[mc 1.15.2]dying while teleporting
joinmod opened this issue ยท 10 comments
Please read the FAQ before submitting a bug report!
Bug description
when you trying return to overworld by some reason you start dying and loosing all XP but when you go back to mining dimension you stop dying and if you re join to world you XP restores
Steps to reproduce the issue
- go to mining dimension
- mine there
- try go back to overworld
- See error
Expected behavior
successful return to overworld with LVL and not sufficating
Log files
here logs.
Versions
- Minecraft version 1.15.2
- Forge version 31.2.30
- Mod version 1.0.4
Other mods
using mod pack HR: New Beginnings all mods updated manually
Screenshots (Optional)
i have video shows how this is happening
UPD1:
Unfortunately I am not able to reproduce this issue. This is most likely caused by another mod.
Does this issue occur without any other mods? If not, please narrow down the mod that causes this.
I can't see the death message in your logs. Are you sure these are the correct logs?
i think i found problem, its caused by performant
mixinbootstrap 1.0.3 (lib for performant), performant 3.10m, (this time i tried with adv. mining dimension 1.0.6)
i think he messing up with portals or dimension loading to optimize loading and lags (and yes i have render problem with textures so... dont pay attention on that)
i loaded a test world and found out what only some coordinations will kill you and portal from mining dimension will be in overworld.
here another video
world seed: -6476272575931298853 (superflat)
mining portal coordination: -103, 4, -244
ok so i created a new profile with performant and adv mining dimension for fast loading (new one not modpack) so first time with performant mining dimension getting fatal error but if turn OFF performant and then got to dimension and when ON fatal error does not appear until you create a new profile with 1.15.2 forge and install these mods
LOG
upd: this log from modpack with disabled all mods except those 3 mods
It seems that this is a performant issue. Can you please report this bug on their tracker aswell?
From my testing, this seems to only be a server related issue. When I disabled performant on my test server and then the production server the issue resolved.