• Check out the relaunch of our general collection, with classic designs and new ones by our very own Pissog!

Needs Triage Bug Report - Unsure

What type of bug are you reporting? Unsure

What is the bug?
Active pokemon bool marked as true in team preview:

Running a bot, created a team (ignore the mons and sets), in team preview, the |request| message is correct but theres an active pokemon ("active":true) when there shouldn't be any. This confused my bot which is not that much the issue, but does look like unexpected behaviour as there should not be any active mon

JSON:
|request|{"teamPreview":true,"side":{"name":"Indychat","id":"p2","pokemon":[{"ident":"p2: Torchic","details":"Torchic","condition":"231/231","active":true,"stats":{"atk":156,"def":116,"spa":176,"spd":136,"spe":126},"moves":["fireblast","rockslide","swordsdance","batonpass"],"baseAbility":"speedboost","item":"","pokeball":"pokeball","ability":"speedboost","commanding":false,"reviving":false,"teraType":"Fire","terastallized":""},{"ident":"p2: Shellder","details":"Shellder","condition":"201/201","active":false,"stats":{"atk":166,"def":236,"spa":126,"spd":86,"spe":116},"moves":["rockblast","iciclespear","razorshell","shellsmash"],"baseAbility":"skilllink","item":"","pokeball":"pokeball","ability":"skilllink","commanding":false,"reviving":false,"teraType":"Water","terastallized":""},{"ident":"p2: Darumaka","details":"Darumaka-Galar","condition":"281/281","active":false,"stats":{"atk":216,"def":126,"spa":66,"spd":126,"spe":136},"moves":["firepunch","focuspunch","zenheadbutt","uturn"],"baseAbility":"hustle","item":"","pokeball":"pokeball","ability":"hustle","commanding":false,"reviving":false,"teraType":"Ice","terastallized":""}]},"rqid":3}

Are you able to replicate it? If so, how?
Make a bot or just debug the |request| command during team preview. Happened to both players. Confirm a pokemon on "side" is active
 
This isn't really a bug, more of a design choice (even if a dumb choice). The current logic simply sets the first Pokémon as active, or the first two in doubles, even if it is during teampreview or if the Pokémon has fainted.

It would be an easy fix, I just don't know if it is desirable.
 
This isn't really a bug, more of a design choice (even if a dumb choice). The current logic simply sets the first Pokémon as active, or the first two in doubles, even if it is during teampreview or if the Pokémon has fainted.

It would be an easy fix, I just don't know if it is desirable.
Fair enough! Got to say it was a minor problem

It did make my bot crash because it was looking for more info about the "active" mon but that was a skill issue on my side lol

It just smelled like undesired/incorrect behaviour which is normally not appreciated in software
 
Back
Top