christalman / enjinhelperrobot Goto Github PK

The bot does not seem to disassociate members when they leave a server. This is needed, because otherwise, if they rejoin, they may not be able to request their roles again.

The robot sometimes fails to respond to conversations, such as !enroll and !server.

Disjin should poll Enjin to detect when a user has been removed from an Enjin site. It could then remove any corresponding association, and remove any associated roles in Discord. This could occur when users remove themselves, or are removed by admins, such as when a ban occurs.

When a user leaves a Discord server, Disjin could remove any corresponding association, and remove any associated tags in Enjin. Given that this could remove all tags from an Enjin user, this feature might need to be optional.

The members search could be improved by including Enjin characters.

Search could also be introduced to the roles page.

The admin log sometimes fails to load, with an Enjin error being reported.

Server admins could control whether the bot provides the 'never enroll' option to users.

When the bot contacts users to enroll, it provides three options: enroll, enroll later, or never enroll. Some servers might have a strong desire for users to enroll, and so they might benefit from being able to remove the option to never enroll. This would mean that the bot would contact users forever until they enroll.

A JavaScript error prevents notifications concerning admin actions (such as making a role a server admin or a guest admin) from being displayed, even though the actions themselves are otherwise successful.

Currently, any errors reported by the Enjin API appear as a generic 'unexpected' error to the user in the Web app. This should be changed to clearly display than an Enjin API error has occured, perhaps with the error code and description.

It would be helpful for a warning to be displayed in the Web app before an update is applied to the bot that requires it to be restarted. Perhaps five minutes or so before a restart.

The !browse command could be made permissionless.

Currently, it requires that the user is a guest or server admin, but this is a legacy requirement, and there is no longer any need for this.

Web app sometimes fails to find a session even though a token has been provided.

This has been reported on Chrome Android.

The activity log should mention when users have been granted guest permissions.