Applying skins and "player as entity"

When starting playback or adding element to a scene you can specify player skin different from one belonging to player with given name. You can do this with optional arguments after player name:

• /mocap playback start [recording name] [player name] [skin source] [skin argument]
• /mocap scenes add_to [scene name] [recording name] [player name] [wait on start] [skin source] [skin argument]

"Wait on start" argument will be described in "Synchronizing recordings" chapter. If you don't need it, set it to 0.

There are 3 skin sources:

• skin_from_player
• skin_from_mineskin
• skin_from_file

Instead of one skin source you can also use player_as_entity which will replace player with specified entity.

Skin from player

You can load skin of a player different from one specifier in player name.

Skin argument is name of a player you want to load skin from.

Skin from mineskin.org

mineskin.org is site that allows you to view and upload skins, but it isn't just skin archive. Vanilla Minecraft client can only load skins from Mojang's server (server can't just upload skin file to client). MineSkin works by temporarily setting uploaded skins on Minecraft accounts and therefore uploading them to Mojang's servers.

Skin argument is URL of mineskin skin, e.g. https://minesk.in/b1e406908b3b4f91b64ce7fce8156643

Skin URL needs to start with minesk.in/ or mineskin.org/skins/. http:// or https:// prefix is not required and is omitted when present.

Skin from file

As mentioned in MineSkin section, vanilla client cannot receive custom skins from game server. Because of that Motion Capture uses custom packet to send its custom skins to client. It means that in order for skin from files to work, client have to install Motion Capture mod. This might be an issue when playing multiplayer server and not everyone has Motion Capture installed. Skin from files have also more compatibility issues with other mods, especially one for client-side recording. Because of these issues, you may sometimes need to set skins from MineSkin instead. When not necessary it's better to use skins from file instead, as one from MineSkin rely on both mineskin.org and Mojang servers in order to work. Which is not guaranteed in perspective of a few or more years.

To use skins from file, save your skin to PNG file, make sure it has .png file extension and copy it to .minecraft/saves/(your world folder)/mocap_files/skins. Then set skin argument to name of the file, but without .png extension.

Skins from skins directory are loaded with wide hands. If you want to load skin with slim hands, move it to skins/slim subdirectory and add slim/ prefix when specifying its name in an argument.

Note that skins from file are cached (on both server and client side), so if you want to replace skin with different one without changing its name, use /mocap misc clear_cache command to make sure change will be visible. Cache persists until server restarts or until rejoining world/server in case of a client.

Player as entity

You can replace player (main playback entity) with different entity using player_as_entity modifier.

• /mocap playback start [recording name] [player name] player_as_entity [entity ID] [entity NBT - optional]
• /mocap scenes add_to [scene name] [recording name] [player name] [wait on start] player_as_entity [entity ID] [entity NBT - optional]