Google, Discord, and connected sign-in

Quick answer

Use the official Google or Discord buttons on Login or Register. To add a provider to an existing RSBazaar account, sign in to that account first and use Sign-in connections.

Register with a provider

Select Google or Discord first and complete its official sign-in/consent screen. If the provider is already connected, you can continue with the existing RSBazaar account. If it is not connected, RSBazaar asks for the remaining signup details, including Customer or Seller, a username, the current terms, and your private profile.

The registration uses the provider-verified email automatically, without asking you to verify it again using a separate RSBazaar email code. If the provider option is unavailable, use the email-and-password flow or try again later.

Connect an existing account

In Account settings, open Sign-in connections and choose the available Google or Discord connection control. Confirm the correct provider account in the provider window.

Discord uses one connection for sign-in and community features. You can also start from Discord. Server membership, accepting the rules, and your account's eligibility still determine community access. Connecting a provider does not merge unrelated marketplace accounts.

Unlink Google or Discord

1. Open Sign-in connections.
2. Select Request unlink for the provider.
3. Enter your current RSBazaar account password in the secure confirmation.
4. Review the request and its displayed completion time.

The provider stays connected for 48 hours. You can cancel before it completes. Discord unlink removes both Discord sign-in and the community connection together. If you do not have a local password, set one through Security before requesting unlink.

Troubleshooting and privacy

If a continuation expires, restart from the official provider button. If the provider belongs to another RSBazaar account or the visible state seems wrong, use Support instead of creating duplicate accounts.

Do not paste provider sign-in links, cookies, tokens, passwords, or codes into chat. Staff only need a safe description, the provider name, and the public error message.