commands run in different order/inconsistant on realms vs local in Papercraft 2: City Project

Partner Rank:

2

Partner Team Reporting:

Jigarbov Productions

Verification builds:

1.16.10 live & 1.16.20 betas, issue is in realms

Summary:

commands run in different order/inconsistant on realms vs local in Papercraft 2: City Project

Impact:
commands behaving inconsistently between realms and when in single player creates distrust in realms and the content creator. players don't know why something doesn't work and often assumes its the fault of the creator despite us having no control for th

Repro Steps:

1. Download papercraft 2 from the marketplace
2. put yourself in creative mode
3. teleport to -263 104 119
4. open creative menu and search for pergola
5. grab a bunch of those items (they are spawn eggs)
6. use them on the vertical logs surrounding the cobblestone area

Expected: Once used, some functions run that clone from an area below the map to create a pergola. The vertical stumps in particular are all connected and it looks good. These vertical stumps cover the bottom stump preventing the player to place multiple in the same spot.
Observed: In single player, and multiplayer hosted on a normal system it works as expected. When hosted on realms, the commands run in a different order and the build that is spawned is incomplete leaving the spawn point available to waste extra items on this spot which can block a player from completing the quest if they use a second on that spot.

Screenshots/Videos attached: Yes

Video https://youtu.be/f6icSKiK0nY

Regression Builds:
realms issue

Notes:
function that runs when the egg is spawned in animation controller. as you can see, in 2 of the 4 cases, the fill is occurring after the second clone:
/execute @s ~ ~ ~ detect ~ 1 ~ concretepowder 2 execute @s ~ ~ ~ detect ~ 102 ~ concrete 1 clone -262 3 120 -260 8 124 -262 103 120
/execute @s ~ ~ ~ detect ~ 1 ~ concretepowder 2 execute @s ~ ~ ~ detect ~ 102 ~ concrete 1 fill ~ ~ ~ ~ ~5 ~ air 0 destroy
/execute @s ~ ~ ~ detect ~ 1 ~ concretepowder 2 execute @s ~ ~ ~ detect ~ 102 ~ concrete 1 clone -262 3 120 -260 8 124 -262 103 120
/execute @s ~ ~ ~ detect ~ 1 ~ concretepowder 2 execute @s ~ ~ ~ detect ~ 102 ~ concrete 2 clone -262 4 125 -260 8 128 -262 104 125
/execute @s ~ ~ ~ detect ~ 1 ~ concretepowder 2 execute @s ~ ~ ~ detect ~ 102 ~ concrete 2 fill ~ ~ ~ ~ ~5 ~ air 0 destroy
/execute @s ~ ~ ~ detect ~ 1 ~ concretepowder 2 execute @s ~ ~ ~ detect ~ 102 ~ concrete 2 clone -262 4 125 -260 8 128 -262 104 125
/execute @s ~ ~ ~ detect ~ 1 ~ concretepowder 2 execute @s ~ ~ ~ detect ~ 102 ~ concrete 3 clone -267 4 125 -263 8 128 -267 104 125
/execute @s ~ ~ ~ detect ~ 1 ~ concretepowder 2 execute @s ~ ~ ~ detect ~ 102 ~ concrete 3 fill ~ ~ ~ ~ ~5 ~ air 0 destroy
/execute @s ~ ~ ~ detect ~ 1 ~ concretepowder 2 execute @s ~ ~ ~ detect ~ 102 ~ concrete 3 clone -267 4 125 -263 8 128 -267 104 125
/execute @s ~ ~ ~ detect ~ 1 ~ concretepowder 2 execute @s ~ ~ ~ detect ~ 102 ~ concrete 4 clone -267 4 120 -263 8 124 -267 104 120
/execute @s ~ ~ ~ detect ~ 1 ~ concretepowder 2 execute @s ~ ~ ~ detect ~ 102 ~ concrete 4 fill ~ ~ ~ ~ ~5 ~ air 0 destroy
/execute @s ~ ~ ~ detect ~ 1 ~ concretepowder 2 execute @s ~ ~ ~ detect ~ 102 ~ concrete 4 clone -267 4 120 -263 8 124 -267 104 120**