I thought of certain scenario after dealing with #2
Suppose you have made a script that specified badge: 'local\\\\filename.png' for achievements. Once you've uploaded all achievements to the server, the CLI will ignore those badge strings because otherwise it'd be annoying just like #2 was.
If for whatever reason you need to edit all of the badges from local files again, the CLI just won't let you because it will keep ignoring your badge property.
Some option is needed here to force CLI into accepting your badges when achievement on server already has one. Command-line option seem to be the best idea.
Alternate solution could be prefixing the incoming string to look like !local\\\\filename.png, this likely is more annoying to deal with.
I thought of certain scenario after dealing with #2
Suppose you have made a script that specified
badge: 'local\\\\filename.png'for achievements. Once you've uploaded all achievements to the server, the CLI will ignore those badge strings because otherwise it'd be annoying just like #2 was.If for whatever reason you need to edit all of the badges from local files again, the CLI just won't let you because it will keep ignoring your badge property.
Some option is needed here to force CLI into accepting your badges when achievement on server already has one. Command-line option seem to be the best idea.
Alternate solution could be prefixing the incoming string to look like
!local\\\\filename.png, this likely is more annoying to deal with.