This is actually an unordered list of part IDs associated with the player avatar, the precise column (derived from the corresponding binary message fragment offset) in which an item ID is stored does not have any particular significance.
In GitLab by @tau on Nov 11, 2019, 22:28
This is actually an unordered list of part IDs associated with the player avatar, the precise column (derived from the corresponding binary message fragment offset) in which an item ID is stored does not have any particular significance.
Update:
Order and field really doesn't matter. I accidentally replaced my hair with the ID of a newer shirt, and it just gave me default hair, but BOTH pieces of clothing at the same time. Apparently it will just render whatever IDs it gets, and then fill the missing slot with the default for that slot.
In GitLab by @BemaniWitch on Nov 13, 2019, 22:34
Update:
Order and field really doesn't matter. I accidentally replaced my hair with the ID of a newer shirt, and it just gave me default hair, but BOTH pieces of clothing at the same time. Apparently it will just render whatever IDs it gets, and then fill the missing slot with the default for that slot.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In GitLab by @tau on Nov 11, 2019, 22:28
This is actually an unordered list of part IDs associated with the player avatar, the precise column (derived from the corresponding binary message fragment offset) in which an item ID is stored does not have any particular significance.
In GitLab by @BemaniWitch on Nov 13, 2019, 22:34
Update:
Order and field really doesn't matter. I accidentally replaced my hair with the ID of a newer shirt, and it just gave me default hair, but BOTH pieces of clothing at the same time. Apparently it will just render whatever IDs it gets, and then fill the missing slot with the default for that slot.