If setting rules isn't working and/or Ragebot isn't detecting you as admin, there's two possible solutions.
First solution works if it does display admins correctly, but you still cannot set rules or use other admin-only commands despite being admin.
The solution is simple - you just invite someone to your group chat.
After that, it should let you set rules.
How to fix it if it doesn't let you use admin commands.
The second solution is only necessary if Ragebot doesn't display the admin list correctly.
You fix it by typing "Talkers" and then "Admins" again - then it should be fixed.
How to fix it if it doesn't display admins correctly.
If none of this worked, try removing Ragebot (if you are admin, you can do this through the "Rage leave" command) and re-adding it.
If you need further help getting it fixed, you can ask for our help in our Support Group.
There are several safeguards in place to protect the stability of Rage.
This includes flood prevention.
If you are muted by Rage, this will clear within 4 hours.
Ragebot lets you know in the group chat when you get muted.
From that moment until the clock expires, Rage will not respond to any commands or substituions triggered by you in the group you were muted in.
Ragebot can only kick spambots (thot bots) if Rage is made an admin.
Additionally, Rage will only kick bots as they enter the group - it doesn't kick any thot bots that are already in the group.
Ragebot will occasionally miss bots that may seem obvious to you.
This is because the thot bots creators change their bots very frequently in order to bypass Ragebots detection algorithm.
If a bot does not meet certain requirements of "being a bot" Ragebot will assume it is human.
These requirements have been lessened in later iterations of Ragebot due to complaints of false positives
If you see a new wave of thot bots that Rage isn't detecting, please take screenshots of them entering the group chat and send it to us in the Support Group.
Rage might accidentally misidentify real humans as bots from time to time, although it should be a rare occurance.
One way to work around this, is to have the same person rejoin again immediately after the first time - Ragebot will not kick upon second entry within a short time estimate.
Another way to work around this, is to either demote Ragebot temporarily, or making it leave through the "Rage leave" command, letting the person enter in peace and then re-adding RageBot and promoting it again.
If someone experiences this a lot, please contact us and we will find a solution.
This could be due to several reasons.
This could be because an admin has set some restrictions with the "Permissions" command.
If you are an admin of the group, you can check what Permissions is set to by typing "Permissions".
You can read more on the "Permissions" command under the Commands section.
If Ragebot only ignores one person but responds to everyone else, it is because they have been muted by Rage.
If Rage left your group right after someone joined, it may be because you already have another Ragebot in your group - please check your members list.
You should not use multiple Ragebots in the same group.
If it left during a time when nobody new joined the group, it usually means that that specific Ragebot has been banned by Kik.
There's nothing we can do to prevent this, but you can add in another Ragebot - check the Status page to view which ones are available.
We encourage users to use the Recommended bot (button at the top), that way you're guaranteed to get a bot that isn't full or overcrowded.
Remember to use the "Import all" command to recover the data for your group.
If you're trying to add in a new Ragebot to your group, you may get a message saying "Error - you can't add people to a group who aren't chatting with you. We'll send them an invite to let them know you tried."
This issue occurs if you haven't friended Ragebot first.
You can do this by private messaging Ragebot, saying "Friend" (without " ") - Ragebot should respond with "I'll be your friend! You can now add me to groups."
Example of the issue.
If Ragebot has ended up as an owner of the group, the admins can make it leave by using the "Rage leave" command in the group chat - then group ownership will be passed on to another admin.
If you want to pass on ownership of a group to someone else, remember to demote Ragebot first, or it might accidentally end up as owner when you leave the group.
If Ragebot has ended up as the owner and there are no admins left in the group, then Rage will automatically leave the group chat when the next user joins - then Kik will automatically grant ownership to someone from the group.
If Rage is owner/admin and there are no other active admins you can either contact Rayg directly (PM him on Kik, explain the issue and include the group #), or just create another group.
Sometimes issues occur with the 48 mode not functioning properly.
In the majority of cases, people forget to type "48 mode on" after setting a cap.
In most of the remaining issues, it can be fixed by removing Ragebot from the group and adding it back in.
If this doesn't work, contact us through the Support group and we will help you out.
Sometimes when you private message Ragebot, it will say "Oops, it looks like Rage's phone has been off/disconnected for a while. We'll deliver your message when they connect again."
This doesn't matter, and it doesn't mean Ragebot is offline - just ignore it.
Example of the issue.
Sometimes when you try to click directly on an @ of a Ragebot from within the Kik app, it displays an error saying "Oops - No user with the username was found."
This is a general Kik issue and not something we can fix - but if you click the username a second time, it should work.
Example of the issue.