Releases: AverageHelper/Gamgee
Releases · AverageHelper/Gamgee
v1.3.1
Added
- Include a link to our repository when users run
/version
- Add @karcsesz to the README list of contributors
- Add proper Code of Conduct and Contributing docs
- More random things to say
Changed
- Functional refactor: Trying to slim down on the spaghetti, I've refactored most of the core structures from object methods to free functions. Data shouldn't have conceptual responsibilities over data. There's lots more cleanup work to be done, especially to organize these new functions in a sane way, but the preliminary work is done.
- Improved formatting of interaction counts
- Re-do how we parse Bandcamp links. (The url-metadata package is not well-maintained, and contains some minor security vulnerabilities that GitHub really wants me to fix. Since the package is quite small, I moved it in-house for now and patched it myself.)
- Update our compile target to native ESM syntax. (You are running Node 16, right? ;)
- Ditch an old database migrator that hasn't been relevant since before v1.0.0
- Clarified some documentation comments, especially in textResponses.ts
v1.3.0
Added
Added a "Likes" counter to the request queue. Most users won't notice this, but DJs might.
- Every time a user runs
/now-playing
or its variants on a song that they didn't submit, the Likes counter increments. - Subsequent invocations from the same user do not add to that counter
NOTE: You should not have to run the migrator, since we only added an optional field to the database here.
Coming soon: The ability to disable the Likes counter, for DJs who are concerned about it.
v1.2.5
Fixed
- Bandcamp support hotfix
v1.2.4
Added
- Some more silly random quotes
- That's it. That's the update.
v1.2.3
Changed
- Updated
ytdl-core
again
Fixed
- Fixed
github-metadata
dependency issue by ditching it and calling the GitHub API ourselves lol - Fixed
sqlite3
dependency issue by installing a fork instead
v1.2.2
Changed
- Clearer comments in some handy places
- Update ytdl-core
Removed
- Remove redundant logging around the
now-playing
command, now that that's fixed.
v1.2.1
Fixed
- Set
sentAt
to the current time as we insert a queue entry, instead of using Discord's incoming message timestamp. This should fix the ordering issue with?now-playing
.
v1.2.0
Added
- Add support for aliasing commands.
- Certain predefined strings may be used as aliases to commands. This does not affect the behavior of slash-commands, since those have autocomplete.
- Add
?nowplaying
as an alias for?now-playing
Changed
- Better ergonimics for
/sr
reply timing.- Before, we only embedded the user's requested song after a successful queue entry.
- Now, we embed the song right away then remove the embed if queue constraints reject the song. Just like
?sr
.
- More consistency between
/sr
and?sr
.- For
/sr
requests, Gamgee emulates the message behavior of?sr
requests.
- For
- Slightly more aggressive about pinging users when we need to get their attention.
Fixed
- Fixed a bug that caused Gamgee to crash when users sent non-URL song requests.
v1.1.0
Added
- Added a contributor to the README. (Thanks again, @ajnrules!)
Changed
- Simplified a few things
- Complicated some others
- Made my
JobQueue
class its own package.
Fixed
- Song requests that use
/sr
now behave more closely to requests that use?sr
- There has been some confusion to do with the way Gamgee handled slash-command requests. Basically, we would only post that the song had been requested if the request made it in. This means that the crowd often saw the request and the confirmation go in at the same time when people used
/sr
, whereas other requests (using?sr
) had more time between request and confirmation. - I'm pretty sure Gamgee treated both kinds of requests fairly; it just didn't tell everybody about
/sr
requests until they already got in. - This should make things more clear for the crowd, if a bit jumpy in the chat for requesters. Gonna iron that out later.
- There has been some confusion to do with the way Gamgee handled slash-command requests. Basically, we would only post that the song had been requested if the request made it in. This means that the crowd often saw the request and the confirmation go in at the same time when people used
v1.0.0
Added
- Add a
/test
and?test
command to check that Gamgee can still talk to our video APIs - More silly random responses lol
Changed
- Update to Discord.js v13
- Updated README
- More stable slash commands for song requests
- Gamgee considers YouTube live streams to be videos of infinite length
- Improved queue stats output
- Inform users publicly when we can't reach their DMs
- Improved debug logging
Fixed
?help
and/help
now work in DMs