user-e1104

Regrettably, I am experiencing what may be a similar issue pertaining to loading RTX packs.

For me, the pack I am using is the boilerplate pack that is provided by NVIDIA for developers creating RTX packs. This pack has been attached to this issue as

for easy download and inspection.

I am also receiving similar readouts from Event Viewer:

Faulting application name: Minecraft.Windows.exe, version: 1.19.31.1, time stamp: 0x6334e15a
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process ID: 0x904
Faulting application start time: 0x01d8dba404292123
Faulting application path: C:\Program Files\WindowsApps\Microsoft.MinecraftUWP_1.19.3101.0_x64__8wekyb3d8bbwe\Minecraft.Windows.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report ID: 5f50c26c-77c7-4694-a399-63cfa88b21e7
Faulting package full name: Microsoft.MinecraftUWP_1.19.3101.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

I do not know where I can find any further details to the crashes I am experiencing. Please let me know if/how this error can be explored in further detail.

Affects latest release (1.19.2) as of this time, and presumably all releases up until this point also.

Additional findings

Notice how to set a scoreholder with a non-alphanumeric character, quotation marks are required around the scoreholder's name:

scoreboard players set "#example" foo 1

Therefore, logically, to retrieve this score value, quotation marks will need to surround the scoreholder's name in the JSON text.

Our current text is:

{"rawtext": [{"score": {"name": "#example", "objective": "foo"}}]}

This means that when the JSON test looks up the score, it is looking up:

• #example for the scoreholder

• foo for the objective
  Notice something? No quotation marks!

The next logical step to find a solution would be to add an inner set of quotation marks around the scoreholder's name:

{"rawtext": [{"score": {"name": "\"#example\"", "objective": "foo"}}]}

Notice the use of backslashes to insure the inner quotation marks are not interpreted as part of the JSON structure.

When this JSON text is printed, we no longer have an error message.
❌ However, there is instead no output. No output is printed, even though a score is set.

It can be confirmed that putting inner quotation marks is correct because the same can be done for any other username, e.g. your own:

{"rawtext": [{"score": {"name": "\"ExpertCoder14\"", "objective": "foo"}}]}

✔ The score output is printed correctly.

Conclusion

It appears that the JSON text resolution system is currently not prepared to handle usernames with non-alphanumeric characters, even when queried in the correct manner. However, such usernames are valid scoreholders within other aspects of the scoreboard system. Therefore, it is most likely unintended that the JSON text does not support these usernames, and this is a bug.

In addition, usernames like these are chosen frequently to be scoreholders because they contain characters that will never appear in a real Minecraft username. If a user with the same name as a fake scoreholder joins the game, this could have unintended effects if a command system detects them as a player. It would be appreciated by many if this could be fixed, which would increase the efficiency of development by allowing fake scoreholders to be printed directly.

@Chris_KR To clarify, this is on the subject of the new syntax for the /execute command. In Bedrock version 1.19.10 and newer, the syntax of /execute has been changed to reflect that of Java Edition's.