Skip to content

4.3.0: Foundry VTT v13 support
Compare
Choose a tag to compare
@lucasmetzen lucasmetzen released this 04 Jan 10:36
· 23 commits to main since this release
4.3.0
b1d636d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

What's Changed

✨ Improvements

  • Add support for UI changes in Foundry VTT v13 in #94
    • Core v13 introduces changes to the UI which prevented LAME Messenger from adding the button to open its window. This is fixed (tested on the latest 13.334).
    • The button to open the LAME Messenger window is always visible:
      • When the sidebar is expanded and the chat tab is active, the button is positioned here:
        image
      • When the sidebar is collapsed and the Core setting "Chat Notification" is set to Chat Cards (in dialog "User Interface Configuration"):
        image
      • When the sidebar is either collapsed and the Core setting "Chat Notification" is set to Notification Pip or the sidebar is expanded but the active tab is not chat:
        image
    • The option to not add the button the UI or not has been removed.
    • As the button in/next to the sidebar is always accessible, the option to add a second one to the scene controls toolbar on the left side of the screen is not available starting with Core v13. It is still available in v12.
  • Additional filtering of system generated whisper messages: Both welcome messages in new worlds, Getting Started and Inviting Your Players, are now ignored by LAME and will not show up in its history.
    image

Known issue in v13

In the current preview version of v13 (namely 13.334), there seem to be changes under way to the SetField type which is used in the configuration to select users to be excluded in LAME. This causes the users to be listed by their ID instead of their name:
image
To avoid premature work fixing this, this won't be worked on until a more stable version of v13 is released.
The feature to exclude users still works though (if you know the user's ID or by trial and error).

Full Changelog: 4.2.0...4.3.0

Maintenance

  • Refactoring work has begun in order to make the code easier to adjust to future changes and additions, as well as adhere more to best practices for Foundry modules.
  • Introduce partial context preparation & improve code separation in #86
Assets 4
Loading