Trying to spawn particles on the server side.

[kitsushadow]

How can i properly spawn particles on the server side for all players to see.

 

 

public void updateEntity() {

 

World world = this.getWorldObj();

int x = this.xCoord;

int y = this.yCoord;

int z = this.zCoord;

if(!world.isRemote){

forgeMaint(world,x,y,z);

heatIngot(world, x, y, z);

fireboxFuelDec(world, x, y, z,this.getStackInSlot(0), this.ticks);

fireboxFuelDec2(world, x, y, z,this.getStackInSlot(1), this.ticks);

if(isBurning==true){

System.out.println("Is Burning");

world.spawnParticle("fire",  (double)x+0.5f, (double)y+1.1f, (double)z+0.5f, 0.0D, 0.0D, 0.0D);

world.spawnParticle("flame", (double)x+0.5f, (double)y+1.1f, (double)z+0.5f, 0.0D, 0.0D, 0.0D);

world.spawnParticle("smoke", (double)x+0.5f, (double)y+1.1f, (double)z+0.5f, 0.0D, 0.0D, 0.0D);

}

}

}

 

 

Any suggestions would be excellent. Thank You

[coolAlias]

You technically can't spawn particles on the server, but you can either spawn them on the client (i.e. when the world IS remote) since all client players will have the tile entity also ticking on the client, or use Block#randomDisplayTick, which is what furnaces do.

[Ernio]

As my predecessor, to clear it up:

 

Particles are "special" entities that are for client ONLY.

You can spawn them only from client thread. To spawn them for all player - use Packets (SimpleNetworkWrapper), DataWatcher, or anything that can perform action (TileEntity, Block, whatever).

 

SNW tutorial:

http://www.minecraftforge.net/forum/index.php/topic,20135.0.html

[kitsushadow]

You technically can't spawn particles on the server, but you can either spawn them on the client (i.e. when the world IS remote) since all client players will have the tile entity also ticking on the client, or use Block#randomDisplayTick, which is what furnaces do.

 

I attempted the randomDisplayTick that the furnace uses with packet handleing as well. The issue I ran into was that all of the Blocks would turn on and off together. When i made a packet handler for x y z and passed those through only one of the blocks could ever produce particle effects.

 

Block randomDisplayTick

 

@Override

@SideOnly(Side.CLIENT)

public void randomDisplayTick(World world, int x, int y, int z, Random rand)

{

super.randomDisplayTick(world, x, y, z, random);

 

if(this.furnaceParts == true){

int l;

float f;

float f1;

float f2;

for (l = 0; l < 3; ++l)

{

f = (float)(locX+0.25) + (rand.nextFloat()/2);

f1 = (float)locY + rand.nextFloat() * 0.4F + 0.3F;

f2 = (float)(locZ+0.25) + (rand.nextFloat()/2);

world.spawnParticle("fire", (double)f, (double)f1, (double)f2, 0.0D, 0.0D, 0.0D);

world.spawnParticle("flame", (double)f, (double)f1, (double)f2, 0.0D, 0.0D, 0.0D);

//world.spawnParticle("smoke", (double)f, (double)f1, (double)f2, 0.0D, 0.0D, 0.0D);

}

 

}

if(this.coalParts == true){

int l;

float f;

float f1;

float f2;

for (l = 0; l < 3; ++l)

{

f = (float)(locX+0.25) + (rand.nextFloat()/2);

//f1 = (float)y + rand.nextFloat() * 0.4F + 0.3F;

f1 = locY+1.1f;

f2 = (float)(locZ+0.25) + (rand.nextFloat()/2);

world.spawnParticle("fire", (double)f, (double)f1, (double)f2, 0.0D, 0.0D, 0.0D);

world.spawnParticle("flame", (double)f, (double)f1, (double)f2, 0.0D, 0.0D, 0.0D);

world.spawnParticle("smoke", (double)f, (double)f1, (double)f2, 0.0D, 0.0D, 0.0D);

}

}

}

 

onBlockActivated where the packet is sent from

the tileEntity locX, locY, and locZ are supplied from the TileEntity

 

