[MC-129905] String command suggestions that end with a number don't get ordered correctly

The bug

When you type /bossbar set foo:bar style, the command suggestions show the different styles ordered incorrectly. The style "notched_6" is after "notched_10", while 10 is a higher number.

This affects all string arguments where the string ends with a number, but not numeric arguments such as age block states.

Affected areas

Disclaimer: this absolutely affects more fields, but these can be reproduced without mods

Affected field	Affected command(s)	Affected selector argument(s)
Advancement IDs	`advancement grant` `advancement revoke`	-(MC-130452)
Advancement criteria	`advancement grant ... only` `advancement revoke ... only`	-(MC-130452)
Biome tags	`execute if biome` `execute unless biome` `fillbiome ... replace`	-
Block tags	`clone ... filtered` `execute if block` `execute unless block` `fill ... replace`	-
Boss bar IDs	`bossbar get` `bossbar remove` `bossbar set` `execute store result bossbar` `execute store success bossbar`	-
Boss bar style	`bossbar set ... style`	-
Command storage IDs	`data ... storage` `execute if data storage` `execute unless data storage`	-
Dimension IDs	`execute if in` `execute in` `execute unless in`	-
Dimension tags	`execute if in` `execute unless in`	-
Entity type tags	-	`type`
Function IDs	`execute if function` `execute unless function` `function` `schedule clear` `schedule function`	-
Function tags	`execute if function` `execute unless function` `function` `schedule clear` `schedule function`	-
Item tags	`clear`	-
Loot table IDs	`loot ... loot`	-
Predicate IDs	`execute if predicate` `execute unless predicate`	-(MC-130452)
Scoreboard objective IDs	`execute if score` `execute unless score` `execute store result score` `execute store success score` `scoreboard objectives remove` `scoreboard players add` `scoreboard players enable` `scoreboard players get` `scoreboard players operation` `scoreboard players remove` `scoreboard players reset` `scoreboard players set` `trigger add` `trigger set`	-(MC-130452)
Sound events	`playsound` `stopsound`	-
Tags	`tag ... remove`	-(MC-130452)
Team IDs	`team empty` `team join` `team list` `team modify` `team remove`	-(MC-130452)

Steps to reproduce

Boss bar style:

Type /bossbar set foo:bar style
Observe that notched_10 is suggested before notched_6

Others listed:

Create an instance of the affected field named test_2
Create another instance with the named test_10
Type an affected command for that instance
Observe that test_10 is suggested before test_2

Linked issues

relates to 1

MC-125115 Command suggestions don't order numbers from least to greatest Resolved

Attachments

Comments 8

Avoma 2021-01-30T16:31:09Z

Can confirm in 21w03a.

Avoma 2021-02-09T09:50:12Z

Can confirm in 21w05b.

Avoma 2021-02-17T11:18:01Z

Can confirm in 21w06a.

Avoma 2021-03-01T17:25:15Z

Can confirm in 1.16.5 and 21w08b.

Avoma 2022-04-24T15:06:45Z

Can confirm in 1.18.2 and 22w16b.

migrated 2022-04-24T16:38:14Z

This affects all string arguments that end with numbers, such as function names; it orders "end" after numbers, rather than before.

Requesting this report to get more generalized.

migrated 2023-07-31T11:26:55Z

Re-requesting generalization, as, again, boss bar styles are not the only thing affected.

Off the top of my head, also affects:

Boss bar IDs (/bossbar, /execute store success/result bossbar)
Function IDs (/function, /schedule)
Loot table IDs (/loot ... loot)
Command storage IDs (/data ... storage, /execute if/unless data storage)
Block tags (/execute if/unless block, /clone ... filtered, /fill ... replace)
Item tags (/clear)
Biome tags (/execute if/unless biome, /fillbiome ... replace)
Dimension tags (/execute if/unless in)

[Mod] turbo 2023-10-31T16:56:22Z

Changing the reporter to @unknown to keep the issue updated, as the reporter has been inactive on the issue for more than 3 years and hasn't responded to or addressed the requests from April and July.