Skip to main content

Supported Platforms

ZyveraWeb uses a platform abstraction architecture with a single core and platform-specific adapters. The same feature set is available on all supported platforms.

Platform Matrix

Platform Minimum Version Status
Spigot 1.16 Tested
Paper 1.16 Tested
Folia Any (via FoliaLib) Tested
Velocity 3.3 Tested
BungeeCord 1.16 Tested

Platform-Specific Differences

Bukkit / Spigot / Paper (platform-bukkit)

  • Additional endpoints: /api/placeholder for PlaceholderAPI resolution.
  • API version: 1.16 (api-version: '1.16')
  • Soft dependency: PlaceholderAPI (optional)
  • Folia support: Automatic via FoliaLib (folia-supported: true)

Folia

  • Uses FoliaLib's PlatformScheduler for regionized task scheduling.
  • No code changes required — the Bukkit platform detects Folia automatically.

Velocity (platform-velocity)

  • Uses Velocity's native Scheduler for async tasks.
  • Commands registered via Velocity's command API.
  • Plugin ID: zyveraweb
  • Endpoints: /api/players (no PlaceholderAPI endpoint).

BungeeCord (platform-bungee)

  • Uses BungeeCord's ProxyServer.scheduler for async tasks.
  • Commands registered via BungeeCord's command API.
  • Endpoints: /api/players (no PlaceholderAPI endpoint).

Feature Parity

All three site types (web, proxy, node), the ACME client, rate limiting, virtual hosting, and metrics are available on all platforms. The only platform-exclusive feature is the PlaceholderAPI endpoint, which is Bukkit-only because PlaceholderAPI itself is a Bukkit plugin.