Default particle speed (extra) should be set to 0 instead of 1

[Privatech38]

Expected behavior

Particle speed should default to 0, NMS code for the particle command, with only a name and position argument, is:

Commands.argument("pos", Vec3Argument.vec3())
    .executes(
        context1 -> sendParticles(
            context1.getSource(),
            ParticleArgument.getParticle(context1, "name"),
            Vec3Argument.getVec3(context1, "pos"),
            Vec3.ZERO,
            0.0F,
            0,
            false,
            context1.getSource().getServer().getPlayerList().getPlayers()
        )
    )

Observed/Actual behavior

Spawning a particle with the API defaults the extra (speed) field to 1. paper-server code:

Paper/paper-server/src/main/java/org/bukkit/craftbukkit/CraftWorld.java

Lines 2166 to 2169 in 6fb36e3

	@Override
	public <T> void spawnParticle(Particle particle, double x, double y, double z, int count, double offsetX, double offsetY, double offsetZ, T data) {
	this.spawnParticle(particle, x, y, z, count, offsetX, offsetY, offsetZ, 1, data);
	}

and

Paper/paper-server/src/main/java/org/bukkit/craftbukkit/entity/CraftPlayer.java

Lines 3003 to 3006 in 6fb36e3

	@Override
	public <T> void spawnParticle(Particle particle, double x, double y, double z, int count, double offsetX, double offsetY, double offsetZ, T data) {
	this.spawnParticle(particle, x, y, z, count, offsetX, offsetY, offsetZ, 1, data);
	}

This results in some of the particles to appear "aggressive" shooting off into the distance.

Steps/models to reproduce

Spawn a particle affected by speed like FLAME or CLOUD

Plugin and Datapack List

/

Paper version

[21:10:34 INFO]: This server is running Paper version 1.21.8-3-main@6fb36e3 (2025-07-17T16:11:32Z) (Implementing API version 1.21.8-R0.1-SNAPSHOT)

Other

No response

[Owen1212055]

This has been a default for ages, sadly we cannot really change that behavior without breaking many plugins in the process.

[Privatech38]

I disagree, I highly doubt there are a lot of plugins that specifically use the default speed 1 and spawn particles like FLAME and use it as a feature.

[Owen1212055]

If there has been a behavior change in last few updates then this is valid, otherwise we can't really just change defaults just because you deem it not useful.

[Privatech38]

I won't argue with your decision, since it's ultimately your (or your teams'). However I would still like you to consider that this behavior is different than the one in vanilla and leads to unexpected results in some particles.

[electronicboy]

Speed has defaulted to 0 for the longest time, but, changing behavior in such a core part of the API mid release cycle is generally bleh, that's the sorta thing you slip into a bit of a larger release so that devs have time to test and mitigate any issues