Fixed Bug: Number of particles removed by particle.kill_all

[baaz777]

Problem:
particle.kill_all always printed the fixed string particle.kill_all: cleared, so an operator clearing a suspected particle leak couldn't tell whether 0 or 40,000 particles were removed.

Change:
Read the particle count from ParticleSystem::GetParticles() before calling clear() and included it in the output.

Issue:
Fixes #14

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[lextpf]

Hi @baaz777,

Thanks for jumping in so quickly, having another pair of eyes on this is always appreciated! 😊
Your changes look good and you have my approval! I'll bypass SonarCloud, this failure is not due to your changes

If you'd like to dive in deeper as a contributer:

The project is a bit opaque about where assets live and it's a bit tricky to set up your own assets which means runtime testing can be quite cumbersome, if you'd like to test locally yourself here are two easy ways to get you up and running in case you want to be more hands-on for future issues:

What you might need	How to get it	Notes
Full pre-built game from your branch	➜ Add me on Discord (@lextpf).	Unzip anywhere and run the executable, includes a full experimental game save file as well.
Only the assets (if you want to build yourself)	➜ Add me on Discord (@lextpf).	After cloning the repo, drop the assets/ folder from this ZIP into the repo root, then build.

Let me know if you need support and we can arrange something, and thanks again for volunteering and helping improve Rift, you're always welcome to work on future issues! 👾

Alex

[baaz777]

no problem, i sent you a request on discord.