#I was using the mcfunction thing but something wrong is happening

18 messages · Page 1 of 1 (latest)

atomic ledge
#

The mcfunctions wont work and the tick.json is having problems how do I fix this?

modest elbow
#

If there are any errors with those functions, those errors will cascade down to tick.json where it tries to call them

#

You need to fix the syntax errors from the functions in order for the tick.json errors to go away

atomic ledge
#

Oh ok

#

How do I fix it then?

modest elbow
#

It looks like Minecraft wants your pack to use the new /execute syntax. This happens if you enable Upcoming Creator Features in your world, and if your pack's minimum engine version is at least [1, 19, 10]
Come 1.19.50 the new syntax will be mandatory for packs with a minimum engine version of at least [1, 19, 50]

#

To upgrade those commands to the new syntax, we need to execute both as and at the target. Here is an equivalent:

execute @e[type=sam:afterimage] ~ ~ ~ tp ~ ~ ~

execute as @e[type=sam:afterimage] at @s run tp ~ ~ ~
#

/execute as defines the executor of the command, or who @s will select. /execute at sets the position of the command to a target, in this case the @s entity

atomic ledge
#

Then what would this be?

modest elbow
#

You can apply the same principle as above. Generalized it might look like this:

execute <target> ~ ~ ~ <command>

execute as <target> at @s run <command>
#

Although, in this case, since you only need the player's position in those commands, then we can remove the as <target> step. That leaves us with /execute at <target> run <command>

atomic ledge
#

Thats gonna be a lot of work

#

Now that its resolved how do I remove this post

#

?resolve

brave fernBOT
#
Redstone in Add-Ons

You may not access or edit any behaviours of redstone. At all.

modest elbow
#

@atomic ledge Use /close, or right click on the post in the sidebar and hit Close Post