WURST Lasted version files out,say error

Yuu-Sakuma

Hello Alexander01998,i downloaded wurst hacked client on lasted version mc 1.21,it crashes when i turn on freecam sometimes, you can't predict when it will happen and it's even possible that it's not because of freecam
mods:

baritone

cloth-config

collective

eating-animation

entityculling

fabric api

fast quit

fasttraiding

ferritecore

infinitietraiding

iris

journey map

journey mao webmap

lithiun

modmenu

resees sodium options

replay mod

sodium extra

sodiun

trade -cycling

Wurst client-v7.45-MC 1.21.1

SHADER:ComplementaryReimagined_r5.2.2

RESOURPACK: Pixlli V33 1.21-1.13 128x
Yes, I know that the version is older, but even if there was a version of Wurst client v44 MC-.21 wrote the same thing, but why?

I'm playing a single

changelog says that wurst is problem (quote)

[07:36:30] [main/INFO]: Loading Minecraft 1.21 with Fabric Loader 0.15.11

[07:36:30] [ForkJoinPool-1-worker-9/WARN]: Mod wurst uses the version v7.45-MC1.21.1 which isn't compatible with Loader's extended semantic version format (Could not parse version number component 'v7'!), SemVer is recommended for reliably evaluating dependencies and prioritizing newer version

HOW TO FIX?

Alexander01998

Hey Yuu-Sakuma, can you please send me the crash report file? It should give more details on what's going wrong.

Just in case you don't know, here is how to find your .minecraft/crash-reports folder:

Windows: Open your Windows Explorer and type %appdata%/.minecraft/crash-reports into the address bar.
(Alternatively, you can press Win+R and type in the same thing.)

Linux: Open your File Explorer and type ~/.minecraft/crash-reports into the address bar.

Mac: Open your Finder and type ~/Library/Application Support/minecraft/crash-reports into the address bar.

Yuu-Sakuma

Ok, I'm sorry,im forgot send crash-report,here send file?

Alexander01998

Yuu-Sakuma Yes, please attach the crash report file here in the thread.

Yuu-Sakuma

Alexander01998 strange,i can't fing this file and problem She's gone,as soon as I appear, I'll send it here then

Yuu-Sakuma

Alexander01998 I found it

2024-08-09-61.log

184kB

Yuu-Sakuma

Alexander01998

crash-2024-08-10-073547-client.txt

20kB

Alexander01998

Hey Yuu-Sakuma,

Thanks for sharing the log file. From what I can see, it doesn't look like your game actually crashed here. This log shows a session that was running fine for about five hours. Maybe this is the wrong file?

Also, I noticed you were still using Wurst 7.44 in this session. If you haven't already, I'd recommend that you update to Wurst 7.45, just to make sure you have all of the latest bugfixes. This way, we can be sure that your crash isn't caused by an old bug that has already been fixed.

Let me know if you find the right crash report file or if you have any further questions.

Alexander01998

Hey Yuu-Sakuma,

I just noticed your second file upload after I sent that last message. This is the crash report file I was looking for, thanks for sending it! I can confirm that Wurst is causing your crash here, specifically the MobSpawnESP hack.

These types of random occasional crashes are a known bug with MobSpawnESP that unfortunately is quite complicated to fix. I might need to do a full MobSpawnESP rewrite to resolve it. But for now, you can work around the issue by simply keeping MobSpawnESP turned off.

Hope this helps!

Yuu-Sakuma

Hey Alexander01998 ! Maybe it is him, BUT he was turned off when I played,And the problem appeared when I turned it on Freecam

Thanks for the answer, but to the first message I will say that, yes, I play a lot, and I use the latest version WURST , This problem was on the new version too, and as I wrote earlier the problem went away, but it was still there,

Yuu-Sakuma

Alexander01998 again 🙁
I can't send file,(The request payload was too large.)

i turn Freecam and that's all

minecraft wrote in log file

Yuu-Sakuma

Alexander01998 teach me to read logs and crash-reports

Alexander01998

Hey Yuu-Sakuma,

First off, I've increased the upload size limit, so you should now be able to send that file without getting the "payload too large" error.

Now, about reading Minecraft logs and crash reports: while I can try to explain the basics, it's probably not something that one can fully teach in just one forum post. Reading these files generally requires a fair bit of knowledge about how Minecraft and Java work, especially when it comes to understanding stack traces, which are the parts of the crash reports that show you what exactly went wrong and where.

