Area cloud effect does not behave like vanilla

[IvanCraft623]

Eg: In this implementation the cloud lasts only about 15 seconds, when in fact it should last about 30 seconds.

I have described some of these behaviors in:
pmmp/PocketMine-MP#5276 (comment)

[JustTalDevelops]

In this implementation the cloud lasts only about 15 seconds, when in fact it should last about 30 seconds.

Where did you get this from? The duration is always set to 30 seconds.

dragonfly/server/entity/area_effect_cloud.go

Line 36 in 967faf1

return NewAreaEffectCloudWith(pos, t, time.Second*30, time.Second*2, 0, 3.0, -0.5, -0.005)

[JustTalDevelops]

Yeah, I don't think this issue is valid — the logic seems to match up with the PR you linked. Is there anything in specific that is incorrect based off of vanilla, aside from the duration (which also is correct by the looks of it)?

[IvanCraft623]

Where did you get this from? The duration is always set to 30 seconds.

Did you play-tested it?

dragonfly_area_effect_cloud_duration.mp4

[IvanCraft623]

Is there anything in specific that is incorrect based off of vanilla, aside from the duration (which also is correct by the looks of it)?

• Area effect clouds only trigger updates every five tick, it should be 10.
• If the potion effect is instantaneous ReapplicationDelay is must be set to 0 (Actualy it would be applied every 10 ticks due to the above mentioned)

This information is obtained through play-tests and analysis of the NBT in vanilla.

[IvanCraft623]

About duration after debugging I found that the problem was on the client side, because it requires certain metadata to calculate the radius itself.

AREA_EFFECT_CLOUD_RADIUS => (float) Initial radius
AREA_EFFECT_CLOUD_SPAWN_TIME => (int) world time when it spawned
AREA_EFFECT_CLOUD_RADIUS_PER_TICK => (float) radiusGrowth
AREA_EFFECT_CLOUD_RADIUS_CHANGE_ON_PICKUP => (float) radiusOnUse
AREA_EFFECT_CLOUD_PICKUP_COUNT => (int) Times it has been pick up

(It is likely that their names do not match because they were obtained from pocketmine)

[JustTalDevelops]

I believe a lot of this can actually be avoided @IvanCraft623 by disabling the client-side behaviour of the cloud. Geyser does this, actually - see https://github.com/GeyserMC/Geyser/blob/3d66d2790f3a03ca8bafa7ce1cc6429ad9ab7a18/core/src/main/java/org/geysermc/geyser/entity/type/AreaEffectCloudEntity.java#L53.