Added "Place feature at" procedure blocks

[AlsoSomeoneElse]

• Added a datalist of configured features
• Added a base type for mod elements that provide a configured feature (currently all feature ME + blocks and plants if generation is enabled)
• Added "Try to place feature at" procedure block, with a variant that returns if the procedure was actually placed

[KlemenDEV]

I did some tests and seems most vanilla features don't want to place (global trigger "On bucket used"). I was testing some underground features on the surface and they don't place. Isn't it that placement is ignored and those should be placed correctly?

[KlemenDEV]

I have also tested placing custom mod element configured feature (NBT-based feature) and only one block is placed (updated, all blocks actually place as one can't go through them - ghost blocks) on the global trigger "when right-clicked on block". However, this is not the case with vanilla features (when they do place).

Are we sure this procedure is reliable enough to not cause bug reports due to its limited use?

[AlsoSomeoneElse]

I did some tests and seems most vanilla features don't want to place (global trigger "On bucket used"). I was testing some underground features on the surface and they don't place. Isn't it that placement is ignored and those should be placed correctly?

Some features have additional placement defined in the feature itself rather than the placement (for example desert wells can only generate on sand). This is also why the additional generation condition isn't disabled in #4713. Ideally the procedure block works the same as /place feature.

I have also tested placing custom mod element configured feature (NBT-based feature) and only one block is placed (updated, all blocks actually place as one can't go through them - ghost blocks) on the global trigger "when right-clicked on block". However, this is not the case with vanilla features (when they do place).

I can look into the NBT-based feature to see if it can be fixed, but some vanilla features also generate ghost blocks (block piles for example - MC-248248)

Are we sure this procedure is reliable enough to not cause bug reports due to its limited use?

We could add a warning message to the place feature procedures, like for the NBT procedures.

[KlemenDEV]

Thank you for the detailed explanation!

I agree with a warning to avoid issues on the issue tracker

[github-actions]

This PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Do not remove this label manually, it should be removed by the bot when new activity occurs.

[github-actions]

This PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Do not remove this label manually, it should be removed by the bot when new activity occurs.

[github-actions]

This PR has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Do not remove this label manually, it should be removed by the bot when new activity occurs.

[KlemenDEV]

LGTM, thanks!

[KlemenDEV]

A port of procedures and data list is now needed for 1.20.6 in the future