Changes

22 bytes removed ,  18:11, 20 December 2020
m
Text replacement - "{{Colored box|title=Important|content=" to "{{Tip/Important|"
Line 44: Line 44:  
An <code>IParticleFactory</code> must be attached to a <code>ParticleType</code> using <code>ParticleManager#registerFactory</code>. This should be called during <code>ParticleFactoryRegisterEvent</code> on the mod event bus.
 
An <code>IParticleFactory</code> must be attached to a <code>ParticleType</code> using <code>ParticleManager#registerFactory</code>. This should be called during <code>ParticleFactoryRegisterEvent</code> on the mod event bus.
   −
{{Colored box|title=Important|content=<code>IParticleFactory</code> is only present on the client, so the event needs to be isolated via <code>DistExecutor</code> or some other method.}}
+
{{Tip/Important|<code>IParticleFactory</code> is only present on the client, so the event needs to be isolated via <code>DistExecutor</code> or some other method.}}
       
== Spawning Particles ==
 
== Spawning Particles ==
 
Particles can be spawned from a world instance. Each side, however, has a specific way of calling them. The <code>ClientWorld</code> can call either <code>addParticle</code> or <code>addOptionalParticle</code>. The <code>ServerWorld</code> must call <code>spawnParticle</code> as it sends a packet to the client world to call one of the other two methods. Calling the two <code>ClientWorld</code> methods on the server will result in nothing happening.
 
Particles can be spawned from a world instance. Each side, however, has a specific way of calling them. The <code>ClientWorld</code> can call either <code>addParticle</code> or <code>addOptionalParticle</code>. The <code>ServerWorld</code> must call <code>spawnParticle</code> as it sends a packet to the client world to call one of the other two methods. Calling the two <code>ClientWorld</code> methods on the server will result in nothing happening.
297

edits