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

Ability To Specify Progression On A Per-User Per-Server Basis #107

Open
Deadmano opened this issue Jan 26, 2023 · 0 comments
Open

Ability To Specify Progression On A Per-User Per-Server Basis #107

Deadmano opened this issue Jan 26, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@Deadmano
Copy link
Collaborator

Currently the artifact sorting takes into account the most optimal artifacts, but not the player behind it, which can cause issues in a training run where inexperienced (trainees) users are given the top tier artifacts but are not using them in calls, or being dead/dying when the artifacts are needed. This obviously impacts the training run as a whole and requires manual artifact sorting which defeats the purpose of the bot.

I'd like to see a way to have 3 tiers that can be assigned by a raid leader role, so that tier 1 (training) only allows a small sub-set of artifacts to be selected, tier 2 (progression) allows slightly more, and tier 3 (completed) offers the best of the best artifacts.

That way when sorting needs to happen, the experienced players will have the best artifacts to assist the team via damage buffs/mitigation, and the less experienced players are still able to contribute but the team overall won't be as impacted if an artifact is missed.

Failing this (if it is overly complex) a way to simply pick from a list of artifacts a user has selected for their class could also work. So you'd assign artifacts they're allowed to use, and when the sorting takes places it will avoid giving them higher tier artifacts since they weren't selected in the first place.

@Deadmano Deadmano added the enhancement New feature or request label Jan 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant