Command aliases executed in wrong order
Bobcat00 opened this issue ยท 0 comments
Server Implementation
Paper
Server Version
1.19.3
Describe the bug
If a Bukkit command alias is defined (in commands.yml) with a sequence of FAWE commands, the commands are executed in an arbitrary order which changes every time.
AWE+WE does not have this problem.
To Reproduce
- Place the following in commands.yml:
aliases:
squarene:
- /pos1
- /pos2
- /shift 1 down
- /expand $$1 n
- /contract 1 s
- /expand $$1 e
- /contract 1 w
- /walls glowstone
The intent of this command to to place a glowstone square of user-specified size in the ground, with the southwest corner of the square located under the player's feet.
-
Go to a location that has a suitably large section of flat ground. I used a plot world.
-
Enter the command
/squarene 16
. This should create a 16x16 square. You can use//undo
to remove the glowstone and execute the command again. You'll see the commands are processed in a different order each time.
Expected behaviour
The commands should be executed in the order in which they are defined. It should be deterministic.
Screenshots / Videos
The chat area shows that the commands are executed in the wrong order.
First, here is the chat when the 8 commands are issued manually, showing the correct order of execution. Positions set, regions shifted, expand/contract, expand/contract, and finally 60 blocks are set.
The following two screenshots show what happens when the command /squarene 16
is issued. Note the commands are not executed in the correct order, and the sequence changes every time. FAWE is manipulating the region before the positions are set, and setting the blocks before the final region is defined.
Error log (if applicable)
No response
Fawe Debugpaste
https://athion.net/ISPaster/paste/view/e7eadac353f94e9198b76919ef0020de
Fawe Version
FastAsyncWorldEdit version 2.5.3-SNAPSHOT-374;84e1886
Checklist
- I have included a Fawe debugpaste.
- I am using the newest build from https://ci.athion.net/job/FastAsyncWorldEdit/ and the issue still persists.
Anything else?
No response