Use Unique IDs: Always track relationships using Player.UserId to ensure data persists even if a player changes their username.
Players need a way to express interest or change their status. A ProximityPrompt or a GUI-based "Interaction Radial" is the standard method for triggering these events.
Opt-Out Features: Always script a "Break Up" or "Block" button that works instantly without requiring the other player's consent. This prevents harassment within the relationship system. Advanced Features: Cinematic Storytelling
The Request System: When Player A selects "Ask to Date" on Player B, fire a RemoteEvent to the server.
The Validation: The server checks if both players are eligible (e.g., not already in a relationship, within distance).
The Prompt: The server fires a ClientEvent to Player B, displaying a "Yes/No" UI.
Age-Appropriate Design: Focus on "Wholesome" romance—friendship, companionship, and weddings—rather than anything suggestive.