QCherry: Document skin color and tattoos available from 0.1.3; identity/armor improvements

2026-09-09T02:32:20Z

Document skin color and tattoos available from 0.1.3; identity/armor improvements

New page

= setPlayerSkinColor =
<div style="background:#fff5f5; border:1px solid #d13b3b; border-left:5px solid #d13b3b; color:#111111; padding:0.85rem 1rem; margin:0.75rem 0 1rem;">
<div style="color:#111111; font-weight:bold; letter-spacing:0.04em;">AVAILABLE FROM UPDATE 0.1.3</div>
<div style="color:#111111; margin-top:0.25rem;">This function is available in G1R:MP 0.1.3 and later. The contract below includes the compatibility guarantees introduced in that update.</div>
</div>

Sets an independent server-owned sRGB skin-color override for a player.

== Syntax ==
<syntaxhighlight lang="lua">
bool setPlayerSkinColor(int playerId, int r, int g, int b)
</syntaxhighlight>

== Parameters ==
{| class="wikitable"
! Name !! Type !! Required !! Description
|-
| <code>playerId</code> || <code>int</code> || yes || The connected player identifier.
|-
| <code>r</code> || <code>int</code> || yes || The red sRGB channel: a finite integer from 0 through 255 inclusive.
|-
| <code>g</code> || <code>int</code> || yes || The green sRGB channel: a finite integer from 0 through 255 inclusive.
|-
| <code>b</code> || <code>int</code> || yes || The blue sRGB channel: a finite integer from 0 through 255 inclusive.
|}

== Returns ==
Returns <code>true</code> when the server accepts the override; otherwise returns <code>false</code>, including an unavailable player or invalid channel value.

== Examples ==
Apply a skin tint after authorizing the request:
<syntaxhighlight lang="lua" line>
-- The resource must authorize this change first.
if not setPlayerSkinColor(playerId, 180, 140, 110) then
outputDebugString("Skin color was rejected.")
end
</syntaxhighlight>

== Notes ==
* Available only in server-side resource scripts.
* Alias: <code>SetPlayerSkinColor</code>.
* Cosmetic state only: this does not change identity, equipped armor, inventory, HP or other progression statistics.
* Fractions, NaN, infinity and values outside 0..255 are rejected, not clamped. RGB is sRGB, converted to linear material RGB by the native client; there is no alpha argument.
* This preserves the tattoo override. Use <code>resetPlayerSkinColor</code> to restore native material defaults; setting white is still an enabled override, not a reset.
* Only supported skin surfaces are tinted. Armor, clothing, eyes and hair are not skin targets. Final appearance depends on the underlying skin texture, supported material, lighting and visible body regions.
* The server owns the reliable state and replays it on late join and relevance entry; the native client reapplies it after supported visual rebuilds. Acceptance is not confirmation that a client has already rendered the change.
* Resources must implement their own authorization before allowing a player request to call a setter. There is no client mutation packet or arbitrary texture upload API.
* See [[Player customization]] and [[Player tattoo catalog]].

[[Category:Lua Functions]]
[[Category:Server Functions]]
[[Category:Player Functions]]
[[Category:Appearance Functions]]

SetPlayerSkinColor - Revision history

QCherry: Document skin color and tattoos available from 0.1.3; identity/armor improvements