Updater‐Block

Overview

Our MissileWars plugin uses WorldEdit or FastAsyncWorldEdit ("FAWE") on your server to place the Missile schematics. While WorldEdit works synchronously, FAWE is asynchronous (and therefore more performant). That's why the Missiles don't get a block update with the schematic paste on FAWE and therefore don't fly by themselves.

As a solution for this, the Missiles need a temporary "Updater-Block" (or "Starter-Block" / "Replacer-Block" / "Temp-Block") that automatically receives a block update after the paste and then is removing from the missile by our plugin. Players will not see the Updater-Block during the game, as it will all happen very quickly.

The Updater-Block in your Schematic

If you use WorldEdit, you can also completely deactivate the temporary Updater-Block after adjusting the schematic files. And if you use FAWE you have to add it in your new Missile schematics.

To do this, you can simply overwrite the existing schematic files in the /MissileWars/missiles/ folder. Usually the Starter-Block is in front of the foremost piston or observer. So (re-)save the schematic one by one with your target Starter-Block and save it again.

Note: In principle, the most Missile constructions only require one Updater-Block. The internal replacement process of MissileWars searches for all blocks of corresponding tempblock_material within the defined tempblock_radius - so more than one Updater-Blocks can be used, if it's necessarry for the Missile.

If you want to use a material other than NOTE_BLOCK, you must then change the Update-Block Settings as described below.

Update-Block Settings

Here you find the compact snippets for the recommended configuration section based of your WorldEdit Solution.

The values are described here exactly, as you can test the behavior live in your Arena Area with the Past-Command (e.g. /mw paste <missile> [flags, e.g. '-tempblock:true']).