[MC-204768] /execute advancement command throws error in log if it fails

When trying to run an execute command which runs an advancement grant or revoke, it throws a error involving brigadier if the command would fail.

execute ... run advancement ... somethingnonexistant
execute ... run advancement ... only somethingnonexistant anycriterion

execute ... run advancement ... somethingnonexistant
execute ... run advancement ... only somethingnonexistant anycriterion

This applies to all execute chains (with the sole-exception of "execute run") and both grant and revoke.

execute as @s run advancement grant @s only somethingnonexistant anycriterion

execute as @s run advancement grant @s only somethingnonexistant anycriterion

Linked issues

relates to 1

MC-265589 Brigadier exception can be repeatedly logged if command has invalid syntax Resolved

Attachments

Comments 4

Former user 2022-06-19T15:59:57Z

confirmed in 1.19

user-f2760 2022-06-19T16:12:35Z

No it isn't; this report is solely about the brigadier error (that only happens with non-valid advancements in the command), that's about something else: it not storing results when the command fails.

Former user 2022-06-19T17:02:39Z

@Dhranios Sorry for my mistake.

this bug only affects auto completion, and doesn't affect execution

user-f2760 2022-06-19T17:43:00Z

Um... again, no. The error gets printed when running the command without a valid advancement.
The reason it isn't a duplicate is because they're not addressing the sane issue; the fix for that report can also be "if error is thrown, return 0", not fixing this.