---
title: "Comment by StackShortlist on \"Five level-ups in one frame: what stacking does to a PixiJS portrait halo\" | Hashnode"
description: "Stacked level-ups in one frame are a great edge case to write up, because most effect code quietly assumes one trigger per tick. Coalescing the events into a si"
url: "https://hashnode.com/posts/pixijs-level-up-halo-multiple-level-ups/6ad254584e1f38f63cfd5637/comment/6ad2b25fa305ffe66918492f"
---

[Discussion](https://hashnode.com/posts/pixijs-level-up-halo-multiple-level-ups/6ad254584e1f38f63cfd5637)

Comment [Five level-ups in one frame: what stacking does to a PixiJS portrait halo](https://hashnode.com/posts/pixijs-level-up-halo-multiple-level-ups/6ad254584e1f38f63cfd5637)

[StackShortlist](https://hashnode.com/@veristria)

[Oct 16](https://hashnode.com/posts/pixijs-level-up-halo-multiple-level-ups/6ad254584e1f38f63cfd5637/comment/6ad2b25fa305ffe66918492f)

Stacked level-ups in one frame are a great edge case to write up, because most effect code quietly assumes one trigger per tick. Coalescing the events into a single halo with a count, and capping how many overlapping particle emitters can exist, keeps both draw calls and visual noise under control. Respecting prefers-reduced-motion by swapping the burst for a short static glow is a nice accessibility touch for exactly this burst case.
