Uses of Interface
hm.zelha.particlesfx.util.ShapeDisplayMechanic

Packages that use ShapeDisplayMechanic

Package	Description
hm.zelha.particlesfx.shapers.parents
hm.zelha.particlesfx.util

Uses of ShapeDisplayMechanic in hm.zelha.particlesfx.shapers.parents

Fields in hm.zelha.particlesfx.shapers.parents with type parameters of type ShapeDisplayMechanic

Modifier and Type	Field	Description
protected final List<Pair<ShapeDisplayMechanic,ShapeDisplayMechanic.Phase>>	ParticleShaper.mechanics

Methods in hm.zelha.particlesfx.shapers.parents with parameters of type ShapeDisplayMechanic

Modifier and Type	Method	Description
void	ParticleShaper.addMechanic(ShapeDisplayMechanic.Phase phase, ShapeDisplayMechanic mechanic)
void	Shape.addMechanic(ShapeDisplayMechanic.Phase phase, ShapeDisplayMechanic mechanic)	Similar to Consumer in the case of phases ShapeDisplayMechanic.Phase.BEFORE_ROTATION and ShapeDisplayMechanic.Phase.AFTER_ROTATION the given mechanic will run before the location is modified to display the next particle, allowing you to modify the addition vector however you want, though doing so may be very volatile keep in mind that all changes to the given objects will be reflected in the display() method, and considering that the display() method often displays hundreds of particles, try to make sure the mechanic isn't very resource-intensive apply(Particle, Location, Vector, int)

Uses of ShapeDisplayMechanic in hm.zelha.particlesfx.util

Methods in hm.zelha.particlesfx.util with parameters of type ShapeDisplayMechanic

Modifier and Type	Method	Description
void	ParticleShapeCompound.addMechanic(ShapeDisplayMechanic.Phase phase, ShapeDisplayMechanic mechanic)