Skip to content

Crash at startup #5

Closed
Closed

Description

@TheNether02

Logs :

[18:58:07 ERROR]: Error occurred while enabling ServerChangelogs v1.2.0 (Is it up to date?)
java.lang.RuntimeException: Failed to start platform entrypoint
at ServerChangelogs-paper-1.2.0.jar//com.codingcat.changelogs.paper.PaperChangelogsPlatform.onEnable(PaperChangelogsPlatform.java:42) ~[?:?]
at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:279) ~[paper-api-26.2.build.56-alpha.jar:?]
at io.papermc.paper.plugin.manager.PaperPluginInstanceManager.enablePlugin(PaperPluginInstanceManager.java:201) ~[paper-26.2.jar:26.2-56-8cd4f47]
at io.papermc.paper.plugin.manager.PaperPluginManagerImpl.enablePlugin(PaperPluginManagerImpl.java:109) ~[paper-26.2.jar:26.2-56-8cd4f47]
at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:519) ~[paper-api-26.2.build.56-alpha.jar:?]
at org.bukkit.craftbukkit.CraftServer.enablePlugin(CraftServer.java:633) ~[paper-26.2.jar:26.2-56-8cd4f47]
at org.bukkit.craftbukkit.CraftServer.enablePlugins(CraftServer.java:590) ~[paper-26.2.jar:26.2-56-8cd4f47]
at net.minecraft.server.MinecraftServer.initPostWorld(MinecraftServer.java:648) ~[paper-26.2.jar:26.2-56-8cd4f47]
at net.minecraft.server.dedicated.DedicatedServer.initServer(DedicatedServer.java:343) ~[paper-26.2.jar:26.2-56-8cd4f47]
at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1267) ~[paper-26.2.jar:26.2-56-8cd4f47]
at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:303) ~[paper-26.2.jar:26.2-56-8cd4f47]
at java.base/java.lang.Thread.run(Thread.java:1474) ~[?:?]
Caused by: java.lang.RuntimeException: Resource not found: lang\en_US.yml
at ServerChangelogs-paper-1.2.0.jar//com.codingcat.changelogs.base.util.ResourceUtil.readResourceAsString(ResourceUtil.java:33) ~[?:?]
at ServerChangelogs-paper-1.2.0.jar//com.codingcat.changelogs.base.util.ResourceUtil.readResourcesAsString(ResourceUtil.java:25) ~[?:?]
at ServerChangelogs-paper-1.2.0.jar//com.codingcat.changelogs.base.ServerChangelogs.onStart(ServerChangelogs.java:64) ~[?:?]
at ServerChangelogs-paper-1.2.0.jar//com.codingcat.changelogs.paper.PaperChangelogsPlatform.onEnable(PaperChangelogsPlatform.java:40) ~[?:?]
... 11 more
[18:58:07 INFO]: [ServerChangelogs] Disabling ServerChangelogs v1.2.0
[18:58:07 INFO]: [ServerChangelogs] console.shutdown

Plugins :
[18:59:51 INFO]: ℹ Server Plugins (2):
[18:59:51 INFO]: Paper Plugins (1):
[18:59:51 INFO]: - ServerChangelogs
[18:59:51 INFO]: Bukkit Plugins (1):
[18:59:51 INFO]: - packetevents

Version 26.2 Paper
Plugin Version : 1.2.0 and 1.2.1

Activity

  1. DRM001 commented on Sep 25, 2026

    @DRM001

    I also have this issue too. Running on paper 26.2 Build 129 with PacketEvents 2.14.0 and ServerChangelogs 1.2.1. This is what I get in the console:

    Image
  2. codingcat2468 commented on Sep 25, 2026

    @codingcat2468
    Owner

    The issue for this should hopefully be fixed in the latest build of the plugin:
    https://github.com/codingcat2468/ServerChangelogs/actions/runs/36198415954/artifacts/10890876693

  3. Sonic3Modder commented on Sep 26, 2026

    @Sonic3Modder

    I think its because of how it reads the .yml

  4. Sonic3Modder commented on Sep 26, 2026

    @Sonic3Modder

    it expects /lang/en_US

  5. Sonic3Modder commented on Sep 26, 2026

    @Sonic3Modder

    but it recives \lang\en_US

  6. codingcat2468 commented on Sep 27, 2026

    @codingcat2468
    Owner

    Yeah that is indeed the case, could someone on windows test the build I linked above to see if it fixes the issue?

  7. DRM001 commented on Sep 27, 2026

    @DRM001

    I’ll spin up a test server tomorrow when I get home from work and test it out.

  8. Sonic3Modder commented on Sep 27, 2026

    @Sonic3Modder
  9. Berkayprof commented on Sep 29, 2026

    @Berkayprof

    @TheNether02 I think this issue can be closed, since the issue has already been resolved in the PR #10 and Sonic3Modder has already confirmed the fix?

  10. codingcat2468 commented on Sep 29, 2026

    @codingcat2468
    Owner

    @DRM001 are you able to confirm it works for you as well? Then I think we're good to close the issue

  11. DRM001 commented on Sep 30, 2026

    @DRM001

    Sorry not had a chance to test yet due to other commitments. I will test this evening.

  12. DRM001 commented on Sep 30, 2026

    @DRM001

    The new version installs just fine on Paper 26.2 (Build 129). However, LuckPerms could not find the permission nodes when attempting to set up permissions so I manually added them as follows:

    Image

    After adding the above everything seems to work correctly.

    Thank you

  13. DRM001 commented on Sep 30, 2026

    @DRM001

    Little update - when leaving on the 'Server Changelogs' page for a while my connection timed out and I was disconnected according to the console. The Server Changelogs page stayed there though until I clicked the Exit button then I was dropped back to the disconnected message within Minecraft.

    This is with the default config.yml file set to CONFIGURATION mode.

  14. DRM001 commented on Sep 30, 2026

    @DRM001

    Here is what the console says:

    Image
  15. DRM001 commented on Oct 12, 2026

    @DRM001

    Also, is the latest build working with 26.3 (https://github.com/codingcat2468/ServerChangelogs/actions/runs/36198415954/artifacts/10890876693)? I only ask as the one downloaded from Modrinth (ServerChangelogs-paper-1.2.1.jar) also seems to throw the start up issue as previously mentioned.

  16. codingcat2468 commented on Oct 14, 2026

    @codingcat2468
    Owner

    Oh yeah sorry, I've been quite busy for the last week so I wasn't able to look at this until now! Great to see that it does work, I do want to release a new version pretty quickly so that the fix will be available on modrinth.

    About the timeout issue, I kind of expected this already, but wasn't able to reproduce it myself. It shouldn't be a major problem at least (as most people won't stay on the page for that long), but it is an issue I've come across already with blocking the configuration phase. If you want, you can create a new issue for this, and I'll see if there's a way to fix that. (It's likely a server-side timeout on the connection level, which does make it a bit difficult to prevent)

    Also I'll close this issue then, as the original problem seems to be resolved!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions