Strange timer between spellcards in Extra stage (HSiFS, WBaWC and UM)
In Hidden Star in Four Seasons, when 鼓舞「パワフルチアーズ」 Drum Dance "Powerful Cheers" ends, the timer will suddenly start counting from 49 downwards. It counts until 47 then it resets to 49 again when 狂舞「クレイジーバックダンス」 Mad Dance "Crazy Backup Dance" begins.
And when 狂舞「クレイジーバックダンス」 Mad Dance "Crazy Backup Dance" ends, the timer will suddenly start counting again from 49 until 47 and will reset to 59 when 弾舞「二つ目の台風」 Bullet Dance "Two-Eyed Typhoon" begins.
In Wily Beast and Weakest Creature, when 血戦「血の分水嶺」 Bloody Battle "Watershed of Blood" ends, the timer will suddenly start counting from 39 downwards. It counts until 37 then it resets to 39 again when 血戦「獄界視線」 Bloody Battle "Hell Realm Sight-Line" begins.
Similarly, when 血戦「獄界視線」 Bloody Battle "Hell Realm Sight-Line" ends, the timer will suddenly start counting again from 39 until 37 and resets back to 39 when 血戦「全霊鬼渡り」 Bloody Battle "Highly Spirited Oniwatari" begins.
In Unconnected Marketeers, when 狐符「フォックスワインダー」 Fox Sign "Fox Winder" ends the timer will start counting from 39 to 37 and will suddenly change to 59 when 管狐「シリンダーフォックス」 Kuda-gitsune "Cylinder Fox" begins.
When 管狐「シリンダーフォックス」 Kuda-gitsune "Cylinder Fox" ends, the timer will again count from 39 to 37 and shift to 59 when 星狐「天狐龍星の舞」 Stellar Fox "Dance of Heavenly Foxes and Dragon Stars" starts.
Curiously enough, Doremy in Legacy of Lunatic Kingdom seems unaffected by this. When a spellcard ends, the old timer remains on screen, stopped, until the next spellcard begins. Then the duration is resetted to match the time of the spell that has come.
There is also an oddity with the timer during extra stage midboss of Double Dealing Character, but that is presented in another post, since it's a bit different.
Please note that the seconds mentioned in this post are the main values seen on screen (for example, when it says "49", it could be very well "49.99", but I was not sure if it was indeed 49.99 or 50.00 and due to the frame loss of the video the 50 is not visible). I know it's not exactly the same thing, but the purpose of this post is to showcase that there is something wrong with the timer. For accurate seconds, you can look into the code yourself.