Fixed a wrong node permission check (as a result the quick link to ban wasn't present in the posts).
Fixed the permission to reply ban in own threads.
XenForo does not allow to reply ban staff members by default, but since Reply Ban Plus allows you to choose which user groups are protected, I removed the check of staff members.
This means that if a staff member is not in a protected user group, he can now be reply banned. This allows more flexibility with the permissions.
The error message about a user that cannot be banned will now include multiple usernames. Previously if you tried to ban multiple users and few of them couldn't be banned, the error complained about one user each time. Now the error will include all users at the same error.
Corrected error phrases to avoid confusion.
When trying to reply ban multiple users while few of them cannot be banned, you'll get an error. In such case, no one of the specified users will be banned. Some moderators may think that while there are users that couldn't be banned, the other specified users are successfully banned. To avoid this confusion, the error is now specifically says that the action couldn't be completed.
Added file health check to verify that all files uploaded correctly and have the expected content.
New permission: Allow user to reply ban in their own threads. Now you can reduce reports from users by letting them more control over their threads. Note that the ability to send alert about the ban is disabled cause users may abuse this. Admins or moderators with the global permission to give reply bans can send alerts as usual.
New permission: Protect users/usergroups from being reply banned.
Since users can now give reply bans, they probably should not be able to ban anyone they want. So this is a permissions to protect groups from being reply banned.
The new permissions are also forum specific. Meaning you can specify different permissions for each forum.