Mark Bukkit plugin descriptor as Folia-supported

[Chwitst187]

Motivation

• Add folia-supported: true to the Bukkit plugin.yml so Folia/Paper recognizes the plugin as explicitly supported and does not reject it at runtime.

Description

• Added folia-supported: true to worldedit-bukkit/src/main/resources/plugin.yml to mark the Bukkit plugin as Folia-supported.

Testing

• Ran ./gradlew :worldedit-bukkit:processResources --no-daemon and the task completed successfully.

---

Codex Task

[Copilot]

Pull request overview

This pull request adds the folia-supported: true flag to the Bukkit plugin descriptor (plugin.yml) to indicate that FastAsyncWorldEdit (FAWE) is compatible with Folia, Paper's region-based multi-threaded server software.

Changes:

• Added folia-supported: true field to plugin.yml to mark the plugin as Folia-compatible

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Adding folia-supported: true indicates that the plugin is compatible with Folia's region-based threading model, but the codebase still uses legacy Bukkit scheduler APIs that are incompatible with Folia.

Folia requires using region-based schedulers (e.g., RegionScheduler, EntityScheduler, AsyncScheduler) instead of the global Bukkit.getScheduler() API. The current implementation in files like BukkitTaskManager.java uses methods such as scheduleSyncRepeatingTask, runTask, and runTaskAsynchronously which won't work correctly on Folia servers.

Additionally, code in BukkitBlockCommandSender.java uses Bukkit.getScheduler().callSyncMethod() which is also incompatible with Folia's threading model.

Before marking the plugin as Folia-supported, the scheduler usage needs to be adapted to work with Folia's region-based threading, or the plugin needs verified testing on Folia to ensure it actually works despite using legacy APIs (Paper's compatibility layer may handle some cases, but this needs verification).

Suggested change

	folia-supported: true
	folia-supported: false