Releases: UnifierHQ/unifier
Releases · UnifierHQ/unifier
3.3.2
- Fixes inaccurate room server count
3.3.1
- lil easter egg (check the console after rebooting)
3.3.0
- Rotating status has custom status for October and December (this can be disabled in config.toml)
- TokenStore access attempt is now detected in
u!eval
(IMPORTANT: This does not guarantee complete prevention of token leaks. Always double check your code before youu!eval
it.) - Unifier will now ignore unavoidable external platform errors (such as 401s, 403s, and 5XXs, this depends on the support plugin)
- "Channels & Roles" and "Browse Channels" are now automatically converted to placeholders in friendlifier
- Bridging and certain commands will be disabled if the bot has Administrator permissions
external
key in config.toml is now deprecated and may be removedu!restart
will become unavailable on bootloader upgrades- Test token for encryption password verification is now randomized on every .encryptedenv file save
- Fixed bug where test token can be modified in token manager
- Fixes an error in emoji parser that prevented some messages from being sent
3.2.8
- Embeds are no longer converted for user messages (bot messages will still have conversion)
3.2.7
- Lottie stickers will be ignored when checking for empty messages
3.2.6
- Correct variable is now used for detecting empty message for sticker bridging
3.2.5
- Sticker bridging is now disabled for system messages
- Newline will only be added when content is not empty
3.2.4
- Adds sticker bridging to external platforms
- Adds role mention support to text friendlifier
u!uptime
command will now display bot name properly- Fixed files not being bridged from external platforms
3.2.3
- Plugins are now called Modifiers
- Platform files can now be prepared for each server rather than for all
- Role mentions are now supported in text friendlifier
- Fixes bridge fail when a mention has an unknown user
- Fixes localization not updating on upgrade
3.2.2
- Correctly use threaded bridge
- Fixes reply author text and reply content being empty