Thanks to Overripe Papaya's comment , I was able to register a lot of skins. However, as already mentioned, the preview is not shown.
Then I made a backup of launcher-skins.json and tested it. Then I deleted the custom ones. I put the backups back together, but the previews were still not working. It is unlikely that a simple copy and paste will change the data inside. As for the preview, suspect there's another flag set, but I have no idea.
Edit: I was curious, so I uninstalled and then reinstalled and removed Roaming>.minecraft. Then I selected the various skins in the library, but the current skin was not updated.
Edit: Overripe Papaya's comment that "other fields can be empty", However but "created" should be entered. "created" affects the order of the skin library. In contrast, the numbers of the nodes (skin_) have no effect on the order. Updating the skin in the launcher with the node's number exceeding two digits breaks the alignment.
skin_1 skin_10 skin_100 skin_11 skin_110
This is not a bug, but a data management specification, so it's probably inevitable.
It was redundant, however, I'd like to think that this is all I've ever cared about.
Thanks to Overripe Papaya's comment , I was able to register a lot of skins. However, as already mentioned, the preview is not shown.
Then I made a backup of launcher-skins.json and tested it. Then I deleted the custom ones. I put the backups back together, but the previews were still not working.
It is unlikely that a simple copy and paste will change the data inside. As for the preview, suspect there's another flag set, but I have no idea.
Edit: I was curious, so I uninstalled and then reinstalled and removed Roaming>.minecraft. Then I selected the various skins in the library, but the current skin was not updated.
Edit: Overripe Papaya's comment that "other fields can be empty", However but "created" should be entered. "created" affects the order of the skin library.
In contrast, the numbers of the nodes (skin_) have no effect on the order. Updating the skin in the launcher with the node's number exceeding two digits breaks the alignment.
This is not a bug, but a data management specification, so it's probably inevitable.
It was redundant, however, I'd like to think that this is all I've ever cared about.