Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

smart loot rules

Open
#146 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
game-dev

Research direction

The issue names no files, tests, or entry points. Start by locating the WoW 3.3.5a loot-rule implementation and review how class, armor, attributes, armor penetration, and talent eligibility are represented. Done should mean the proposed need restrictions are implemented and verified for the listed class and item cases.

Written by the indexing model from the issue text.

Description

atm wow 3.3.5a loot rules on non-df are quite weak my idea is a way to tweak them, ie:

allow only need for for items usable by the class and for armors only the highest armor, ie plate for dk / paladin / warrior.
deny need to classes that doesn't uses certain atribute, ie don't allow need to dks or warriors to items with inteligence or druids with strengh.
deny need to classes that doesn't benefice from armor penetration, ie paladin.
deny need to items you don't have talents, ie tank items for priest.

Dominant language
C++
Stars
83
Forks
58
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TrinityCore/TrinityCoreCustomChanges

All issues in TrinityCore/TrinityCoreCustomChanges

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.