TrinityCore / TrinityCore/TrinityCoreCustomChanges

in core dbm

Open
#29 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description:

maybe a good idea can be a way to enable on screen warnings and co for people without addons.

TC rev. hash/commit:

4c0a8ad3b3f9

TDB version:

N/A

Operating system:

N/A

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.

Research direction

The issue only identifies “core dbm” and does not name files, tests, or a specific warning behavior. First clarify which on-screen warnings should be available without addons, then locate the relevant DBM-related core entry point and define how the result can be verified. Done means the agreed warnings work for users without addons and are covered by an appropriate verification path.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.