-
Notifications
You must be signed in to change notification settings - Fork 4
Home
This plugin has only one function: eliminate the lag caused by the WorldEdit! This is done by hooking into WorldEdit inners classes and replacing some of them with specially prepared classes. All WorldEdit operations are divided into two stages: preparation and block placing. The preparation phase is done in async thread and calculates the list of blocks that need to be changed. All the block placing in stage two is done in packages. The package size and how often the blocks are drawn are configurable in the config. AsyncWorldEdit is not a reimplementation of WorldEdit! It attaches the original WorldEdit API and WorldEdit classes and tries to fix the lags. There fore you have access to all the WorldEdit operations, and all those operations work exactly like in the original WorldEdit. So basically you get the same commands, same permissions and the same experience. 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.
The AsyncWorldEdit Premium is a direct continuation of the original AsyncWorldEdit. It contains additional functions and improvements and it is going to be updated regularly.
TODO: Record new tutorial
To install the plugin simply follow those steps:
- download and install WorldEdit
- buy the plugin on spigotmc.org
- download the plugin
- to enable blocks loggin and blocks access control download BlocksHub
- if you are using PlotMe older then 0.17 and want to enable the PlotMeFix put AsyncWorldEdit-PlotMe* in your plugins folder. Use the jar that's for your PlotMe version!
- if you want to use additional progress display put the appropriate bridge for your progress display plugin
- restart server
- edit the config file
- restart server or do /AWE reload
To install the plugin simply follow those steps:
- download WorldEdit and WorldEdit Forge
- install WorldEdit into plugins folder
- install WorldEdit forge into mods folder
- download AsyncWorldEdit
- install AsyncWorldEditInjector into mods folder (do not put it into the plugins folder!)
- install AsyncWorldEdit into plugins folder (do not put it into the mods folder!)
- Follow the installation instruction from the regular version.
The premium version of AsyncWorldEdit is a direct continuation of AsyncWorldEdit. In addition to all the features that you can find in AsyncWorldEdit you get:
- Better memory management,
- Automatic configuration update,
- No more holes if your player reaches exceeds the maximum number of queued blocks,
- Fixed some legacy bugs (missing injector detection, plugin unload, ...)
- New commands for schematics:
- schematic information
- place schematic directly without the usage of clipboard
- Direct chunk API (Edit millions of blocks in seconds). Supported commands:
- copy/paste blocks from and to the clipboard
- supports entities riding other entities
- copy one piece of world to other location
- set blocks
- Continuous support and plugin update ;)
This plugin does not provide auto update feature it only nags the server owner's when there's an update. To disable this feature set checkVersion to false in the config. Alternatively you can remove the AWE.admin.version permission node if you don't want to receive update information.
This version of the plugin contains a new super fast world editing feature. It is based on direct chunk data access. It allows you to copy large pieces of the map instantly. Currently the Direct Chunk API supports Spigot 1.8R3 API (Spigot 1.8.7). Support for additional versions will be added in future versions.
Warning: Currently the Direct Chunk API does not support BlocksHub.
The enables logging of blocks placed by WorldEdit and can enforce block access. This is done using a special plugin called BlocksHub. To enable block logging (or block access control) you need to enable it in AWE config. This feature requires you to download, install and configure BlocksHub and then install any of the supported block loggers (access controllers).
New loggers and new access control plugins are going to by added directly to BlocksHub plugin.
WARNING: The Direct Chunk API currently does not support BlocksHub.
#How many blocks can I queue? All tests ware done in a controlled environment. Using the official spigot, only AWE and WE ware installed and there was 1 player on the server. The AWE config was not changed.
On a minimum server (512m) free memory ~200m I managed to queue up to 1 000 000 blocks. But after the queue reached 500 000 blocks TPS started to dropped drastically because of the garbage collector. Therefore I do not recommend to queue more then 500 000 blocks on a server that has 200m free ram.
On a server that had 1g ram, approximately ~700m free, I managed to queue up to 2 500 000 blocks. After the queue reached 2 000 000 blocks the TPS started dropping because of the garbage collector.
Adding 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. When I disabled the blocks freeze function I managed to queue additional 20% blocks, (1 800 000 for each additional 500m of free ram).
If a plugin stopped working after installing AsyncWorldEdit please contact me. I'll try to help.
This plugin depends on:
BlocksHub - block login and blocks access
Other optional dependencies:
Progress display plugins:
- ActionBarAPI
- BarAPI
- BountifulAPI
- TitleManager
- WelcomeTitle
- ActionMessager
This plugin uses MCStats to gather statistics. It gathers only the standard stats gathered for most of MCStat's enabled plugins (for example: OS, Java version, CPU, country, plugin and server version). For details what exactly is gathered click on the graph below. To disable the stats you need to disable stats gathering for MCStats (set opt-out to true in plugins/PluginMetrics/config.yml). This disables all the stats gathering for all plugins that use the default MCStats.
Thank you for using this plugin.

