Incorrect "abandoned" status

[Drago The Dragon]

Today I was doing dual dating to check Bryce's BBQ special interaction. I started with Adine so I had to go with 3-3. So at that point who I choose to date now decides who I'll be able to go with at chapter 5 and who will be marked as abandoned.
I went with Adine to fastival(4th date) and afterwards the status screen really surprised me because bryce was set as "good" but I couldn't date him (so just as it should be) and Adine was set as abandoned...4 dates, abandoned.
I proceeded to chapter 5 and I could go with Adine just as it should be, though she was still Abandoned at the status screen.

So things work properly but status screen descritions are wrong.

[JeffMakesGames]

So after her 4th scene concluded, her status said Abandoned?

I am looking over that scene's code and can't seem to spot anything that would result in that. I can only see her either being Impressed or Good.

[Drago The Dragon]

Exactly this happened, and Bryce's was still "good". Reloading save from before 4th scene and doing it again wasn't changing this. But I'll give it a quick check once again, maybe after restarting the game something changed.

[Drago The Dragon]

Nope, it's still like that
https://steamuserimages-a.akamaihd.net/ugc/861731682090452635/2A4C6102468E872539B0D19D7CFFE76710422263/

But chapter 5 works properly and I can see fireworks either with her or alone or everyone despite this status.

[M]

I investigated and found out this happens only in the specific case you experienced, meaning:

Going for Bryce and Adine at the same time and then picking Adine as 4th scene.

In similar cases the script is supposed to set the character you don't pick for the 4th scene as abandoned and won't let you play their 4th scene, and this works properly in every other case except this one, where it mistakenly set Adine as abandoned instead of Bryce.

As you say, just changing the status doesn't prevent you from playing her ending, though.

In any case, thanks for bringing this to our attention. We'll fix it in the next patch.