Block "beacon" in WorldEdit / AsyncWorldEdit

Vouch, there is no reason for anyone to need to place more than a handful of beacons at once.

object, reasons were stated below

Object

Beacons on their own (without being activated) really aren't that big of an issue. Even if they are largely placed using worldedit and activated with all the beam shit just... Get staff to clear the build? No need to block everything that causes occasional lag given they're rarely used for that purpose these days.

Object. If there's a way to only block mass amounts being edited in (~10k beacons at once), then Vouch.

I Vouch.

Quote from Shyrix

Beacons on their own (without being activated) really aren't that big of an issue.

Compare the two images in the spoiler below. The first one has no 25-radius beacon sphere and I get over 200 FPS. As soon as I generate the sphere my FPS ranges from 0 to 5 at most. This is not a case of a "shit GPU" since I have a higher-end RTX 30-series card. There are absolutely 0 compelling reasons other than to lag clients that people should be able to WorldEdit beacons. Immediately after removing the sphere, my FPS recovered.

Changing to object, partly with Alcos reasoning, partly after my own tests in-game. Any significant amount of beacons can cause lag (less so when done as a flat edit as opposed to a sphere, but still). There's not really any legitimate use for world editing in beacons anyway, as their practical use doesn't require more than a few for a large area, and their decorative use is similarly small.

vouch, ihate beacons because they are awfully laggy and gives bad actors opportunity to make the server unplayable.

Object, beacons aren't an efficient way to lag clients. But semi-transparent blocks do really tend to lag the game when mass-edited in with world edit.

Quote from KaddicusAlmighty

block mass amounts being edited in (~10k beacons at once), then Vouch.

Tbf this should be applied to every block