I see.
It just so happens that they accept NBT in some cases; the support is originally limited to strings.
Thank you.
I met the same thing.
This command does not return 1, it just skips execute store process.
scoreboard players set @p test 901247831
execute store success score @p test run data modify storage minecraft:test a set string storage minecraft:test a 100 // throws unexpected error
scoreboard players get @p test // returns 901247831
This commands skips execute store process due to unhandled exception; This command does not return 1, it just does not change the scoreboard.
By the fact that the command does not change the scoreboard, you can detect command failure.
still occurs at 23w14a
Sorry for not following the guidelines.
MC-260942
My issue is exactly the same as this Issue.
I made a detailed analysis of this issue, as I thought this was a bug and not a specification.
The comment I received made it clear that in json interpret, it is not intended that non-string formatted NBTs are used in the first place, so it is no wonder that the strange behavior occurs.
Thank you for your response and resolving the issue.