VerityAI 5.1

Added

• BlueMap & Dynmap integration. VerityAI now automatically detects whichever supported live map plugin is installed. Both integrations are fully optional, checked independently, and configurable through integrations.map.bluemap / integrations.map.dynmap.

  • No polling — map data is fetched only when requested through /verity map or the AI's get_map_info function when function-calling is enabled.
  • /verity map now shows whether a live map is active, whether the player is visible on it, and provides a direct link to their current position.
  • Added the get_map_info AI function, allowing VerityAI to answer map-related questions such as "can you show me on the map?" with a real map link instead of guessing.
  • Added an extensible MapProvider interface. Additional map integrations, such as Squaremap, can be added through new provider implementations without changing the existing map system.
  • If neither BlueMap nor Dynmap is installed, or if their API becomes unavailable, VerityAI logs a clear warning and continues running normally without crashing.

Fixed

• BlueMap provider initialization. Fixed a compilation error in BlueMapProvider where the BlueMap enable listener could reference the plugin field before it was initialized.

  • BlueMap listeners are now initialized inside the constructor after the VerityAI plugin instance has been assigned.
  • Preserves clean listener registration/unregistration during plugin enable and shutdown.

• Reminder times ignored player/server timezone differences. /verity task add 8:00 ... previously used the server's local timezone, which could cause reminders to fire at the wrong time for players in different timezones.

  • Players can now set their personal timezone offset with /verity task timezone <+HH:mm> (for example, +03:30).
  • Reminders now use the player's configured offset.
  • Fully backward compatible — players without a configured timezone continue using the server's local time.

Notes

• No breaking configuration changes. The new integrations.map.* settings are additive and use safe defaults. Both BlueMap and Dynmap integrations are enabled by default and automatically detected when installed.
• To enable map links, configure integrations.map-web-url with the map's actual public URL. BlueMap/Dynmap's internal webserver address may not be publicly accessible, especially when using a reverse proxy or external hosting.
• VerityAI verifies that the map plugin is running but does not attempt to guess the public-facing URL.