支持 Folia

[StarWishsama]

• 迁移至 Folia Scheduler
• 为部分模块添加多线程支持
  • 为 TickerTask 引入异步调度器并行运行任务
  • sub region slimefun ticker (由于 Folia 没有显式获取所有 Region 的方法，故取消)
• Fix feature/folia分支部分多方快结构无法使用 #1082
• 正确处理传送
• 新增 Ticker 线程池配置，便于用户根据服务器情况调优
• Folia 不支持的事件替代方案（重生、登录、...）
• [API] concurrent safe 标记*
• 线程池管理
• 合并到 Insider 通道

*: BlockTicker#isConcurrentSafe() 用于标记当前机器 Ticker 是并发安全的，Slimefun 默认认为附属的机器是并发不安全的，并移至异步单线程处理这些机器。

[Copilot]

@StarWishsama I've opened a new pull request, #1193, to work on those changes. Once the pull request is ready, I'll request review from you.

[Copilot]

Pull request overview

Copilot reviewed 61 out of 61 changed files in this pull request and generated 5 comments.

---

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

[Copilot]

schedule(...) uses runLaterAsync(this, delay), but implementations mutate Player state (inventory/velocity/effects). On Folia this can run off the entity thread and cause region/entity-thread violations. Use runAtEntityLater(p, ...) (and similarly an entity-bound repeating scheduler) for these tasks.

[Copilot]

This Folia fallback schedules only a single delayed check and only completes when p.getHealth() > 0. If the player respawns later than this delay, items may never be returned and the returnTasks entry is never removed (blocking future scheduling). Use a repeating entity-bound task that retries until the player is alive/valid, and always remove the map entry when the task finishes.

[Copilot]

On Folia, the no-context overload now throws if neither a Location nor Entity is provided. There are still call sites using runSyncMethod(Callable) without context (e.g. DebugFishListener), which will now crash at runtime. Consider keeping the no-context overload safe (run inline when already on a region thread, otherwise require callers to pass Location/Entity), and/or deprecate it and update remaining call sites.

[Copilot]

This pattern is still vulnerable to a race: another thread can acquire the menu lock between menu.locked() and menu.lock(false), causing the ticker thread to block unexpectedly now that lock() is a blocking ReentrantLock. Prefer a tryLock-style API (return immediately when locked) or make lock(false) itself non-blocking.

[Copilot]

The executor is created with initSize - 1 / maxSize - 1, but the config keys are named as thread counts (init-size, max-size). This off-by-one mapping is surprising for operators and easy to misconfigure. Either pass the config values directly, or rename/update the config docs/defaults to reflect the - 1 semantics.