Skip to content

Doom Desire & Future Sight Timers UI#2574

Merged
Zarel merged 6 commits intosmogon:masterfrom
mollup:timers
Mar 15, 2026
Merged

Doom Desire & Future Sight Timers UI#2574
Zarel merged 6 commits intosmogon:masterfrom
mollup:timers

Conversation

@mollup
Copy link
Contributor

@mollup mollup commented Dec 12, 2025

Future Sight and Doom Desire Timer UI

Added Future Sight and Doom Desire UI timers so that both users can easily see when damage will actually be dealt. Currently spawns in with 3 turns remaining when used, then ticks down to 2, then 1, then attacks.

Link to issue

Changes

battle.ts

Added Future Sight and Doom Desire as sideConditions on client side. Not affected by Court Change because courtchange in moves file on server side manually selects the sideConditions it affects. Also added them as -sidestart cases.

battle.css

Added an optional animation implementation for Future Sight and Doom Desire. The animation is currently unused, as it did not feel fully faithful to in-game behavior, but the underlying implementation is preserved for potential future use.

Example:

image

@Zarel Zarel merged commit 7df45ea into smogon:master Mar 15, 2026
1 check passed
@Zarel
Copy link
Member

Zarel commented Mar 15, 2026

Thanks!

@pyuk-bot
Copy link
Contributor

Won’t this break in doubles if there are future moves active against each slot on one side? It will also be weird in FFA, since it will always show the opposite side as being the target no matter who it actually targeted, which will also have issues if one Pokemon sets up multiple future attacks at once. In the current gen, I think starting in gen 7 with the advent of the info screen, the target of future moves is revealed via the info menu available at move selection, so a proper implementation of this should include extra data sent from the server.

@Zarel
Copy link
Member

Zarel commented Mar 15, 2026

It looked like the old one was implemented as a volatile, which was also wrong. Future Sight is properly a slot condition but I think this is probably better than no change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants