Skip to content

The most retarded error ever about statebag overflow #3528

@mcNuggets1

Description

@mcNuggets1

What happened?

[ sbag-update-dropped] Client xxxx sent too many state bag updates and had their updates dropped.
[ sbag-update-dropped] If you believe this to be a mistake please increase your rateLimiter_stateBag_rate and rateLimiter_stateBag_burst. You can do this with set rateLimiter_stateBag_rate [new value]. The default rate limit is 75 and burst limit is 125
[ sbag-update-dropped] You can disable this warning with con_addChannelFilter sbag-update-dropped drop if you think you have this properly set up.

Who thought of this bullshit of an error message?
It doesnt have any information about the issue WHATSOEVER, nor does it give debugging information.
It just says to increase the max limit. I wanna know which statebags caused this.

Expected result

Some fucking info to work with

Reproduction steps

Enjoy getting an error with no information whatsoever.

Importancy

Slight inconvenience

Area(s)

FiveM

Specific version(s)

FiveM

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugtriageNeeds a preliminary assessment to determine the urgency and required action

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions