#Aasync worldedit how to
#Aasync worldedit install
#Aasync worldedit update
#Aasync worldedit mods

When I disabled the blocks freeze function I managed to queue additional 20% blocks, (1 800 000 for each additional 500m of free ram).ĪsyncWorldEdit 2.x has lower BPS then in 1.x. After the queue reached 2 000 000 blocks the TPS started dropping because of the garbage collector.Īdding additional ram resulted in increase of the maximum number of queued blocks approximately by 1 500 000 blocks for each 500m of additional free ram. On a server that had 1g ram, approximately ~700m free, I managed to queue up to 2 500 000 blocks. Therefore I do not recommend to queue more then 500 000 blocks on a server that has 200m free ram. But after the queue reached 500 000 blocks TPS started to dropped drastically because of the garbage collector. On a minimum server (512m) free memory ~200m I managed to queue up to 1 000 000 blocks. Using the official spigot, only AWE and WE ware installed and there was 1 player on the server.

#Aasync worldedit how to

You can also use that thread for reference on how to configurate AsyncWorldEdit for you hardware specification.Īll tests ware done in a controlled environment. Recently a thread has been started on where you can show others how fast you can place blocks using AsyncWorldEdit. New loggers and new access control plugins are going to by added directly to BlocksHub plugin.

#Aasync worldedit install

This feature requires you to download, install and configure BlocksHub and then install any of the supported block loggers (access controllers). To enable block logging (or block access control) you need to enable it in AWE config. This is done using a special plugin called BlocksHub. The enables logging of blocks placed by WorldEdit and can enforce block access.

#Aasync worldedit update

Alternatively you can remove the permission node if you don't want to receive update information. To disable this feature set checkVersion to false in the config. This plugin does not provide auto update feature it only nags the server owner's when there's an update.

to enable blocks login and blocks access control download BlocksHub.

#Aasync worldedit mods

install AsyncWorldEdit into plugins folder ( do not put it into the mods folder!).install AsyncWorldEditInjector into mods folder ( do not put it into the plugins folder!).install WorldEdit forge into mods folder.Installation for cauldron (since AsyncWorldEdit 2.1.0) Use the jar that's for your PlotMe version! if you are using PlotMe and want to enable the PlotMeFix put AsyncWorldEdit-PlotMe* in your plugins folder.to enable blocks login and blocks access control download and install BlocksHub.For AsyncWorldEdit 2.x put the AsyncWorldEdit.jar and AsyncWorldEditInjector.jar into plugins.For AsyncWorldEdit 1.x put the AsyncWorldEdit.jar into plugins.If you are using WorldEdit 6.1.2+ you need to get AsyncWorldEdit 2.3.0 or later.If you are using WorldEdit 6.x you need to get AsyncWorldEdit 2.2.2 or earlier.

If you are using WorldEdit 5.x you need to get AsyncWorldEdit 1.x.If you want to have more features, want more frequent updates check out the AsyncWorldEdit Premium.

In addition to that if WorldEdit team releases a new feature, fixes a bug all you need to do is update WorldEdit and AWE will do its job as usual. So basically you get the same commands, same permissions and the same experience. There fore you have access to all the WorldEdit operations, and all those operations work exactly like in the original WorldEdit. AsyncWorldEdit is not a reimplementation of WorldEdit! It attaches the original WorldEdit API and WorldEdit classes and tries to fix the lags. The package size and how often the blocks are drawn are configurable in the config. All the block drawing is done in packages. This plugin has only one function: eliminate the lag caused by the WorldEdit! This is done by replacing the WorldEdits session with an special asynchronous one.