Orgy Events
Orgy Night events are special planning events where attendees can engage in group activities. These events require careful planning and staffing to ensure safety and consent.
Event Overviewβ
| Event Type | Security (Min-Max) | Volunteers (Min-Max) | Attendees Expected |
|---|---|---|---|
| Orgy Night | 2-4 | 1-3 | 25-40 |
Night of making a hot sticky mess on some poor world creator's world.
Designate a SFW/Aftercare area for attendees to cool off.
Special Event Planning Thread Requirementβ
Orgy events are special planning events and require a planning thread in πspecial-event-planning to be opened at least 24 hours in advance of the event start time.
- Minimum: 24 hours in advance (required)
- Preferred: 2-3 days in advance
- Best practice: As soon as the schedule comes out
Important: If a planning thread is opened less than 24 hours before the event, the event will be canceled and changed to a regular event.
Additional Guidelinesβ
πAftercare
Aftercare must be available and clearly communicated to attendees at the start of the event.
π₯Staffing Requirements
Minimum staffing: 4 total
- Option A: 1 Host and 3 Security
- Option B: 2 Hosts and 2 Security
πWorld Selection
- Choose a world large enough to accommodate the event
- 3+ rooms recommended
- Recommended: Pick worlds with built-in consent labels if available
π‘οΈConsent & Safety
- Consent still applies in Blue zones; announce zone expectations at the start
- Encourage the Eden Consent badge; explain it in announcements and enforce consent
- Maintain coverage: at least 1 @Event Host/@Event Security present in the Open Consent Zone at all times
Training Restrictionsβ
π«No Training During Event
No training during the event.
Exception: Only if additional Security can be gathered to run training; absolutely no Host training during orgy events.
Orgy events require significant staffing to ensure safety and consent enforcement. Make sure you have adequate coverage before scheduling.
AU Timezone Exceptionβ
ONLY if in an AU timezone, a host is authorized to host an orgy event even if security is missing, but must follow a strict security-to-attendee ratio.
Strict Security Ratio Ruleβ
1 security per 10 attendees maximum
Examples:
- 1 security available = 10 attendees maximum
- 2 security available = 20 attendees maximum
- 3 security available = 30 attendees maximum
Being a @Senior Event Team member does not count towards the security count! Only actual @Event Security members count for this ratio.
This exception only applies to AU timezone hosts due to the limited availability of security staff during those time slots.
Relatedβ
- Event Types - Overview of all event types
- How to Host an Event - General hosting guidelines
- Incident Management - Handling incidents during events