This guide is intended for those who need a more in depth guide into the avatar’s inner workings or creating assets intended for release or purchase.

If you’re looking for a general installation and user guide for the Winterbold, check here:

ItsGuusy Winterbold User Guide

This changelog tracks changes pushed through numbered updates:

ItsGuusy Winterbold Update Changelog

If you create an asset and release it, be sure to show it off in the discord!

ItsGuusy Community Discord: https://discord.com/invite/XDubRpFbyB

Design Patterns and Features

VRCFury

• The Winterbold is built with VRCFury in mind which should make your life much easier! If you would like to learn more about making VRCFury compatible assets, check here: https://vrcfury.com/
  • VRCFury is essentially a tool that automates the merging of animators, parameters, creating of menus, and more. It makes Duplication of the same asset on an avatar much easier, and it allows for great modularity (to add or remove an asset, you simply drag on or delete the prefab)
  • Assets can easily be adapted to VRCFury via the “Full Controller” feature: https://vrcfury.com/components/full-controller
    • This feature is typically what’s used by asset creators and allows you to more freely animate your toggles and effects
  • Clothing especially benefits from VRCFury, as you can set it up to automatically map your clothing armature to the avatar (through multiple different methods) via the “Armature Link” feature: https://vrcfury.com/components/armature-link and can easily link to avatar blendshapes with the “Blendshape Link” feature: https://vrcfury.com/components/other
  • When customizing with VRCFury packages, it is very important to note the placement of them in your avatar’s hierarchy
  • VRCFury will build your avatar from the root of the prefab downward, meaning placement matters for proper syncing across platforms
  • When building for Quest and PC, place your VRCFury objects in the same hierarchical order as each other.
    • It’s possible one platform may have more packages than another, in which case place the additional packages that are unique to one platform after the ones that appear in both

Modular Toggles

This system is designed for official updates and shouldn’t be used for 3rd party assets. Specifically, it is designed to streamline the addition of new toggles to avoid overwriting changes the user has manually made to their avatar. Please don’t place 3rd party assets in the Modular Toggles object

• Modular toggles is a system utilizing VRCFury that allows the user to easily add or remove additional features that they may or may not want. This makes freeing up space for additional clothing items or assets that utilize parameter memory much easier.
• As with VRCFury packages, it is very important to note the placement of these items in the avatar’s hierarchy and have them appear in the same order for PC and Quest versions. This ensures proper syncing of toggles across platforms.
• Any new toggles added to the avatar will appear here, and can be added manually from the “Modular Toggles” folder

VRChat

• The Winterbold utilizes 4 custom contact receivers and 1 custom contact sender

  • Left Eye Receiver
  • Right Eye Receiver
  • Nose Receiver
  • Head Receiver
  • Nose Sender

• The Winterbold uses 56 total memory (70 with base clothing)

• The PC version of the Winterbold uses 11 Physbones (14 with base clothing)

  • Hair
  • *Left Arm Fluff (ArmFluff)
  • *Right Arm Fluff (ArmFluff)
  • *BackFur
  • Tail
  • Ears
  • Booty
  • Left Toes (Toes)
  • Right Toes (Toes)
  • Tongue
  • Breasts

  ** Means they could be removed in the future if the overall physbone count causes too heavy of performance constraints for creators to work in (the marked ones give a very subtle effect)*