You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While hubot.coffee tests Meteor.settings for a botname field which determines the name by which the bot can be addressed, the bot's name when speaking is always codexbot, which is also assumed by client-side code. 'botname' should be set in the public part of settings and used as the name the bot speaks as. (Yes, even though everyone says bot instead of codexbot.)
The text was updated successfully, but these errors were encountered:
Torgen
added a commit
to Torgen/codex-blackboard
that referenced
this issue
Jan 5, 2019
Formerly you could set the name the bot responded to, but its display name would always be codexbot. Now you can set its display name with the botname setting/BOTNAME environment variable, and its gravatar with the botgravatar setting/BOTGRAVATAR environment variable.
On the client side, the latest botname is detected with a 'bot_wakeup' field.
Disallows logging in as any name the bot has ever used.
Will address cjb#336 but depends on the custom login handler.
While hubot.coffee tests Meteor.settings for a botname field which determines the name by which the bot can be addressed, the bot's name when speaking is always codexbot, which is also assumed by client-side code. 'botname' should be set in the public part of settings and used as the name the bot speaks as. (Yes, even though everyone says bot instead of codexbot.)
The text was updated successfully, but these errors were encountered: