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

feat(core-five): custom and expanded blip categories #3223

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

tens0rfl0w
Copy link
Contributor

Goal of this PR

This PR introduces custom blip categories to the game, allowing for more flexible organization of blips.

How is this PR achieving the goal

The game reserves blip category IDs 12 - 254, but they are unused and have no associated code paths. This PR leverages this unused range to define custom blip categories, enabling better grouping and organization.

  • Blip categories 12 - 133: These are named categories. They support a prefix, which can be set using:
    AddTextEntry("BLIP_CAT_" .. id, categoryName)

  • Blip categories 134 - 254: These are unnamed categories. They do not have a prefix but still serve to group blips together.

blip-tests

This PR applies to the following area(s)

FiveM

Successfully tested on

Game builds: 2372, 3407

Platforms: Windows (Client)

Checklist

  • Code compiles and has been tested successfully.
  • Code explains itself well and/or is documented.
  • My commit message explains what the changes do and what they are for.
  • No extra compilation warnings are added by these changes.

Fixes issues

Requested here: https://forum.cfx.re/t/2191939

This adds custom grouped blip categories to the game.

Categories 12-133 are categories that have a name prefix, that can be set with `AddTextEntry("BLIP_CAT_" .. id, categoryName)`.

Categories 134-254 are unnamed categories, so they don't have a prefix and just group the blips together.
@github-actions github-actions bot added the invalid Requires changes before it's considered valid and can be (re)triaged label Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid Requires changes before it's considered valid and can be (re)triaged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant