Releases: amoeba/TownCrier
Releases · amoeba/TownCrier
v1.3.2
This release fixes a breaking bug in Discord webhooks and is a recommended upgrade for all users.
FIXED
- Fixes broken Discord integrations by enabling TLS 1.2 support. #91. Thanks to @trevis for this contribution.
CHANGED
- Upgraded Newtonsoft.Json from 12.0.3 to 13.0.1. #89. This shouldn't result in any changes for end users.
v1.3.1
v1.3
v1.2
v1.1.0
This is a minor release and mainly fixes two edge cases.
FIXED
- Fixed an issue where webhooks could fail from bad input. Thanks to Brycter for the report. 98ce97d & #74
- Fixed an issue with timed triggers causing disabled timed triggers to not be able to be re-enabled. b8d4ee7
NEW
- Added a pre-defined event for rare items leveling up. Thanks to Beale for this one.
v1.0.0
This is a major release and is more or less where I wanted to get TownCrier to so I'm marking it as v1.0.0.
NEW & CHANGED
Major stuff
- Profiles are now character-specific by default. Webhooks are still shared across all profiles.
- Profiles can be controlled with the
/towncrier profile
- Shared profiles can now be created so multiple characters can use the same profile.
- Chat Triggers can now uses regular expression capture groups and your
Message
can reference those like you already do for other variables except by number. e.g., Use $1 to substitute your first capture group.
Other
$SERVER
can now be used as a variable
v0.2.3
v0.2.2
NEW
- You can now trigger webhooks using chat which makes it possible to trigger webhooks with metas and the like. Commands are prefixed with
@towncrier
,@tc
,/towncrier
, or/tc
. - Schneebly graciously added a pre-defined event for your character finding a rare which makes it a bit easier to set up (versus using a chat trigger). Thanks!
- New variables:
$DATE
,$TIME
, and$DATETIME
.
FIXED
- Fixed some issues with chat triggers you hopefully never noticed
v0.2.1
NEW
- Chat Triggers now use regular expressions to match chat messages so you can be more fine-grained or flexible about what you match. The $EVENT variable will still send the entire line of incoming chat text even if your regular expression uses match groups.
FIXED
- There was a bug with Chat Triggers where you couldn't use the
$EVENT
variable with tells. This was due to how tells (and generally, clickable links in chat) work under the hood uses a format similar to<a>
tags in HTML.