Sunset for Rover API when calling on render commands.

[nikita-petko]

Description

As you may know, Eryn announced that the legacy API for Rover would be getting replaced:

Announcement

Hello RoVer API subscribers! The RoVer V2 API is live now. You can view the docs and create an API key by going to https://rover.link/guilds, choose your server, and click Developer API on the left side.

This new API will be replacing our legacy verify.eryn.io API. One month from today, requests to verify.eryn.io will have a small chance to result in an intentional error. In the days and weeks following, the error rate will steadily increase until the legacy API is completely disabled.

Differences from the legacy API

• All requests are now scoped to members of your server. You cannot retrieve information about a user that isn't in your Discord server.

• The popular reverse lookup API (Roblox ID to Discord account) has made a return!

• There is a new API for Plus subscribers to programmatically trigger a RoVer user update (equivalent to running /update on them)

Please check out the Developer API page for further information. Feel free to leave any questions or concerns in the #rover-help channel.

Thanks!

Reasoning

The reasoning behind the sunset is because there are not many other verification services that provide such a wide database of user resolutions, as Rover is one of the most popular one. So instead of refactoring existing code, scrapping it would be preferable as it removes a dependency.

Possible future updates

In the future, when guild-based configuration is implemented there may be a chance that this API is reincorporated but will be guild-scoped, and you will resolve to the user you verified as in that guild. But for this idea to become a thing, guild owners must provide an API Key on the configuration page.

How this affects you as a user.

You will no longer be able to run ;render and /render commands like:

;render (renders yourself)
;render (renders a user by mention)

/render self
/render discord_user user:<user_ref>

Closing notes

While this may affect some people, it may be better in the long run if guild-based systems are implemented. Please stay tuned in the future.