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

Bound max loot can on loot split to top hostiles #424

Open
MikeJeffers opened this issue Nov 3, 2021 · 0 comments
Open

Bound max loot can on loot split to top hostiles #424

MikeJeffers opened this issue Nov 3, 2021 · 0 comments
Labels
Difficulty: Easy This issue would be easy to do, and has little uncertainty in scope and implementation performance Priority: Low This ticket is not part of any forseen need or upcoming roadmap item

Comments

@MikeJeffers
Copy link

https://github.com/OpenPerpetuum/PerpetuumServer/blob/Development/src/Perpetuum/Zones/NpcSystem/Npc.cs#L1002-L1011
It is possible that this could be a very expensive transaction if there are countless many on the threat table of a boss. This tends to really lock up tables when all these entities are divided and created into many loot cans which then need to be sent to all players (which will also mutually see other loot cans as they are all visible to other units).

A safe upper limit would be a good MVP (64? 32?) Anything other than none..
Even better if the loot is given to the top participants if these maximum is reached that would be even better.
Sort the Hostiles by Threat value to indicate this.

@MikeJeffers MikeJeffers added performance Difficulty: Easy This issue would be easy to do, and has little uncertainty in scope and implementation Priority: Low This ticket is not part of any forseen need or upcoming roadmap item labels Nov 3, 2021
@clouths clouths moved this to BACKLOG in Game Server Dec 17, 2023
@clouths clouths moved this from BACKLOG to Checkup in Game Server Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Difficulty: Easy This issue would be easy to do, and has little uncertainty in scope and implementation performance Priority: Low This ticket is not part of any forseen need or upcoming roadmap item
Projects
Status: Checkup
Development

No branches or pull requests

1 participant