Skip to main content

Frostbrand

Frostbrand is an opt-in nearby pairing system. It shows other opted-in Snowcloak users in range and lets either person send a pair request without exchanging UIDs first.

Enabling Frostbrand​

Open the main Snowcloak window, select Frostbrand, and enable the feature after reading the notice.

When enabled, Frostbrand adds its DTR entry beside your other server-info icons. It shows nearby available users and changes state when you have pending requests.

Enabling Frostbrand is also a prerequisite for the separate Roleplay tools.

Nearby users​

Select the Frostbrand DTR entry to open the nearby window.

You can use either a compact table or profile cards. Profile cards may show:

  • character and home-world information;
  • public profile summary and portrait;
  • visible tags and rotating hooks;
  • current RP availability and themes;
  • a current hook.

Use the search field to filter by name, profile text, race, tribe, class, world, or other displayed details. A tag filter and Only with profiles option are also available.

Right-click a result to:

  • Examine;
  • open their Adventurer Plate;
  • view their public Snowcloak profile;
  • send a pair request;
  • report or block them.

Name highlighting​

Nearby opted-in users can be highlighted in the game world. Change the highlight colour under Frostbrand settings → Highlighting.

The DTR count, hover list, and nearby window use your current client-side filters.

Auto-reject filters​

Frostbrand can automatically reject requests using:

  • minimum level;
  • friends-only mode;
  • vanilla race, clan, and binary game-gender combinations;
  • home world.

Set the minimum level to 0 to disable level-based rejection.

Race, clan, and gender checks use the sender's visible vanilla character state. Snowcloak does not automatically load Adventurer Plates to infer custom gender markers.

If the sender is out of draw range when the request arrives, Snowcloak cannot immediately inspect those character details. The request remains pending and is checked when that character next becomes visible.

Filters are local

Filters do not hide you from other Frostbrand users. They decide which incoming requests your client accepts or rejects.

Pair requests​

Pending requests appear in the Frostbrand panel and change the DTR entry's colour.

You can:

  • accept the request;
  • reject it;
  • block the requester.

Acceptance creates your side of the pairing. Appearance syncing and direct chat become fully available once the relationship is mutual.

Requests started from the Roleplay directory are labelled with that source and may include a snapshot of the sender's current hook.

Profiles and Frostbrand​

Publishing a character profile does not enable Frostbrand, and enabling Frostbrand does not publish a profile.

Frostbrand always uses the public profile projection. Pair-only and owner-only fields remain hidden. Adult-rated fields and kink tags also retain their Adult-content and matching-tag rules.