TrinityCore / TrinityCore/WowPacketParser

playerchoice_respons_reward

Open
#804 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
522
Forks
387
Avg merge
3d 6h
Merged PRs (30d)
4

Description

Playerchoice and playerchoice_response get filled but reward never maybe an issue with struct

Contributor guide

No contributing guide indexed for this repository

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

Start by locating the parser code for PlayerChoice and playerchoice_response, then inspect how their structures populate fields from packet data. Reproduce the issue with a relevant sniff or parser input and compare the reward field with the other populated values. Done means reward is populated correctly and the behavior is covered by the project's available validation or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.