Here’s a quick rundown though:

Log files: These just record what happens during a game session, but that doesn't necessarily mean there's an issue. Each line starts with a timestamp, so you know exactly when something happened. But beyond the timestamps, there's no strict rule on what gets logged. It's often just a mix of things that developers think might be useful to see. For example, Minecraft typically logs all chat messages.
Crash report files: These get generated when your game actually crashes. They contain a stack trace which shows the exact error and what led up to it - down to the specific file, method, and line number where the problem occurred. Minecraft's own code will usually look a bit cryptic (because it's obfuscated), but methods belonging to mods should be readable. Crash reports also include system information and a list of mods with all their versions, which can be really useful when diagnosing issues. Sometimes you'll even see extra info, like the NBT data of a block or entity that caused the crash.

Keep in mind that most of these files also have a timestamp in their name (e.g. crash-2024-08-15_15.47.43-client.txt), which can help you to find the right file for a particular crash or other problem.

Hope this helps!

Yuu-Sakuma

Alexander01998 thx,idk what happened
complains about WURST

tl-logger6817884529437736358.txt

1MB

Alexander01998

Uhh, Yuu-Sakuma, this is not how you spell Wurst:

at journeymap_webmap.service.webmap.kotlin.routes.SkinKt.skinGet(skin.kt:22) ~[journeymap-webmap-fabric-1.21-1.0.1.jar:?]

