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

XML_ERROR_PARSING when joining a singleplayer world #945

Open
MightyKnight opened this issue Mar 7, 2024 · 2 comments
Open

XML_ERROR_PARSING when joining a singleplayer world #945

MightyKnight opened this issue Mar 7, 2024 · 2 comments

Comments

@MightyKnight
Copy link

Potential issue?
This error message appears everytime in the game log after joining a singleplayer world (auto record is enabled).
Haven't noticed any issues this is causing yet

16:06:11.750
net.minecraft.class_338
Netty Local Client IO #0
[System] [CHAT] [Replay Mod] Recording started

16:06:12.696
game
M�rz 07, 2024 4:06:12 PM com.replaymod.replaystudio.lib.viaversion.protocols.protocol1_13to1_12_2.blockconnections.ConnectionData init
INFORMATION: Loading block connection mappings ...
M�rz 07, 2024 4:06:12 PM com.replaymod.replaystudio.lib.viaversion.protocols.protocol1_13to1_12_2.storage.BlockConnectionStorage <clinit>
INFORMATION: Using FastUtil Long2ObjectOpenHashMap for block connections
  <log4j:Event logger="net.minecraft.class_3324" timestamp="1709823972696" level="INFO" thread="Server thread">
    <log4j:Message><![CDATA[Playername[local:E:7d4f81c2] logged in with entity id 139 at (5005.207391930176, 63.0, 1018.6288320323216)]]></log4j:Message>
  </log4j:Event>

16:06:12.696
monitor
Process Monitor
XML_ERROR_PARSING
@Johni0702
Copy link
Member

That's benign. It's just the embedded ViaVersion outputting its log messages in a format different from what the official Minecraft Launcher expects.
Will keep this open because it could theoretically be fixed, though I don't immediately know how, so probably not happening any time soon (if ever, given the low impact).

@cassiorenan
Copy link

Please do fix it if/when possible. When working on modpacks we rely on the game output to identify errors and the less noise there is, the better.

I do aggree it's low impact though, so I'm not trying to rush you or anything like that, just putting in my vote on the matter :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants