Opaline Roleplay Website
Current public lore, rules, lineages, factions, roll guidance, XP policy, and player instructions.
Official in-world reference
Pair an approved character, synchronize authoritative data, make transparent public rolls, and use the lineage tools that connect Lyra to Second Life.
Begin with the three systems ↓01 · Understanding the three systems
Current public lore, rules, lineages, factions, roll guidance, XP policy, and player instructions.
Accounts, character creation and approval, XP, advancement, grimoire management, shared-scene submissions, and HUD pairing.
Synchronization, public rolls, environmental guidance, applicable session and feeding tracking, and Hollowborn Spellcraft.
02 · Getting the HUD
Obtain the current Lyra HUD through Opaline's official in-world distribution or Staff instructions. Wear it as a HUD attachment. Do not use copied scripts, unofficial objects, or credentials supplied by another player.
The HUD must make secure requests to Lyra, so Second Life may ask you to permit its normal scripted operation.
03–05 · Requirements, code, pairing
You need an approved Lyra character whose saved Second Life UUID matches the avatar wearing the HUD.
Sign in to Lyra ↗ and open the approved character page.
Choose Generate Pairing Code. The eight-character code is single-use and expires after ten minutes. Generating another code cancels the older unused code.
An unpaired HUD opens a text box. Enter the code exactly as shown.
Successful pairing stores the private device connection and immediately synchronizes the character.
07 · Synchronizing data
Sync retrieves the applicable current character identity and lineage, Attributes and Ability ranks, session state, Duskborn feeding state, Second Life time, moon phase and illumination, Hollowborn Schools, prepared spells, casting limits, magical fatigue, and sustained-spell state.
Choose Sync after pairing, after an approved advancement, after saving grimoire changes, or whenever displayed information appears stale.
08 · Making a public roll
09 · Choosing Target Numbers
| Target | Difficulty | Guidance |
|---|---|---|
| 8 | Easy | Simple under pressure; failure is possible but unlikely |
| 10 | Routine | Ordinary challenge requiring some effort |
| 13 | Challenging | Meaningful obstacle with a real chance of failure |
| 16 | Difficult | Demanding action requiring strong capability |
| 19 | Very Difficult | Exceptional challenge beyond ordinary competence |
| 22 | Legendary | Extraordinary feat rarely accomplished |
| 25 | Nearly Impossible | Extreme action possible only under exceptional circumstances |
If a Storyteller runs the scene, the Storyteller selects the Target Number. If another character directly opposes the action, compare the appropriate totals rather than assigning a separate Target Number; Resistance Checks follow their specific rule. During ordinary unsupervised roleplay, the rolling player chooses honestly from this table.
10 · Advantages and Hindrances
Minor but meaningful circumstances: useful positioning or preparation, a useful ordinary tool, familiar natural terrain, or distinct credible assistance.
Significant circumstances: native aquatic conditions supporting a Tideborn physical action, exceptional physical force in Ridgeborn War Form, or directly applicable lunar influence.
A carefully prepared ambush; complete positional control; uniquely ideal equipment or surroundings; extensive preparation for this action; an opponent at an extreme situational disadvantage.
Light rain; mild distraction; awkward positioning; unstable footing; a rushed attempt; partially obstructed view.
Heavy rain or strong wind; significantly limited visibility without appropriate senses; significant underwater obstacles without appropriate support; partial restraint; significant exhaustion; damaged or inadequate equipment; applicable New Moon Ridgeborn influence.
Near-total darkness without an applicable Capability; dangerous weather or exposure; a severely dangerous underwater action without appropriate support; major restraint; debilitating injury or condition; overwhelming pressure.
11 · Duskborn sessions and feeding
0–1 completed sessions since feeding.
2–3 completed sessions since feeding.
4 or more completed sessions since feeding.
A legitimate scene does not require a scripted object. Tell an Admin when it concludes. After any needed verification, the Admin updates Lyra's authoritative state; choose Sync to receive it.
Ending a session without feeding advances the counter. Feeding resets it. No general player-feeding HUD button exists.
12 · Ridgeborn lunar guidance
Sync retrieves the server-calculated phase and illumination and privately displays guidance. Full Moon may supply a +2 Advantage to directly applicable shifting, supernatural recovery, heightened senses, or lunar Abilities, and a −2 Hindrance to appropriate restraint or Rage-control checks. New Moon may supply +2 to appropriate focus, discipline, or emotional control and −2 to difficult shifting or supernatural recovery. Other phases have no universal modifier.
The HUD does not add lunar modifiers automatically. Declare one relevant lunar Advantage or Hindrance in the normal roll flow.
13 · Hollowborn grimoire and Spellcraft
5 prepared spells.
8 prepared spells.
12 prepared spells.
Select unlocked, non-ritual, non-story-level spells and save. Sync the HUD afterward.
Beginning a session locks the grimoire until End Session.
Select a prepared spell, then declare Target Number, one Advantage, and one Hindrance.
Lyra uses d20 + Wisdom + Arcane Focus + one Advantage − one Hindrance. A natural 1 critically fails and a natural 20 critically succeeds.
| Spell Tier | Casts per preparation period | Ordinary HUD status |
|---|---|---|
| I | Unlimited reasonable use | Available when prepared |
| II | 5 | Available when requirements are met |
| III | 3 | Available when requirements are met |
| IV | 2 | Available when requirements are met |
| V | 1 | Story-level spells require Storyteller resolution |
14 · Sustained spells
Only one sustained spell may be active. A successful sustained cast normally begins with up to two combat turns. Advance Turn reduces the remaining duration; End Sustain ends the active effect early. Sync refreshes the displayed sustain state.
15 · Pair Again, Forget, and timeouts
Enter a new code to connect the HUD to the selected approved character.
Deletes the locally stored Lyra connection from that HUD object.
If a dialog expires, touch the HUD and restart the action.
Transferring the HUD clears stored connection data automatically.
16 · Troubleshooting
Touch the HUD. If no connection is stored, it opens the pairing-code input. Generate a fresh code on the approved character's Lyra page.
Generate a new code. Codes are single-use and expire after ten minutes.
Choose Pair Again and enter a new code generated from the correct approved character page.
Choose Sync. Confirm that Lyra shows the expected approved character record first.
Confirm the advancement is approved in Lyra, then choose Sync. Pending requests are not available to the HUD.
End any active session, save the prepared grimoire in Lyra, and choose Sync.
Confirm a Hollowborn character is paired and synchronized. Spellcraft appears only for Hollowborn.
End the active roleplay session through the HUD before changing prepared spells in Lyra.
Choose Begin Session before Duskborn tracked play or Hollowborn casting.
For an approved scripted prop, confirm Lyra recorded the feeding and choose Sync. For roleplay-only feeding, contact an Admin for verification and a Lyra update, then Sync.
HUD input dialogs close after 60 seconds. Touch the HUD and begin the selection again.
Ownership changes clear the stored connection. The new owner must pair an eligible approved character.
17 · Security and privacy
Never share active pairing codes, HUD tokens, private account information, environment variables, or application secrets. Staff may ask what error you saw; they do not need your password or private device token.
Use only the official Lyra domain and official Opaline-distributed HUD objects.