Old Aperture HEP Launcher Fires Dual Pellets

[LincoCompany00]

BEE2 Application Version

4.46.1

BEE2 Package Version

4.46.1

What operating system are you running on?

Windows 11

Description of the bug

While I was playtesting one of my maps, I found that the Old Aperture HEP launcher launches two HEPS instead of one. I've only tested it in 60's style, but I'm assuming it's the same for 50's and 70's.

Expected behavior

It should only fire one pellet, not two!

Steps to reproduce

1. Place a non-infinite HEP launcher in a map, with a cube button connecting to it (weighted probably works too)
2. Set "start enabled" to false.
3. Compile the map in 50's, 60's, or 70's style
4. Put an angled surface across from the launcher, as it's not always as obvious that there's more than one pellet until some catchers receive some.
5. have some catchers in the map, as every time a catcher receives a pellet from any source, the ones fired from the launcher seem to get more and more out of sync with each other— even if the catchers are activated by a pellet summoned with a console command.

Logs and Reports

Additional information

Please note that it might not be as obvious that there's more than one pellet fired from the launcher. I also had a cube button connecting to the launcher and a timer value of 15.

[Potato-Man1234]

That happens with HEP launchers on overgrown on a previous version