v2.7.2

Fixed

• Callback executed on close to disable rewards and stop MIDI was only applied with rewards mode enabled. MIDI has to stop too with rewards mode disabled

Changed

• Improved blacklist and whitelist search performance. It was using "find" when an "indexOf" is simpler and can provide faster results

v2.7.1

Fixed

• Re-configuration of step 3 (REWARDS_MODE, VIP_REWARDS_MODE, TARGET_CHANNEL, SEND_UNAUTHORIZED_MESSAGE) always re-applied SEND_UNAUTHORIZED_MESSAGE even when properly configured
• Empty .env variable validation

Changed

• Convert TARGET_CHANNEL to lowercase since all Twitch usernames must be lowercase (the display name can have case sensitivity but does not apply here)

v2.7.0

Added

• !addchord update validation. If a chord progression is already saved with the same alias, an error is thrown
• Database "insert" method interface and implementation

Changed

• !sendchord disabled (only available for broadcaster) by default to avoid confusion with !sendloop
• !removechord default permissions restricted to only Moderators and Broadcaster
• Removed default !sendchord and !removechord rewards
• Lowered price for default !sendloop reward from 100 points to 50 points
• Default value for "SEND_UNAUTHORIZED_MESSAGE" variable changed to false
• Database interface method renames

v2.6.6

Fixed

• Typo in spanish text for !midihelp sendcc

v2.6.5

Changed

• !addchord now validates the chord progression before adding it

v2.6.4

Fixed

• Requests with no arguments. Now requests that require arguments throw an error if those are not provided

v2.6.3

Fixed

• Rewards were re-enabled on Config API /refreshConfig regardless if bot is on or off. Now only re-enables them if they were enabled before

v2.6.2

Changed

• Minor refactors in barLoopChange event listener, removed unused logic and reduced synchronous code
• Now MIDI is stopped automatically when closing the app

v2.6.1

Added

• Troubleshooting section for auth errors

Changed

• Removed .env from bundle, it is not required and creates confusion

v2.6.0

Added

• Incremental setup process. Now only invalid or not configured environment variables are prompted on setup
• Environment variable to toggle showing authorization errors, it always showed them before
• Safe commands now also follow requirements/whitelist/blacklist. "Safe" means they can be requested via chat while requests are paused or with rewards mode on

Fixed

• .env recreation without removing token JSONs, it gave authentication errors

Changed

• Now users in whitelist do not need to comply to role restrictions. Makes more sense now