Starting to keep track of changes as of October 28, 2015. I will try my best to keep this file updated.
You can also browse the commit history to track my commits: https://github.com/owenconti/livecodingtv-bot/commits/master
- Possibly fixed issue with bot disconnecting after a certain period of time without sending a message to the server.
- Updated default enabled commands to disable
unavailableandgreetingcommand.- If you want to use either of these commands, please make sure you updated your
setup/custom/settings.jsonfile.
- If you want to use either of these commands, please make sure you updated your
- No longer greet the bot or the streamer in the
greetingcommand. - Replaced Pastebin with Gist for help documentation and youtube playlist track output.
- Required update
- Delete your
helpbrain file before starting up. - Update the
youtubeplugin to latest from repo, if you use that command. - Setup your Gist/Github access token in
credentials.js{ "gistUsername" : "owenconti", "gistAccessToken" : "ajskfnasdifhj98y3129uncawdf" }
- Added a setting for the
unavailablecommand to enable/disable the command. - Added a
setsubjectcommand, to set the room's subject via XMPP. - Added the ability to pass a settings object to the
client.jscode of plugins. - Updated
helpcommand to output a link to Pastebin when called. - When the bot starts, it will generate and store the documentation for help in a Paste on pastebin.com.
- Greetings are now run through a templater with
usernameandstatusvariables being passed-in.
- Say command messages limit increased to 80 characters.
- Added a Say message to the ban command.
- Decreased ban flyout duration to 6 seconds from 10 seconds.
- Case-insensitive command matching (assuming all commands register their regex in lowercase).
- Added setting to customize the on-ban say message.
- Added setting to enable/disable the Say utility.
- Added the loadUrl function to the Assets utility class.
- Updated ban management to display the ban police image when a user is banned.
- Replaced node-xmpp with node-xmpp-client.
- Required update
- You must run
npm installafter pulling this change.
- Hopeful fix for the brain to stop it from erasing files when an error occurs.
- Removed public.html and replaced with the
/clientfolder. - To run the new client page:
- Make sure the bot is running
- Open a new terminal window and navigate to
/client - Run
python -m SimpleHTTPServer {PORT} - Navgiate to
localhost:{PORT}/#{USERNAME} - The websocket connection should happen, any plugin code should be loaded, and then the client page should be ready to go.
- Setup plugins to register themselves for the client page.
- Moved playlist.js command to a
youtubeplugin.- Required update
- If you used the playlist.js command, you will need to install the plugin to use it.
- Ensure you have a
settings.jsonfile in theyoutubefolder. The structure should be:{ "youtubeApiKey" : "aisjdoi12masdasd", "requiredVotesToSkip" : 3 }
- Removed the doge flyout from the
saycommand. Will come back soon as part of the flyouts plugin.
- Fixed error with Client.js getUser() where it would crash when no
usersbrain file existed.
- Updated pattern for
Templaterclass to use '{{VAR}}' instead of '${VAR}'.- Required update
- If you are using the
Templaterclass, make sure your template strings use the '{{VAR}}' pattern.
- Removed the
upcomingplaylist command - Updated
skipplaylist command to be random - Fixed auto ban command
- Changed how user messages are stored.
- Required update
- If you depended on userMessages, you should clear your userMessages brain file because the structure has changed.
- Assets now load custom assets, and then core assets.
- Rearranged setup folder so it makes more sense.
- Updated the Loader class to read settings files to determine which commands and plugins it should load.
- Required update
- By default, all core commands are enabled.
- By default, all plugins are disabled.
- You must add a
coreCommandsandpluginssetting to yoursetup/custom/settings.jsonfile if you want to enable or disable commands and plugins.
- Fixed bug with
greetingcommand where an existing user with a status that did not have a matching greeting, was not greeted.- Required update
- If you had any custom greetings, you will need to update to the new greeting structure. See
setup/core/settings.jsonfor an example.
- Updated Loader to allow bot to start without a
/pluginsdirectory. - Verifying credentials.js includes the required attributes to start up when starting the bot.
- Moved a couple classes into the
utilsdirectory.- If you required any of the following files, you will need to update your references:
ChatBot.jsClient.jsLoader.jswebsocket.js
- If you required any of the following files, you will need to update your references:
- Created a
Settings.jsutility file, to easily load settings. - Created a
setupdirectory, and started adefaultSettings.jsonfile to keep default settings. - Moved
credentials.jsinto thesetupdirectory.- If you required
credentials.js, you will need to update your references.
- If you required
- Added available statuses to the default settings
- Added
hasStatusto User model to easily check for a specific status - Updated various commands to pull from default settings file
- Added
Templaterclass, to build strings from a template - Added
Assetsclass, to load assets into the bot - Updated say command to display a popout doge when !say is used