Bug Report Guidelines

This document explains how to report bugs and technical issues with RFG Studio's products, services, and experiences.

A good bug report helps our developers and Quality Assurance (QA) team understand what went wrong, reproduce the problem, and investigate it more quickly.

Please provide as much relevant information as possible. You do not need any technical knowledge to submit a bug report.

1. Product

Tell us which RFG Studio's product, service, or experience you were using when the issue occurred.

If you are unsure which option applies, select the closest available option or Other.

2. Platform

Tell us what device or platform you were using when the issue occurred.

For example:

• Windows
• macOS
• iPhone / iPad
• Android
• Roblox
• Web browser
• Other

If relevant, include your operating system, browser, application, or device version.

3. Summary

Give your report a short and clear title describing the problem. Someone should be able to understand the general issue just by reading the title.

Good examples

• Vehicle becomes stuck after exiting
• Unable to sign in after linking my account
• Inventory does not update after dropping an item
• Menu disappears after changing teams

Avoid titles such as

• bug
• broken
• help
• doesn't work

Keep the title specific to the problem you experienced.

4. Description

Explain what happened in as much useful detail as possible.

Please keep each report focused on one issue. If you experience multiple unrelated problems, submit a separate report for each one.

Your description should explain:

• What were you trying to do?
• What happened?
• What did you expect to happen instead?
• Has the issue happened more than once?
• Did anything unusual happen before the issue started?

You do not need to know what caused the problem. Simply describe what you experienced.

5. Steps to Reproduce

If you can reproduce the problem, provide the exact steps required to make it happen.

For example:

1. Join the experience.
2. Select a team.
3. Spawn a vehicle.
4. Enter the driver's seat.
5. Exit the vehicle while it is moving.
6. Attempt to enter the vehicle again.
7. The vehicle can no longer be entered.

Please be specific. Instructions such as use the vehicle and it breaks make it much harder for us to reproduce the issue.

If you cannot reproduce the problem, that is completely fine. Tell us what you remember doing before it occurred.

6. Expected Behaviour

Explain what you expected to happen.

7. Actual Behaviour

Explain what happened instead.

Providing both the expected and actual behaviour helps us understand exactly what went wrong.

8. How Often Does It Happen?

If possible, tell us how frequently you experience the problem.

• Every time
• Most of the time
• Sometimes
• Rarely
• Happened once
• Unsure

You can also provide additional details, such as It happened 3 out of 5 times.

9. Screenshots and Videos

Screenshots and videos can be extremely helpful when investigating a bug.

Consider attaching evidence when reporting:

• Visual glitches
• UI problems
• Error messages
• Gameplay problems
• Animation issues
• Unexpected behaviour
• Problems that are difficult to explain in text

Videos are particularly helpful for issues that require several steps to reproduce.

Please make sure your attachments do not contain passwords, private messages, personal information, or other sensitive information.

10. Error Messages

If you received an error message, include it in your report. Whenever possible, copy the exact message rather than describing it from memory.

A screenshot of the error is also helpful.

11. When Did It Start?

If you remember when the issue started occurring, let us know.

If something worked previously but no longer works, mentioning this can be particularly useful to our developers.

12. Check for Existing Reports

Before submitting a report, please check whether someone has already reported the same issue.

If an existing report describes the same problem, add any new or useful information there instead of creating a duplicate.

If your problem is different, create a new report.

13. Do Not Exploit Bugs

Finding a bug does not give permission to intentionally abuse it.

If you discover an issue that can provide an unfair advantage, bypass restrictions, duplicate items or currency, affect other users, or otherwise be exploited, stop reproducing it once you have enough information to report it.

Repeatedly exploiting a bug may result in moderation action regardless of whether the bug was eventually reported.

14. Security Issues

This includes issues involving:

• Account access
• Authentication or permission bypasses
• Exposed private information
• Exposed passwords, tokens, or credentials
• Vulnerabilities that could affect other users
• Vulnerabilities affecting RFG Studio's systems or services

Please report potential security issues privately through our designated support by email [email protected] or create a ticket at our dedicated project Discord server.

Do not publicly share instructions for reproducing a potential security vulnerability.

15. Protect Your Information

Never include sensitive information in a bug report.

This includes:

• Passwords
• Login or verification codes
• Authentication tokens
• API keys
• Session information
• Private keys
• Payment information
• Personal information

RFG Studio's staff will never ask for your password to investigate a bug.

If you accidentally include sensitive information in a report, contact us as soon as possible.

Before Submitting

Before submitting your bug report, please check that:

• Your title clearly describes the problem.
• You are reporting one issue at a time.
• You explained what happened.
• You explained what you expected to happen.
• You included reproduction steps where possible.
• You identified the affected product and platform.
• You attached useful screenshots or videos where appropriate.
• You removed personal or sensitive information.
• You checked whether the issue has already been reported.