This log file is complaining about JourneyMap, over and over again for a megabyte of text, and then there is a JVM crash at the end, interrupted by another JourneyMap error:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ff898d6428c, pid=14744, tid=6916
#
# JRE version: OpenJDK Runtime Environment Microsoft-9388422 (21.0.3+9) (build 21.0.3+9-LTS)
# Java VM: OpenJDK 64-Bit Server VM Microsoft-9388422 (21.0.3+9-LTS, mixed mode, tiered, compressed class ptrs, z gc, windows-amd64)
# Problematic frame:
# C[06:40:48] [JettyServerThreadPool-374/WARN]: Uncaught exception
java.lang.NullPointerException: null
	at journeymap_webmap.service.webmap.kotlin.routes.SkinKt.skinGet(skin.kt:22) ~[journeymap-webmap-fabric-1.21-1.0.1.jar:?]
	at io.javalin.router.Endpoint.handle(Endpoint.kt:52) ~[io_javalin_javalin-6.1.6-1549561cfa746969.jar:?]
	at io.javalin.router.ParsedEndpoint.handle(ParsedEndpoint.kt:15) ~[io_javalin_javalin-6.1.6-1549561cfa746969.jar:?]
	at io.javalin.http.servlet.DefaultTasks.HTTP$lambda$9$lambda$7$lambda$6(DefaultTasks.kt:52) ~[io_javalin_javalin-6.1.6-1549561cfa746969.jar:?]
	at io.javalin.http.servlet.JavalinServlet.handleTask(JavalinServlet.kt:99) ~[io_javalin_javalin-6.1.6-1549561cfa746969.jar:?]
	at io.javalin.http.servlet.JavalinServlet.handleSync(JavalinServlet.kt:64) ~[io_javalin_javalin-6.1.6-1549561cfa746969.jar:?]
	at io.javalin.http.servlet.JavalinServlet.handle(JavalinServlet.kt:50) ~[io_javalin_javalin-6.1.6-1549561cfa746969.jar:?]
	at io.javalin.http.servlet.JavalinServlet.service(JavalinServlet.kt:30) ~[io_javalin_javalin-6.1.6-1549561cfa746969.jar:?]
	at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:723) ~[jakarta_servlet_jakarta_servlet-api-6.1.0-74acdd294210a01e.jar:?]
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:764) ~[org_eclipse_jetty_jetty-servlet-11.0.20-cd4afb88e3db5f0a.jar:?]
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:529) ~[org_eclipse_jetty_jetty-servlet-11.0.20-cd4afb88e3db5f0a.jar:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221) ~[org_eclipse_jetty_jetty-server-11.0.20-43a41c523fa8fc71.jar:?]
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1580) ~[org_eclipse_jetty_jetty-server-11.0.20-43a41c523fa8fc71.jar:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221) ~[org_eclipse_jetty_jetty-server-11.0.20-43a41c523fa8fc71.jar:?]
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1381) ~[org_eclipse_jetty_jetty-server-11.0.20-43a41c523fa8fc71.jar:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:176) ~[org_eclipse_jetty_jetty-server-11.0.20-43a41c523fa8fc71.jar:?]
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:484) ~[org_eclipse_jetty_jetty-servlet-11.0.20-cd4afb88e3db5f0a.jar:?]
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1553) ~[org_eclipse_jetty_jetty-server-11.0.20-43a41c523fa8fc71.jar:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:174) ~[org_eclipse_jetty_jetty-server-11.0.20-43a41c523fa8fc71.jar:?]
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1303) ~[org_eclipse_jetty_jetty-server-11.0.20-43a41c523fa8fc71.jar:?]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:129) ~[org_eclipse_jetty_jetty-server-11.0.20-43a41c523fa8fc71.jar:?]
	at org.eclipse.jetty.server.handler.StatisticsHandler.handle(StatisticsHandler.java:173) ~[org_eclipse_jetty_jetty-server-11.0.20-43a41c523fa8fc71.jar:?]
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:122) ~[org_eclipse_jetty_jetty-server-11.0.20-43a41c523fa8fc71.jar:?]
	at org.eclipse.jetty.server.Server.handle(Server.java:563) ~[org_eclipse_jetty_jetty-server-11.0.20-43a41c523fa8fc71.jar:?]
	at org.eclipse.jetty.server.HttpChannel$RequestDispatchable.dispatch(HttpChannel.java:1598) ~[org_eclipse_jetty_jetty-server-11.0.20-43a41c523fa8fc71.jar:?]
	at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:753) ~[org_eclipse_jetty_jetty-server-11.0.20-43a41c523fa8fc71.jar:?]
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:501) ~[org_eclipse_jetty_jetty-server-11.0.20-43a41c523fa8fc71.jar:?]
	at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:287) ~[org_eclipse_jetty_jetty-server-11.0.20-43a41c523fa8fc71.jar:?]
	at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:314) ~[org_eclipse_jetty_jetty-io-11.0.20-f152e268d66cfe47.jar:?]
	at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:100) ~[org_eclipse_jetty_jetty-io-11.0.20-f152e268d66cfe47.jar:?]
	at org.eclipse.jetty.io.SelectableChannelEndPoint$1.run(SelectableChannelEndPoint.java:53) ~[org_eclipse_jetty_jetty-io-11.0.20-f152e268d66cfe47.jar:?]
	at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.runTask(AdaptiveExecutionStrategy.java:421) ~[org_eclipse_jetty_jetty-util-11.0.20-ca3d17b4583742f1.jar:?]
	at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.consumeTask(AdaptiveExecutionStrategy.java:390) ~[org_eclipse_jetty_jetty-util-11.0.20-ca3d17b4583742f1.jar:?]
	at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.tryProduce(AdaptiveExecutionStrategy.java:277) ~[org_eclipse_jetty_jetty-util-11.0.20-ca3d17b4583742f1.jar:?]
	at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.run(AdaptiveExecutionStrategy.java:199) ~[org_eclipse_jetty_jetty-util-11.0.20-ca3d17b4583742f1.jar:?]
	at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:411) ~[org_eclipse_jetty_jetty-util-11.0.20-ca3d17b4583742f1.jar:?]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:969) ~[org_eclipse_jetty_jetty-util-11.0.20-ca3d17b4583742f1.jar:?]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.doRunJob(QueuedThreadPool.java:1194) ~[org_eclipse_jetty_jetty-util-11.0.20-ca3d17b4583742f1.jar:?]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1149) ~[org_eclipse_jetty_jetty-util-11.0.20-ca3d17b4583742f1.jar:?]
	at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]
  [lwjgl_stb.dll+0x4428c]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\alina\AppData\Roaming\.minecraft\home\fabric-loader-0.15.11-1.21\hs_err_pid14744.log
[1913.969s][warning][os] Loading hsdis library failed
#
# If you would like to submit a bug report, please visit:
#   https://aka.ms/minecraftjavacrashes
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

This JVM crash doesn't tell us exactly what caused the issue, just that it occurred in the lwjgl_stb.dll file from LWJGL and that you have an hs_err_pid14744.log file that might contain more useful information.

Given that there are zero abnormal log entries mentioning Wurst (the string "wurst" only appears six times in the entire file and all of these entries are normal), but about a megabyte of abnormal log entries mentioning JourneyMap, it seems much more likely that JourneyMap might be causing your crash here.

Hope this helps! Let me know if you'd like to take a closer look at the hs_err_pid14744.log file next.