What You Can Build

VibeLands is a multiplayer world-creation platform, not only a fixed game. Plugins turn reusable source packages into new world content, interactions and shared activities without importing the private host repository.

Available now

Goal	Public building blocks	Typical tier
Atmosphere, flora, ambient life and visual effects	WorldLayer, terrain/time/weather/quality hooks, deterministic RNG, assets and host audio	A
Buildings, props and content packs	manifest editorItems, object renderers, property schemas and colliders	A or B
Natural-language world building	every enabled editorItem label/id automatically joins the editor and AI spawn vocabulary	A or B
Shared quests, scoreboards and minigames	server messages, replicated KV state/entities, storage, timers and rewards	B
Resources and crafting	harvestable editor items, inventory items, recipes and host-owned inventory mutations	B
Shops and player economy content	item buy/sell metadata, General Store integration and validated rewards	B
Physical toys and destructible interactions	curated client physics plus host-owned dynamic plugin entities	B
HUD prompts and feedback	HUD surfaces, key actions, notification center and server messages	A or B

Tier A is the default because decorative content can be deterministic and network-free. Upgrade to Tier B only when all players must observe one authoritative outcome.

How packages become world vocabulary

One plugin can contribute several connected layers:

1. editorItems make objects placeable and configurable.
2. The same items become available to AI world-building commands while the plugin is enabled.
3. items and recipes connect content to inventory, shops and crafting.
4. Tier B server hooks add validated interactions, persistence and rewards.
5. Publishing makes the complete vocabulary reusable in other worlds when the creation is ready to share.

This is the preferred route for modular content growth. Avoid hardcoding a new renderer or server branch when a stable manifest or SDK extension can express the feature.

First-party examples

• ambient-birds, ambient-insects, grass, clouds, fog, moon and stars prove deterministic environmental Tier A plugins.
• forest, light-kit, market-stalls, parkour-kit, resources and wayfinding-signs prove reusable editor content packs.
• farming, chess, fast-travel-points, physics-playground, treasure-hunt and world-feedback prove server-authoritative Tier B gameplay.

Use the Marketplace source/remix flow when an open-source example is available. The public package contract, not private first-party registration code, is the external authoring boundary.

Planned extension order

The next public surfaces should be opened only after one first-party system dogfoods each contract:

1. common activity/minigame discovery and lifecycle;
2. activity and community surfaces in the in-game phone;
3. reusable service/economy providers;
4. reusable world-event and mission integration.

Deep vehicle, weapon and terrain authority remains a future Tier C concern. Those systems stay host-owned until their networking, performance and security contracts are stable enough for third-party code.