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

[FEATURE]: Tag Players + Watchlist #628

Open
tabarra opened this issue May 7, 2022 · 4 comments
Open

[FEATURE]: Tag Players + Watchlist #628

tabarra opened this issue May 7, 2022 · 4 comments
Labels
database-related Stuff with direct impact to the txAdmin database. discussion A discussion based issue enhancement New feature or request

Comments

@tabarra
Copy link
Owner

tabarra commented May 7, 2022

Scope

Web, In-Game Menu, Developer API

Feature Description

As per Mr. 🐢 suggestion, a feature to be able to tag players, and a way to watch out for those players.
There should be a list of default tags (cheater, trouble maker, vip, streamer, friend, etc.), but it should also be configurable.

Use Case

If you want to tag people that paid to be unbanned (actually requested!) to pay extra attention to them.
I can also see this being used for tagging VIP players, Streamers and other People Of Interest.

Proposed Solution

  1. Create a dedicated player watchlist page with:
    a. List of available tags and a way to add or remove them;
    b. Some way of listing how many players in each tag;
    c. A list of players, with the tag in their name;
    d. A clear emphasis on those who are online;
    e. A button on the player card (web + ingame) to tag a player.
  2. Change the web playerlist (web + ingame) to prioritize in sorting the tagged player;
  3. For the ingame menu playerlist, add a button to filter by tag;
  4. This would probably be an array tags in the player object, or integrated with the notes thing.

Additional Info

  1. I'm pretty sure it would be needed to save to the player log the tag addition or removal;
  2. It has been requested a way to add notes to when you tag a player, this only makes sense if we do the bubble's notes ideas;
  3. Super interesting if this were integrated with the API, as in be able to tag a player through an exported function, or txAdmin emitting an event when a tagged player joins;
  4. Maybe something that allows tebex VIP integrations to mark the player?
@tabarra tabarra added enhancement New feature or request discussion A discussion based issue labels May 7, 2022
@tabarra
Copy link
Owner Author

tabarra commented Jun 30, 2023

Just like discord roles, each tag would have an order id, which could be used as the priority in the playerlist as well as if we decide to make a connect queue.

@Br0kenMaverick
Copy link

Super interesting if this were integrated with the API, as in be able to tag a player through an exported function, or txAdmin emitting an event when a tagged player joins

This would be really helpful. Looking forward to it.

@tabarra
Copy link
Owner Author

tabarra commented Aug 21, 2023

This idea would also work well with "automatic tags" which would be set to online players that meet a criteria but are not saved in the database.
Examples:

  1. ADMIN: [FEATURE]: Staff icon in player list #638
  2. NEWCOMER: [FEATURE]: Highlight new players in web console  #805
  3. WATCH LIST: Someone who had any warns or bans in the last week (configurable?).
  4. [FEATURE]: Players Playtime with IDs over head #973

@tabarra tabarra pinned this issue May 7, 2024
@tabarra tabarra added the database-related Stuff with direct impact to the txAdmin database. label May 7, 2024
@tabarra
Copy link
Owner Author

tabarra commented Oct 9, 2024

I guess would make sense for some tags to use discord roles as sources.
Just not sure what would be the best way to cache it for offline searches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
database-related Stuff with direct impact to the txAdmin database. discussion A discussion based issue enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants