Fast Block Manipulation?

How are plugins able to set and remove blocks so quickly without locking the main thread? For example, on minecraftparty.com, the 'wool mix-up' game removes and adds backs all the different colors of wools without locking the main thread. How do they do it?

 

I don't know how many blocks you're planning to change, but depending on the server, you can easily change 500-750 blocks in some milliseconds.

If is something that really lock the main thread (~25k blocks or more), create a qeueue system.

Code:java

// this inside a repeating task (control the block quantity/delay to run)
thisRun = 0;
if (queue.hasNext() && thisRun < 1000) {
queue.next().setType(Material.WOOL);
thisRun++;
}

 

I have a pretty decent dedicated server.
I am using the following code to set the blocks.

Code:java

 
 
  public void restore(){
        for(Tile tile: tiles){
            tile.generate();
        }
  }
 
 
Tile class:
  public void generate(){
        for (Block set : blocks) {
            set.setType(Material.WOOL);
            set.setData((byte) c.getItemStack().getDurability());
        }
  }
 

There are 360 tiles in the tiles array, and 16 blocks in each blocks array
so in total I should be generating 5760 blocks.
It completely locks up the server thread for at least 5 seconds.

 

Try queueing for 400 blocks per second?

 

400 per second? Then it would take 14 seconds to change all the blocks. I need it to happen basically instantly. As I was saying, minecraftparty.com, the 'wool mix-up' game does this without little lag when changing all the blocks. and I don't think it's just because they have a godlike server

 

You change 5.100 blocks on a row. If you change less blocks in more runs, it'll be smoother and less lagging.
Try like... 200 blocks blocks per run, running each 7-13 ticks

Well, CPU makes a HUGE difference, your plugins either...

 

NerdsWBNerds My guess is that the 'wool mix-up game' sends fake block updates to Player's and keeps the information about the blocks in the plugin, or it just changes such a small amount that it wouldn't cause too much lag.

 

If you're going to be doing a lot of complexity within a method, you should make it asynchronous. Obviously bukkit functions remain in the main thread.


I've managed to set nearly a million blocks at once in ~700ms on a 2gb server with this.

 

Thanks, would this work with spigot since it's calling upon craftbukkit, or no?

If it sent fake block updates.

A. How would you do that.
B. Would people be able to fall through the fake updated air blocks?

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

NerdsWBNerds these forums don't provide support for spigot.

 

This isn't specifically for spigot. Developing a plugin usually isn't different for plugin, unless you get into the types of things @ZeusAllMity11 was talking about. And that might even work with Spigot, I'm not sure. If it doesn't then I'll go on the Spigot forums and ask specifically how to port that code to Spigot.

 

My solution is compatible with Craftbukkit.

 

But not Spigot (I don't know if there's some implementations of Craftbukkit in Spigot or something)
If not I'll go on the Spigot forums and ask them what would be the Spigot equivalent (if I can't find out myself)

 

Nearly everything that you can do on CraftBukkit will also work on Spigot because Spigot is a fork of CraftBukkit. If you are building against CraftBukkit and Spigot is throwing errors at you, you are using the wrong build. ZeusAllMighty11 's solution will work fine on Spigot if you use the right build.

I don't understand why everyone instantly lashes out at Spigot being the issue. I have never, ever had issues working with NMS classes building against CraftBukkit while running on the same version Spigot server.

 

Thank you!

The blocks are changing, but the client still has them rendered. They're gone upon relog. Any idea how to fix this?

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

NerdsWBNerds

Update the chunks and send them to the player