Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Defeats from some Mystery Encounters are not displayed in Run History correctly #4706

Open
2 of 3 tasks
frutescens opened this issue Oct 22, 2024 · 2 comments
Open
2 of 3 tasks
Labels
Mystery Encounter Mystery Encounters and related work P3 Bug Non gameplay affecting bug. typos, graphical issues, or other minor incorrect interactions. UI/UX User interface/-experience related

Comments

@frutescens
Copy link
Collaborator

frutescens commented Oct 22, 2024

Describe the bug

Defeats from some Mystery Encounters are not parsed correctly by the Run History UI. This issue looks through all 22 original Mystery Encounters and checks if their lose conditions are correctly parsed by the UI currently or not.

Affected Mystery Encounters

Reproduction

To reproduce this bug, please refer to the labeled session data attached.

Expected behavior

The trainer + trainer's team / wild Pokemon that defeated the player.

Screenshots / Videos

No response

Session export file

No response

User data export file

No response

Additional context

No response

@frutescens frutescens added UI/UX User interface/-experience related Mystery Encounter Mystery Encounters and related work Triage The issue needs triage labels Oct 22, 2024
@frutescens
Copy link
Collaborator Author

frutescens commented Oct 22, 2024

Mysterious Challenges

Status: Broken
Run History File -> mysteriousChallenges.txt

Mysterious Chest

Status: Broken
Notes: Loss occurs when player rolls the bad result with only a single valid Pokemon in the team
mysteriousChest.txt

@Snailman11
Copy link
Collaborator

Link to Discord's Bug Report (Run history trainer not showing up)
https://discord.com/channels/1125469663833370665/1298383872358092872
-Bug Type Superfan

@Snailman11 Snailman11 added P3 Bug Non gameplay affecting bug. typos, graphical issues, or other minor incorrect interactions. and removed Triage The issue needs triage labels Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Mystery Encounter Mystery Encounters and related work P3 Bug Non gameplay affecting bug. typos, graphical issues, or other minor incorrect interactions. UI/UX User interface/-experience related
Projects
Status: Ready
Development

No branches or pull requests

2 participants