if(!world.isRemote){

if(player.inventory.getCurrentItem()!=null){

if((player.inventory.getCurrentItem().getItem()==Item.getItemFromBlock(Blocks.torch))||

(player.inventory.getCurrentItem().getItem()==Items.flint_and_steel)||

(player.inventory.getCurrentItem().getItem()==ModItems.fireBow)){

tileEnt.isBurning=true;

tileEnt.markForUpdate();

TargetPoint point = new TargetPoint(0, x, y, z, 10);

//Main.sNet.sendToAll(new MsgPacketOn(tileEnt.isBurning));

Main.sNet.sendToAllAround(new MsgPacketOn(tileEnt.isBurning), point );

if(tileEnt.getStackInSlot(1)!=null){

tileEnt.isOn=true;

Main.sNet.sendToAll(new MsgPacketBurning(tileEnt.isOn));

}

}

}

 

[Ernio]

1. Update your forge

 

2. randomDisplayTick runs from Block - there is only one BLock instance for given block - it will run for all the same way.

What you can ONLY do is to:

2.1. Use metadata of block in given x/y/z to save boolean if given block should be "burning"

2.2. Pull that boolean (isBurning) from TileEntity at given x/y/z

 

3. this.furnaceParts and this.coalParts == true is wrong.

Again - there is only ONE Block. Anything in Block class (this) will be shared for all blocks of this type.

[kitsushadow]

1. Update your forge

 

2. randomDisplayTick runs from Block - there is only one BLock instance for given block - it will run for all the same way.

What you can ONLY do is to:

2.1. Use metadata of block in given x/y/z to save boolean if given block should be "burning"

2.2. Pull that boolean (isBurning) from TileEntity at given x/y/z

 

3. this.furnaceParts and this.coalParts == true is wrong.

Again - there is only ONE Block. Anything in Block class (this) will be shared for all blocks of this type.

 

i use metadata for rotation. will that be a problem?

[coolAlias]

Metadata can represent up to 16 states, but when you start combining states you quickly lose that versatility. Since you already have a TileEntity and it already knows if it is burning or not, why not just use that?

TileEntity te = world.getTileEntity(x, y, z);
if (te instanceof MyTileEntity) {
  boolean isBurning = ((MyTileEntity) te).isBurning;
}

Just make sure that the client side also knows about the state - you can do so either by using your custom packets or marking the block for an update if you have overridden getDescriptionPacket.

[jabelar]

You technically can't spawn particles on the server, but you can either spawn them on the client (i.e. when the world IS remote) since all client players will have the tile entity also ticking on the client, or use Block#randomDisplayTick, which is what furnaces do.

 

To clear up some confusion on this.

 

If you're trying to spawn vanilla particles, you DO "initiate" the spawn on the server. This works even though EntityFX is client side only class because the spawn particle method doesn't actually use the EntityFX class (which is not available to the server) but instead has a mapping to a string particle name. When you do this, the server will take care of notifying all clients, each of which will create the actual instance of the EntityFX class. So I would still sort of call this "spawn on the server" since you initiate it on server side.

 

If you're trying to spawn custom particles, you should still initiate on the server, but you have to implement the packets yourself to tell each client to instantiate the EntityFX.

 

The point of saying "spawn particles on the server" is that you want your code to initiate the process on server side only, and then the server should take care (either using built-in sync for vanilla particles, or using custom packets for custom particles) of syncing the clients.

[coolAlias]

If you're trying to spawn vanilla particles, you DO "initiate" the spawn on the server.

No, you don't. World#spawnParticle calls IWorldAccess#spawnParticle, and the server implementation (in WorldManager) literally does nothing. If you try to spawn them on the server, nothing will happen.

 

You either send a packet or spawn them directly on the client side, depending on the situation.

 

There is IWorldAccess#playAuxSFX, and THIS one actually sends a packet to all around when called on the server, so you can play sound, spawn particles, or whatever else on the server as dictated by the specific SFX.

[BoonieQuafter-CrAfTeR]

PARTCULES ARE CLIENT SLIDE RIGHT ERINO?

[jabelar]

If you're trying to spawn vanilla particles, you DO "initiate" the spawn on the server.

No, you don't. World#spawnParticle calls IWorldAccess#spawnParticle, and the server implementation (in WorldManager) literally does nothing. If you try to spawn them on the server, nothing will happen.

 

You either send a packet or spawn them directly on the client side, depending on the situation.

 

You misunderstood my statement. I said you "initiate" the spawn. That does not mean you use any world spawn method. I mean you use your own code to send a packet to all the clients.

 

This is the confusion -- the impetus for spawning particles should be on the server. The actual instance of the particles is only created on the clients.

 

The problem is the terminology "spawn". Spawn doesn't mean create an instance, it means to start the process to create something (whatever that means for the case involved). For example, you could say that placing a block is "spawning" a block -- even though no new instance is created at all. In the case of actual entities, you actually instantiate them on the server. In the case of particles you initiate the spawn on server but instantiate on the clients, and in case of blocks you initiate the spawn on the server and it is never instantiated in the Java sense. All of that is spawning, and all of those cases start on the server.

[coolAlias]

You misunderstood my statement. I said you "initiate" the spawn. That does not mean you use any world spawn method. I mean you use your own code to send a packet to all the clients.

 

This is the confusion -- the impetus for spawning particles should be on the server. The actual instance of the particles is only created on the clients.

There is no reason that particle spawning must be initiated on the server - it is one of the few cases where it is perfectly fine to do it only on the client. The times when you do initiate it on the server are typically when a. the trigger happens there, such as when a villager is struck, or b. you want the particles visible to all players and it is not run in a method that happens consistently client side.

 

Things like Block#randomDisplayTick or any update tick method that happens on the client (such as for spawning critical particles for the EntityArrow) are perfectly valid places to initiate particle spawning and need never go through the server.