Frequently Asked Questions

A historical dark maritime roleplay setting being created for Second Life. The fictional archipelago was known to its original inhabitants as Orunai-Wipó, long before foreign sailors reached its shores. Begin with The Chronicle.

Second Life will host the in-world roleplay. You can read the lore and join the Crownbreak Discord while the region is being prepared.

Crownbreak is in development. The opening date, region location and joining instructions have not been announced. Watch Discord for confirmed updates.

The islands, communities and local events are fictional, against a backdrop informed by the wider Pacific world of 1676—South Sea exploration, Spanish America's western ports, and distant European maritime rivalries. The Aruwai and Varkuró are invented peoples, not representations of any one living Indigenous culture.

The People introduces islanders, sailors, traders, settlers, foreign arrivals and more. Backgrounds are starting points, not compulsory classes or allegiances. Character application details will be shared as the community approaches opening.

Yes. Players are welcome to propose their own factions, ship crews, trading companies, households, religious circles, or other organizations, so long as they fit Crownbreak Cove's seventeenth-century South Seas setting, history, and roleplay atmosphere. Larger or more influential groups, and concepts that affect established lore, politics, or supernatural themes, may require staff approval. The team will publish proposal guidelines ahead of the community opening.

The Varkuró are an ancient Indigenous people of the caverns beneath Ulavé, distinct from the coastal Aruwai. Varkuró characters are not an open background; exceptional concepts would require specific staff approval.

Such beings belong to Crownbreak's folklore, but supernatural roles are exceptionally rare and may not be playable at opening. Any such proposal needs explicit staff approval. Faith, ancestral reverence and healing traditions are not automatically magic.

Crownbreak is intended for adult roleplayers and includes difficult historical subjects. Player boundaries always matter more than fictional justifications. The team is finalizing detailed policies on consent, combat, and character death; the Charter outlines the guiding principles.

TGS is the in-world game system being developed for equipment, combat, survival, trade, and exploration. The team is preparing the player guide, which will explain the systems available at opening.

No particular background requires a faction allegiance. The setting is intended to make space for merchants, travelers, craftspeople, peaceful residents and adventurers alike. The team will share any specific participation guidance before the region opens.

Join our Discord server to follow news and meet the community. Character applications and private support tickets will be added there as the server is organized.

Report concerns privately to Crownbreak staff. Once private Discord tickets are configured, use the player-report ticket route; until then, contact a Discord administrator privately. Do not post accusations or confidential information in public channels.

Include the avatar's Second Life username, approximate time (ideally SLT), region, a factual account, any relevant rule, and available screenshots or chat/IM logs. Preserve originals and enough context for a fair review. You can still report a safety concern without screenshots or logs; staff may ask follow-up questions.

You do not need to confront someone who threatens or harasses you. Violations of Second Life's Terms of Service should also be reported through Linden Lab's official abuse report process.

Keep relevant screenshots, messages or chat logs, dates and times, region names, and the sequence of events. Avoid altering original evidence or spreading private material. Never put yourself at risk to obtain it. Use a confidential staff channel to share what you have.

Yes. Send staff-conduct concerns to a different administrator or the project owner privately. The team is preparing formal appeals and staff-review procedures. In the meantime, raise concerns privately rather than posting public allegations.

Record the error message, what you clicked, approximate time and steps to reproduce, with a screenshot if practical. Use a private system-support ticket when available, or reach staff privately in Discord until then.

See Special Concepts and Contact. The team will publish application procedures and review criteria ahead of opening.