or want to bypass the 5 second suicide cooldown.

Seems that should just be the default native behaviour here - it likely wasn't known what the boolean was for when this was added.

What's game support like for explode?

ZPS Supports exploding of models with their own gibs even and also requires the force parameter to be set to true to avoid the delay.

Seems that should just be the default native behaviour here - it likely wasn't known what the boolean was for when this was added.

It is weird that a native called "ForceSomething" isn't forcing something by default indeed. I don't know if changing the force default value to true would cause problems in some games now that it's been off for so long, but I'm inclined to try.

I don't think we should even expose force, just use true internally.

I don't think we should even expose force, just use true internally.

I'd agree if this native wasn't around for many years already. This might cause unexpected behavior for old plugins that expect the cooldown to be present. It's not likely many of them exist, but it's a possibility.

KickClient was expanded because it (well documented) crashed, RemoveEdict is still a nightmare in-frame where it's simply not safe. The Force* on these is a wart, I think defaulting these to safe is the appropriate way forward.

@peace-maker @asherkin I've set the force param to true by default. Is this good to go?

KickClient was expanded because it (well documented) crashed, RemoveEdict is still a nightmare in-frame where it's simply not safe. The Force* on these is a wart, I think defaulting these to safe is the appropriate way forward.

The force parameter isn't removing entities or edicts when they shouldn't be. The game just prevents spamming CommitSuicide for some reason and ignores future calls for 5 seconds after the last call. Plugins should be able to override this.

Can this be backported / included in the 1.11 builds?