OneLiteFeatherNET / OneLiteFeatherNET/Voyager

Map transition polish: countdown timer, animated map-name title

Open
#134 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

beta gameplay P2
Dominant language
Java
Stars
0
Forks
0
Avg merge
2d 21h
Merged PRs (30d)
12

Description

Description

The transition between maps in a cup currently feels abrupt. Adding a pre-race countdown and an animated map-name title sequence makes the cup feel like a professional minigame.

Acceptance Criteria

  • Before each map starts, a 5-second countdown is displayed (5…4…3…2…1…GO!) as a title
  • Countdown title uses: large title = number, subtitle = map name
  • "GO!" title stays for 0.5s then clears
  • Between maps, a 3-second "inter-map" screen shows: map number (e.g., "Map 2/3"), map name, and current standings
  • All timings are configurable in the cup config JSON
  • Titles use MiniMessage formatting for color/gradient support

Technical Details

  • PreparationPhase handles the countdown — currently exists but may need enhancement
  • Inter-map screen happens in CupSystem between GamePhase end and next map load
  • Use Minestom TitlePacket with fadeIn, stay, fadeOut times

Dependencies

  • "Mid-cup standings display after each map" (Beta) for the standings portion

Estimate

S

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading PreparationPhase for the existing countdown, then inspect CupSystem where GamePhase ends and the next map loads. Review the cup config JSON and Minestom TitlePacket timing options, along with the dependent mid-cup standings issue. Done means configurable countdown and inter-map titles meet every listed timing, content, and MiniMessage requirement.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.