Allow replacing nonexistiant GBs or LBs.

[forkiesassds]

It annoys me that to replace a nonexistent GB or LB I have to make an LB just to be able to replace the blocks in the map.

[UnknownShadow200]

Question is how should nonexistent block IDs behave in respect to block permissions

[rdebath]

Same as if you /delete or /paint them manually.

[UnknownShadow200]

I mean more from the aspect of /blockset

[rdebath]

:confused: ... /blockset doesn't need to be changed. :bulb: ...

My take on the problem that @forkiesassds has is...

• Copy area from level A
• Paste into level B
• /Replace block that is Valid in A but is invalid in B with something valid in A -- this fails because "From" block is invalid.
• So manually use /place, /paint or just delete and place to replace the trivial updates.
• Create remaining /lb entries.
• Repeat /replace command.
• Delete fake '/lb' entries.

The point being that the only permissions I see is needed are the same as existing commands need, in this case it appears to be default to "Invalid block may be deleted" and check "Air/NewBlock can be placed."

Note that the real problem is the Paste (or an /lb remove) which allows invalid blocks to exist. However, "fixing" this would mean either a horrible multiple substitutes syntax for doing the /replace during the /paste or just pushing the /lb creation before the paste. This cannot be automated because you don't know if the difference between purple block and violet block is significant.