Nikola Boss Cooldown and Rebattle Confirmation

[Kadajblade]

Hello,

I just had a misfortune when rebattle Nikola boss.

This is what happens;

I noticed that Nikola had no cooldown shown in the dialogue after defeat. Later, I asked on discord support and staff told me Nikola has 21 days cd.

After few weeks, I went to Nikola to check if he is up to battle. Without any confirmation like any other bosses "Are you ready?" "Yes/No" choice, Nikola just straight battle me.

I lost and have to wait another 21 days.

I had no team preparation because I check the cooldown after headbutting trees in Unknown Place.

So it just bunch of sync and false swiper pokes on my team.

This is really upset me. But, it already happened so I let it go.

 

What I wish that staff may fix the cooldown dialogue and rebattle confirmation, so that in the future there won't be any players experience this misfortune like me.

 

I hope you consider this report.

Thank you. :Smile:

[Neroli]

- Moved in proper forum -

[Naero]

Hello, and thank you for the report. :)

 

Apologies for any inconveniences caused by this blip. While you do seem to understand that Nikola's rechallengeability is not compensable, I do want to pledge assurance that these blips will not be recurrent moving into the future, as I have fixed it systemically.

 

There were multiple omissions on our part that have possibilized this; I will note them below.

 

Firstly, I have added a confirmatory prompt on Nikola's dialogue, meaning that he will ask you to confirm your readiness for challenging you before proceedingly initializing the battle; this allows you to ascertain Nikola's availability by speaking to him without any initiability on the battle script's part.

 

Secondly and lastly, if you wish to do more than a binary check on Nikola's readiness, you can now do a quantitative check by speaking to any of the all-encompassing cooldown-timers available, as I have just incorporated Nikola's timer into the check. Because the domain of his boss post (Trainer's Valley) is categorized as an expansionary area to Kanto, I have subsumed his check under all Kanto checks—for those that need that referential pointer.

 

Apologies again for any inconveniences this has caused on you, and I thank you on behalf of the staff for understanding and dutifully reporting this.