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

Exception in server tick loop crash when updating my origins datapack to 1.19 #581

Closed
MichaelJackson23 opened this issue Jul 30, 2022 · 8 comments
Labels
bug Something isn't working

Comments

@MichaelJackson23
Copy link

I've been making origins on 1.18 for a while now and when it was time to update them to 1.19 this strange crash started happening

crash-2022-07-30_13.09.45-server.txt

Any info on this crash would be incredibly helpful

@notabirb1
Copy link

I'm getting this crash as well, this only happened once I updated to 1.19.1.

@ghost
Copy link

ghost commented Aug 1, 2022

Same issue
crash-2022-07-31_21.13.31-server.txt
was loading custom datapacks for origins mod

@apace100
Copy link
Owner

apace100 commented Aug 1, 2022

Origins is not compatible with 1.19.1 - the file on CF is not marked as compatible with 1.19.1.
The problem is a changed method in the command system, making execute_command actions cause this crash.

@apace100 apace100 pinned this issue Aug 1, 2022
@apace100 apace100 added the bug Something isn't working label Aug 1, 2022
@notabirb1
Copy link

You may want to update the listing on Modrinth then, as it is listed as 1.19.1-compatible on Modrinth (which is why I assumed it would work).

@HyperSoop
Copy link

HyperSoop commented Aug 15, 2022

You may want to update the listing on Modrinth then, as it is listed as 1.19.1-compatible on Modrinth (which is why I assumed it would work).

It does not work. Having the same issue here. Is there any ETA for a fix?

@Not-February
Copy link

A comment on Curse leads me to wonder whether this is caused specifically by selected origins that alter player size. It would certainly match up with my own experience getting this crash, as all of the origins I'd personally tried from Bucolic Origins do indeed have size alterations, but I have yet to test more extensively with origins that don't do anything with the player's size

Could anyone else who has had this issue perhaps clarify what origin datapack/addon they are using/getting the crash with, as well as whether the origin selected that causes the crash alters player size in any way?

Quoting the comment itself for ease of access:

playing on 1.19.2 works fine but any origin that changes size causes this error, causing any server (singleplayer or dedicated) to crash, yes i have pehkui

Description: Exception in server tick loopDescription: Exception in server tick loop
java.lang.NoSuchMethodError: 'int net.minecraft.class_2170.method_9249(net.minecraft.class_2168, java.lang.String)' at Not Enough Crashes deobfuscated stack trace.(1.19.2+build.8) at io.github.apace100.apoli.power.factory.action.EntityActions.lambda$register$15(EntityActions.java:235) at io.github.apace100.apoli.power.factory.action.ActionFactory$Instance.accept(ActionFactory.java:41) at io.github.apace100.origins.power.OriginsCallbackPower.onChosen(OriginsCallbackPower.java:24) at io.github.apace100.origins.component.OriginComponent.lambda$onChosen$0(OriginComponent.java:49) at java.lang.Iterable.forEach(Iterable.java:75) at io.github.apace100.origins.component.OriginComponent.onChosen(OriginComponent.java:49) at io.github.apace100.origins.networking.ModPacketsC2S.lambda$chooseOrigin$0(ModPacketsC2S.java:50) at net.minecraft.server.ServerTask.run(ServerTask:18) at net.minecraft.util.thread.ThreadExecutor.executeTask(ThreadExecutor:157) at net.minecraft.util.thread.ReentrantThreadExecutor.executeTask(ReentrantThreadExecutor:23) at net.minecraft.server.MinecraftServer.executeTask(MinecraftServer:776) at net.minecraft.server.MinecraftServer.executeTask(MinecraftServer:159) at net.minecraft.util.thread.ThreadExecutor.runTask(ThreadExecutor:131) at net.minecraft.server.MinecraftServer.runOneTask(MinecraftServer:758) at net.minecraft.server.MinecraftServer.runTask(MinecraftServer:752) at net.minecraft.util.thread.ThreadExecutor.runTasks(ThreadExecutor:140) at net.minecraft.server.MinecraftServer.runTasksTillTickEnd(MinecraftServer:737) at net.minecraft.server.MinecraftServer.runServer(MinecraftServer:669) at net.minecraft.server.MinecraftServer.method_29739(MinecraftServer:257) at java.lang.Thread.run(Thread.java:833)

@HyperSoop
Copy link

A comment on Curse leads me to wonder whether this is caused specifically by selected origins that alter player size. It would certainly match up with my own experience getting this crash, as all of the origins I'd personally tried from Bucolic Origins do indeed have size alterations, but I have yet to test more extensively with origins that don't do anything with the player's size

Could anyone else who has had this issue perhaps clarify what origin datapack/addon they are using/getting the crash with, as well as whether the origin selected that causes the crash alters player size in any way?

Quoting the comment itself for ease of access:

playing on 1.19.2 works fine but any origin that changes size causes this error, causing any server (singleplayer or dedicated) to crash, yes i have pehkui

Description: Exception in server tick loopDescription: Exception in server tick loop
java.lang.NoSuchMethodError: 'int net.minecraft.class_2170.method_9249(net.minecraft.class_2168, java.lang.String)' at Not Enough Crashes deobfuscated stack trace.(1.19.2+build.8) at io.github.apace100.apoli.power.factory.action.EntityActions.lambda$register$15(EntityActions.java:235) at io.github.apace100.apoli.power.factory.action.ActionFactory$Instance.accept(ActionFactory.java:41) at io.github.apace100.origins.power.OriginsCallbackPower.onChosen(OriginsCallbackPower.java:24) at io.github.apace100.origins.component.OriginComponent.lambda$onChosen$0(OriginComponent.java:49) at java.lang.Iterable.forEach(Iterable.java:75) at io.github.apace100.origins.component.OriginComponent.onChosen(OriginComponent.java:49) at io.github.apace100.origins.networking.ModPacketsC2S.lambda$chooseOrigin$0(ModPacketsC2S.java:50) at net.minecraft.server.ServerTask.run(ServerTask:18) at net.minecraft.util.thread.ThreadExecutor.executeTask(ThreadExecutor:157) at net.minecraft.util.thread.ReentrantThreadExecutor.executeTask(ReentrantThreadExecutor:23) at net.minecraft.server.MinecraftServer.executeTask(MinecraftServer:776) at net.minecraft.server.MinecraftServer.executeTask(MinecraftServer:159) at net.minecraft.util.thread.ThreadExecutor.runTask(ThreadExecutor:131) at net.minecraft.server.MinecraftServer.runOneTask(MinecraftServer:758) at net.minecraft.server.MinecraftServer.runTask(MinecraftServer:752) at net.minecraft.util.thread.ThreadExecutor.runTasks(ThreadExecutor:140) at net.minecraft.server.MinecraftServer.runTasksTillTickEnd(MinecraftServer:737) at net.minecraft.server.MinecraftServer.runServer(MinecraftServer:669) at net.minecraft.server.MinecraftServer.method_29739(MinecraftServer:257) at java.lang.Thread.run(Thread.java:833)

it's because the only way of changing player size is doing the /scale command

@eggohito
Copy link
Collaborator

A bit late, but this should now be fixed in Origins 1.7.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants