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

playerblips: Fixed that the resource "playercolors" should be activated for teams #474

Merged
merged 1 commit into from
May 10, 2024

Conversation

T-MaxWiese-T
Copy link
Contributor

The reason for this pull request is because the resource did not work the way I wanted it to. Only after I had a closer look at the code I realized that you can configure the playerblips resource in the meta.xml. Because I wanted the playerblips resource to take over the team colors that I have in my code, but that didn't happen. And since the server log said to activate the playercolors resource, I did it, but it didn't help. Only after I deactivated the playercolors resource and set "use_team_colors" to "true" did it work as expected.
Anyway, the playercolors resource only makes sense if you want to have random player nametag colors, which makes no sense for teams, since teams can only have one color.

…ed for teams

The reason for this pull request is because the resource did not work the way I wanted it to. Only after I had a closer look at the code I realized that you can configure the resource in the meta.xml. Because I wanted the playerblips resource to take over the team colors that I have in my code, but that didn't happen. And since the server log said to activate the playercolors resource, I did it, but it didn't help. Only after I deactivated the playercolors resource and set "use_team_colors" to "true" did it work as expected.
Anyway, the playercolors resource only makes sense if you want to have random player nametag colors, which makes no sense for a team, since a team can only have one color.
@jlillis
Copy link
Contributor

jlillis commented May 10, 2024

I realized that you can configure the playerblips resource in the meta.xml.

The intended use case is for admins to change the settings via the admin panel, but you can also do it directly via the meta.xml. This PR brings up another issue I just noticed - the resource has no event handlers for onSettingChange so it relies on admins knowing to restart the resource after changing a setting (a step that isn't documented anywhere). I'll open an issue to fix that separate. Your PR does improve functionality when using team colors so I'll merge it now. Congratulations on your first contribution here!

@jlillis jlillis merged commit 2cd28db into multitheftauto:master May 10, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants