Skip to content

Conversation

@TelepathicGrunt
Copy link
Contributor

Closes #703

The dev exception will look like this which is a bit more clearer than vanilla's error. And by having the throw in the constructor for TranslatableContent, it makes it easy to find the code that is the source of the problem.
image

Also fixed several spots in NeoForge where we were passing bad arguments as well.

Note: the track command's crash from bad argument passed to Translatable will be fixed in this PR: #915

Closes neoforged#703

Also fixed several spots in NeoForge where we were passing bad arguments as well.

Note: the track command's crash from bad argument passed to Translatable will be fixed in this PR: neoforged#915
@neoforged-pr-publishing
Copy link

  • Publish PR to GitHub Packages

@Matyrobbrt Matyrobbrt added 1.20.6 Targeted at Minecraft 1.20.6 bug A bug or error enhancement New (or improvement to existing) feature or request labels May 4, 2024
@Matyrobbrt Matyrobbrt enabled auto-merge (squash) May 4, 2024 10:12
@Matyrobbrt Matyrobbrt disabled auto-merge May 4, 2024 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

1.20.6 Targeted at Minecraft 1.20.6 bug A bug or error enhancement New (or improvement to existing) feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Component.translatable crashes for non component/number/string objects.

3 participants