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 Request: Separate lootmaster in raid from lootmaster in session #192

Open
JangXa opened this issue Aug 25, 2020 · 2 comments
Open

Comments

@JangXa
Copy link

JangXa commented Aug 25, 2020

We'd like to have one melee autoaward to the dedicated loot guy. We'd like this guy assign loot and that people trade him.
Right now the masterlooter in the session has to be the masterlooter ingame

@evil-morfar
Copy link
Owner

So to be clear; you want me to come up with a completely different system of determining the ML just because you have one guy that's too lazy to go loot the boss?

@JangXa
Copy link
Author

JangXa commented Aug 28, 2020

Im sorry let me elaborate:

You got two great functionalities in your addon that are linked together:

  1. The ability to do loot sessions, the vote, assigning winners by the lootmaster. I dont think this has to be linked to the ingame function.

  2. A way to autoloot stuff TO a specific person for a later session. This will only work with ingame lootmaster.

The scenario in our guild: We have a dedicated lootmaster that handles loot according to our guild rules. His role in the raid as player makes it cumbersome to loot every trash mob. Thats why we have a second melee player have the lootmaster roole ingame with the autoaward function to loot everything to the LM pockets.

Right now we swap the ML whenever a session has to be started, which sometimes causes smaller issues which need reloads etc.

I only had a rudimentary look at the code base so far, so I don't know how feasible would be to make the RCLC lootmaster different from the ingame lootmaster. If its a very fundamental assumption that ingame LM = RCLC LM I understand that this is a bit too much to ask.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants