TrinityCore / TrinityCore/TrinityCoreCustomChanges
CFBG system is not working properly
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 83
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
Description:
FIRST ISSUE IS : cfbg after compilation looks like it works properly, but ingame when you run the battleground, it connects all players to one team and the other team is empty. (for example 2 alliance players join bg and 2 horde players join bg, now who first clicks on enter battleground, if horde player changes it to alliance player and puts it in the team alliance, then all players put it in the alliance team, if he gives the first enter battleground alliance player, then it turns him into a horde player and everyone is in the horde team.
SECOND ISSUE IS : when the battleground starts, it can no longer be joined, it does not send an invitation to the ongoing battleground.
Current behaviour:
no crash nothing happens, everything looks like it works well.
Expected behaviour:
cfbg should work as a balance system, it should assign one player to one team, another to another team, and gradually fill bg to full. and you should definitely join the ongoing battleground.
Steps to reproduce the problem:
- Compile Core
- Set up min players for battleground start in my case 4 players for WSG
- Run Server
- Create 6 Accounts
- Log ingame and Join WSG battleground
- Enter the battleground and check the system as the player connects
Branch(es):
Writing server debug on console will return the best results for reporting bugs (3.3.5a for now)
3.3.5, CFBG or both
TC rev. hash/commit:
TrinityCore rev. 2302a5bc4451+ 2021-08-30 00:48:59 +0000 (master branch) (Win64, RelWithDebInfo, Static)
TDB version: TDB 335.21081
Operating system: Win64
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the CFBG behavior with the stated four-player WSG setup, six accounts, and server debug output, focusing on the battleground entry flow. Done means players are assigned to both teams as they enter and invitations can still be sent after the battleground starts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100