[1.7.10] - setBlock Flags

[American2050]

Hello guys, I have a question about the flags and how to use them when using setBlock

 

It says most likely we want to use 2, but using 2 I have a problem. Lets say I set a lot of block to air, and next to some of the blocks I replaced there was lava, or maybe water. Well the problem I'm having is that using flag 2 the lava doesn't know that the block it not there anymore and as result it doesn't start flowing.

 

world.setBlock(x, y, z, Blocks.air, 0, 2)

 

When I use the flag 1 the blocks still showing, till I try to place something there, then it gets removed and what I placed take the space.

 

Then I see the function description says, "Flags can be added together" but I don't know how to do that.

 

How should I do it, and what flags should I use 1, 2 or 4, all of them?

 

[Draco18s]

1 + 2 = ?

2 + 4 = ?

[larsgerrits]

You probably want to use flag 3, which are flag 1 (block update) and flag 2 (notify clients).

[American2050]

Thanks you guys  I had no idea it worked like that...

 

I'll make that for all the blocks I'm adding to the world, and also, I found a setBlockToAir I guess I will just use that when it's only air what I'm changing...

 

Thanks a lot once again.

[Draco18s]

  On 5/11/2015 at 7:57 PM, American2050 said:

I'll make that for all the blocks I'm adding to the world, and also, I found a setBlockToAir I guess I will just use that when it's only air what I'm changing...

 

Which, if you look at it, is just a wrapper function for

world.setBlock(x, y, z, Blocks.air, 3)

[American2050]

  On 5/11/2015 at 8:03 PM, Draco18s said:

  Quote

I'll make that for all the blocks I'm adding to the world, and also, I found a setBlockToAir I guess I will just use that when it's only air what I'm changing...

 

Which, if you look at it, is just a wrapper function for

world.setBlock(x, y, z, Blocks.air, 3)

 

Thanks for the tip, I think I should get used to take a look more into the code itself to see how some things are done "behind the scenes"

[jabelar]

  On 5/13/2015 at 11:22 PM, American2050 said:

Thanks for the tip, I think I should get used to take a look more into the code itself to see how some things are done "behind the scenes"

 

I would go as far as to say you should always check the source for methods you're calling because sometimes they don't work like you might expect. In fact some are actually mis-named -- like the Entity#getLastAttacker() actually gets the last thing the entity attacked, not the last attacker of the entity (because the lastAttacked field is also mis-named). And over time there have been many methods that have gotten abandoned and aren't used like you might expect.

[Draco18s]

Also be highly skeptical of the Javadoc.  world.getWorldTime() calls provider.getWorldTime() which returns the private field totalWorldTime which has the comment "stores the time of day, 0-23999" which is false.

(Note, I may have misremembered the actual names, but the comment is the important part here.  The saved time is the total time and is not bounded to 24000 ticks.  One modder decided that the javadoc was correct and the implementation wrong, so for his mod he decided he would modulo the time down under 24k, save it back to the world time, and use it like that.  I had to discourage that idea).