Removed DIRECTION and POTION_EFFECT_TYPE options due to them being legacy
Added OPACITY option to support ParticleTypes.ENTITY_EFFECT (it uses ARGB int as color, so it's represented as COLOR and OPACITY options)
Added DESTINATION option to support ParticleTypes.VIBRATION
Made ITEM_STACK_SNAPSHOT option to be explicitly not empty because minecraft throws exception on empty itemstack anyway
Updated options description
PositionSource:
Exposed minecraft interface (gabizou said it's fine to expose it)
Can be reference to Entity with some vertical offset or reference to BlockPos (it's packed into vibration particle and sent to client)
If made of entity, vibration particles will chase entity
Probably not the best name because it sounds very similar with our Locatable but I can't come up with good name (maybe something like ResolvablePosition, idk)
The only method it could have is Optional<Vector3d> position(World) (mirrored from original PositionSource) but I'm not sure if it should be exposed
SpongeAPI | Sponge
ParticleOptions:
DIRECTION
andPOTION_EFFECT_TYPE
options due to them being legacyOPACITY
option to supportParticleTypes.ENTITY_EFFECT
(it uses ARGB int as color, so it's represented asCOLOR
andOPACITY
options)DESTINATION
option to supportParticleTypes.VIBRATION
ITEM_STACK_SNAPSHOT
option to be explicitly not empty because minecraft throws exception on empty itemstack anywayPositionSource:
Entity
with some vertical offset or reference toBlockPos
(it's packed into vibration particle and sent to client)Locatable
but I can't come up with good name (maybe something likeResolvablePosition
, idk)Optional<Vector3d> position(World)
(mirrored from originalPositionSource
) but I'm not sure if it should be exposed