Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Servers show a confusing "sv_disableClientReplays" to end users #2367

Closed
blattersturm opened this issue Jan 31, 2024 · 1 comment · Fixed by #2452
Closed

Servers show a confusing "sv_disableClientReplays" to end users #2367

blattersturm opened this issue Jan 31, 2024 · 1 comment · Fixed by #2452
Labels

Comments

@blattersturm
Copy link
Contributor

blattersturm commented Jan 31, 2024

What happened?

Ever since recent server artifacts, server info pages show a confusing variable called 'sv_disableClientReplays'.

Web UI:
image

In-game UI:
image

This isn't documented and I don't think this is meant to show to end users. People are also evidently confused about it on the Discord:

image

Expected result

This variable to be suppressed from the UI, like other internal variables

Reproduction steps

  1. Launch FiveM.
  2. Click on a server in the server list.
  3. Note the variable being displayed.

Importancy

Slight inconvenience

Area(s)

FiveM, RedM

Specific version(s)

FiveM Ver.7388/canary

Additional information

No response

@blattersturm blattersturm added bug triage Needs a preliminary assessment to determine the urgency and required action labels Jan 31, 2024
@github-actions github-actions bot added the RedM Issues/PRs related to RedM label Jan 31, 2024
@nihonium-cfx nihonium-cfx removed the RedM Issues/PRs related to RedM label Jan 31, 2024
@LCK-Locke
Copy link

Is there any way to remove it?
Thanks

@github-actions github-actions bot removed the triage Needs a preliminary assessment to determine the urgency and required action label Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants