OneLiteFeatherNET / OneLiteFeatherNET/Voyager
Particle effects polish: ring glow, boost trail, finish fireworks
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 0
- Forks
- 0
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 12
Description
Description
Visual feedback makes game events feel satisfying. This ticket covers particle effects for the three highest-impact moments: ring borders glowing as you approach, a boost activation trail, and a finish-line firework burst.
Acceptance Criteria
- Ring glow: a ring emits
CRITorEND_RODparticles along its perimeter when a player is within 8 blocks, fading out as they move away - Boost trail: for 1 second after boost activation,
FLAMEparticles are emitted behind the player every 2 ticks - Finish fireworks: on crossing the finish line, 3 firework particle bursts (
FIREWORK) erupt at the player's position - Particles are per-player (only visible to the player triggering them) where possible to avoid visual clutter for others
- Particle rendering has a distance cutoff to avoid unnecessary packet spam to far-away players
Technical Details
- Use Minestom
ParticlePacketAPI - Ring glow scheduler runs in
CollisionSystemwhen proximity detected - Boost trail uses a countdown component (
BoostTrailComponent) decremented each tick
Dependencies
- None (purely additive)
Estimate
M
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the Minestom ParticlePacket API and tracing the proximity handling in CollisionSystem. Then inspect how boost activation and the BoostTrailComponent countdown are represented. Done means implementing the ring glow, one-second boost trail, and three finish fireworks with per-player visibility where possible and distance-based cutoff behavior.
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