RoVer automatically updates the roles of active members in your server from time to time, so they don't have to click the update button themselves. This page explains how automatic updates work and how to configure your server so that every update produces exactly the roles you intend.

§What automatic updates do

When members are active in your server, RoVer periodically re-checks them in the background and updates their roles and nickname, exactly as if they had run the update command themselves. Nothing about the update itself is different. The only difference is that nobody had to click a button.

§An update can happen at any time

Because updates can be triggered automatically, and because members can always request one themselves on our website or with the update command in your server, you should treat every role RoVer manages as something that can be re-evaluated at any moment.

An update never invents anything: it reads the role bindings on your server dashboard and applies them to that member. They receive the bound roles they qualify for, and lose the bound roles they don't. If an update ever changes roles in a way you didn't expect, it means the roles members were holding didn't match your bindings, and the update brought them back in line.

This is why your RoVer dashboard should be the source of truth for the roles it manages. When your bindings describe exactly who should have each role, it doesn't matter when an update happens or who triggers it. Everyone simply ends up with the correct roles.

§Common configuration mistakes

Two setups reliably lead to unexpected role changes:

• Manually assigning or removing roles that RoVer manages. Your manual change only lasts until the next update, because the binding still says otherwise.
• Multiple bots managing the same role. The bots can disagree about who should have the role and undo each other's changes, and it becomes difficult to tell which bot did what. We recommend that only one bot manage any given role.

Instead of working around your bindings, change them to describe what you want. Our guide on setting up your server covers this, including how to mark a role as "give only" so that RoVer will grant it but never remove it. That's the right choice when you want to handle removals yourself.

§An example of what can go wrong

Say you bind a Discord role to the Leader rank of your Roblox group. Later, you have a falling out with one of your Leaders, and you remove their Leader role in Discord.

While you're asleep, that member is updated. Perhaps automatically, or perhaps they ran the update command on themselves. RoVer checks your group, sees that they still hold the Leader rank on Roblox.com, and gives the role right back. You might wake up to some unexpected drama.

The demotion didn't stick because the binding points at your group, so your group is the source of truth for that role. The correct move is to demote them on Roblox.com first, and then run RoVer's update command on them. After that, every future update agrees with your decision.

§Turning automatic updates off

You can turn off automatic updates in the Behavior tab of your server dashboard. RoVer will stop re-checking members based on activity, but members are still updated when they join, when they verify, and whenever they request an update themselves.

Keep in mind that this only changes when updates happen, not what they do. Members can still trigger an update at any time, so a configuration that doesn't match your intent can still produce unexpected results. Correcting the configuration is what prevents them.