The hopper crash tracker behaves incorrectly if the server brand is null when the crash occurs (IE, the game crashes before the MC|Brand packet is received but after the player joins the game).
When the brand is null, a NullPointerException is caught and handled, and the brand is treated as ~~ERROR~~ NullPointerException: null. Hopper seems to be detecting that the brand is not vanilla and thus treating the server as modded, even when it isn't.
A demo of this: MCX-3002118/77338978 says:
Server brand: ~~ERROR~~ NullPointerException: null
Server type: Integrated singleplayer server
...
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)Given that the client is (most likely) unmodified, and that it's an integrated single player server, the server brand should be vanilla, but is null. Why it's null is beyond the scope of this issue, but hopper shouldn't be assuming it's modded just because it's null. While there are some modded servers that don't send a brand, it can also happen in vanilla and thus the brand being null shouldn't be used to mark an issue as modded-only.
Comments 2
hopper.minecraft.net as a service no longer exists, so this issue no longer applies. It used to be a crash report analysis system, and loading the given link would show more info about a specific crash. However, it was retired a long time ago, and the troubleshooting documentation that was also hosted on it was relocated to the third-party site https://minecrafthopper.net/.
Here's an archived example. It turns out that this one is also an example of this bug, although this report was in multiplayer instead of singleplayer so it is less obvious if the server was modded or not.
In any case, hopper itself is long gone, so this issue no longer applies.
I'm not sure I understand this issue.
Is it still happening?
Could you please provide more details or/and media files. As such we have no repro of this issue.
Also, just a reminder, to make your bug report as effective as possible, please try and include the following steps to reproduce the problem:
Steps to Reproduce:
1.
2.
3.
Observed Results:
(Briefly describe what happens)
Expected Results:
(Briefly describe what should happen)
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.