mojira.dev
MC-129245

Crash when entering worldsave due to "illegal character"

The bug

I currently enter 1.11 and 1.12 release worlds to see if they get successfully updated to 1.13, but I just crashed upon entering one of my worlds which I backed up before.

Crash report

18w19a\: [^crash-2018-05-08_17.31.47-client.txt]

Description: mouseClicked event handler

java.lang.IllegalArgumentException: Illegal character in path at index 105: file:/C:/Users/Meri/AppData/Roaming/.mc-snaps/backups/2018-05-08_17-31-47_BONUS%20MushroomBlocks%20Map%20[LD].zip
	at com.sun.nio.zipfs.ZipFileSystemProvider.uriToPath(ZipFileSystemProvider.java:87)
	at com.sun.nio.zipfs.ZipFileSystemProvider.newFileSystem(ZipFileSystemProvider.java:107)
	at java.nio.file.FileSystems.newFileSystem(Unknown Source)
	at java.nio.file.FileSystems.newFileSystem(Unknown Source)
	at cci.h(SourceFile:74)
	at cmj.a(SourceFile:130)
	at cml.b(SourceFile:189)
	at cit$1.a(SourceFile:45)
	at cgw.mouseClicked(SourceFile:103)
	at chs.mouseClicked(SourceFile:45)
	at cfx.b(SourceFile:67)
	at cjn.a(SourceFile:429)
	at cfx.a(SourceFile:67)
	at org.lwjgl.glfw.GLFWMouseButtonCallbackI.callback(GLFWMouseButtonCallbackI.java:23)
	at org.lwjgl.system.JNI.invokeV(Native Method)
	at org.lwjgl.glfw.GLFW.glfwWaitEventsTimeout(GLFW.java:2599)
	at cgf.a(SourceFile:296)
	at cfv.c(SourceFile:845)
	at cfv.a(SourceFile:381)
	at net.minecraft.client.main.Main.main(SourceFile:143)
Caused by: java.net.URISyntaxException: Illegal character in path at index 105: file:/C:/Users/Meri/AppData/Roaming/.mc-snaps/backups/2018-05-08_17-31-47_BONUS%20MushroomBlocks%20Map%20[LD].zip
	at java.net.URI$Parser.fail(Unknown Source)
	at java.net.URI$Parser.checkChars(Unknown Source)
	at java.net.URI$Parser.parseHierarchical(Unknown Source)
	at java.net.URI$Parser.parse(Unknown Source)
	at java.net.URI.<init>(Unknown Source)
	at com.sun.nio.zipfs.ZipFileSystemProvider.uriToPath(ZipFileSystemProvider.java:85)
	... 19 more

Linked issues

Attachments

Comments 8

Yeah I know, e.g. it deletes all builds of worlds you have entered in a 1.13 snapshot before, but Professor Mobius tweeted just before that it'll be fixed in the b-snapshot 🙂

The issue here is a different one, it throws "illegal character" which it shouldn't, the characters should be all valid. But thanks for helping!

Seems to be caused by the brackets in your world name. Minecraft should turn these into dashes like it does with other special characters. You could try removing those characters from the world's folder under .minecraft/saves.

Thank you @unknown I wanted to fiddle with the names later, I just wanted to know/make sure what really is considered an "illegal character" and what isn't, as this may then happen to anyone who used the same characters, which didn't cause any issue before.

I'll test that later, thank you again!

Doesn't throw any error in 18w19a when those brackets are removed 🙂
Still, it accepted it in the old 1.13 snapshot?

Could it maybe be changed that whenever someone would enter those brackets as part of the world name, those brackets would not be chosable/result in an error-popup text or so?

Can confirm for 1.13pre2.

Can confirm for 1.13pre3. See

[media]

.

Maybe I am misunderstanding the report, but I am not able to reproduce this.

What I did was:

  1. Create a superflat world in 1.12.2 with the name Test[]/&#x5c;

  2. Start a snapshot / pre-release (1.13.-pre4) and try to open the world

  3. On the backup dialog select "Backup and load"

Are these steps correct?

Yes, you did everything correctly, that's how I tested it previously too.
Appears to be fixed in 1.13pre4 🙂

Meri Diana

(Unassigned)

Community Consensus

Minecraft 18w19a, Minecraft 1.13-pre3

Minecraft 1.13-pre4

Retrieved