01Planned
Player assistance
The same questions, every session.
Contextual help using approved server rules, guides and game knowledge, with sources players can check.
Plugins & tools In development
Better tools.
Stronger communities.
Built around the work behind the worlds.
Repeated support questions. Logs to investigate. Events to prepare. Arkaine is developing custom server plugins and AI-enabled tools to help multiplayer communities handle that work with care.
Explore the development areas01 / Architecture direction
Local-first.
Not local-only.
Prefer local or self-hosted models for suitable routine tasks, low latency, sensitive information and manageable costs. The right choice depends on the task and the hardware available.
Optional external or frontier APIs can support stronger reasoning, larger context, richer interactions or capabilities that are impractical to run locally. The design stays flexible across providers.
External processing may send selected information off the server. Operators should decide what may be shared and which routes are permitted; privacy is a design consideration, not an absolute guarantee.
- 01
Player or admin request
Approved knowledge and the context needed for the task.
- 02
Operator rules & routing
Permissions, data boundaries and a choice of model.
Local / self-hostedOptional external API - 03
Review, then respond
A response, or a validated tool action. Admin approval where required.
Models would not receive unrestricted server access. Approved tools, validation, rate limits and audit records are design requirements around any action.
02 / What we are working toward
Less busywork.
More time for the world.
The overall initiative is in development. These individual capabilities are planned directions, not a list of released products or live server features.
02Planned
Administration & diagnostics
Less time searching through logs.
Help operators review logs, investigate errors and understand configuration changes before applying them.
03Planned
Moderation assistance
More context for difficult decisions.
Organize reports and surface relevant context. Consequential moderation decisions stay with human admins.
04Planned
Events & narrative
Make room for the memorable moments.
Support event preparation, community activities and optional narrative experiences within operator-defined rules.
05Planned
Permission-controlled actions
Useful actions need clear boundaries.
Expose a limited set of approved tools, with permissions, input validation, rate limits and an audit trail.
06Planned
Flexible model routing
Different jobs need different tools.
Route suitable work to local or self-hosted models, with optional external APIs when a task needs more capability.
03 / Operators stay in control
Assistance with
accountability.
Permission before action
An approved tool list, scoped permissions, validation and rate limits should bound what a system can do. An unavailable model or failed check should leave the operator with a clear failure, not an unverified action.
People make consequential decisions
Moderation and operational decisions need human/admin oversight. Auditability should make it possible to understand the request, the proposed action and who approved it.
Validate in the world it serves
A server network gives this work a practical setting: latency matters during play, permissions differ between players and admins, and failures must be recoverable. Arkaine intends to use that setting to evaluate player experience before wider availability. Completed testing or measured gains are not being claimed.
Development status
Follow the work.
Help shape what matters.
The tooling initiative is in development, with individual areas still planned. No public release date, downloads or production AI rollout are announced here.
Have a recurring server problem or an idea for a useful tool? Use our existing community and contact channels.
Join Discord