viverse-default-room-multiplayer

Integrate default-room multiplayer networking into local VIVERSE world projects.

2|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/viverseofficial/viverse-sdk-skills --skill viverse-default-room-multiplayer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: viverse-default-room-multiplayer
Source: https://github.com/viverseofficial/viverse-sdk-skills/tree/main/skills/viverse-playcanvas-toolkit/skills/viverse-default-room-multiplayer
Command: npx skills add https://github.com/viverseofficial/viverse-sdk-skills --skill viverse-default-room-multiplayer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the complexity of manually wiring multiplayer networking into local VIVERSE projects by providing a standardized, low-risk integration path for default-room shared presence.

Core Features & Use Cases

  • Shared Presence: Enables basic synchronized player visibility within the default room of a local world.
  • Synchronized Interactions: Facilitates package-level interaction synchronization without requiring complex custom authority logic.
  • Use Case: A developer building a local PlayCanvas-based world can use this skill to quickly enable multiplayer functionality for visitors in the default room while maintaining existing single-player logic.

Quick Start

Use the viverse-default-room-multiplayer skill to add shared presence to my local project folder located at /path/to/my/world.

Frequently Asked Questions about viverse-default-room-multiplayer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add multiplayer shared presence to a local VIVERSE PlayCanvas world?

Shared presence in VIVERSE multiplayer works by synchronizing player visibility and package-level interactions within a default room environment, allowing visitors in a local PlayCanvas world to see each other and interact without complex custom authority logic.

Can I synchronize player interactions in a default room without writing custom authority logic?

To integrate default-room multiplayer, validate your project bootstrap file and confirm the target world's application identity, then apply the networking skill to your local project folder path to automatically wire shared presence into the existing PlayCanvas world.

Does default-room multiplayer networking work with existing single-player logic in my local project?

Default-room multiplayer networking works alongside existing single-player logic in local projects by adding a shared presence layer that synchronizes interactions specifically within the default room, preserving the original standalone world behavior.

What do I need to validate before enabling shared presence in my VIVERSE world?

Before enabling shared presence, you need to validate the project bootstrap file and confirm the target world's application identity to ensure the local PlayCanvas project correctly interfaces with the default-room multiplayer networking layer.

What are the limitations of using default-room multiplayer for VIVERSE shared presence?

Default-room multiplayer is limited to basic synchronized player visibility and package-level interactions within the default room environment, meaning it does not support complex custom authority logic or synchronized interactions across multiple distinct rooms.