TrinityCore / TrinityCore/TrinityCore

No quest greeting found error for multiple NPCs

Open
#20,705 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Branch-master Priority-Cosmetic
Dominant language
C++
Stars
10.8k
Forks
6.4k
Avg merge
3d 16m
Merged PRs (30d)
6

Description

Description: No quest greeting found for multiple NPCs in a new install.

Current behaviour:

On a fresh build and install of TDB, I am experiencing an error where after completing a quest for an NPC (who offers a follow up quest), the second quest appears to be auto-accepted (it is shown in the quest log).

In the worldserver I see the following message: Guid: GUID Full: 0x20000400002FE5000000000000000028 Type: Creature Entry: 49044 Low: 40 - No quest greeting found. Server.log attached.

The quest works correctly, but the quest greeting is not shown.

Expected behaviour: Quest greeting should be shown, allowing quest to be accepted / declined.

Steps to reproduce the problem:

  1. Create Undead new character
  2. Accept "Fresh from the grave"
  3. Walk to hand in NPC
  4. Right click to hand-in
  5. Quest greeting is not shown, new quest is added to log

Branch(es): master

TC rev. hash/commit: TrinityCore rev. b8dc4df22098 2017-10-21 00:28:57 +0200 (master branch) (Win64, RelWithDebInfo, Static) (worldserver-daemon)

TDB version: TDB_full_720.00_2017_04_18

Operating system: Windows 10 x64

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

Reproduce the flow with a new Undead character using the listed quest steps, then inspect the worldserver output and attached server.log for the missing greeting. Trace the NPC's quest hand-in and follow-up quest behavior; done means the greeting appears and the player can accept or decline the new quest.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
game-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.