#Creeping Crypts Command Issues

1 messages · Page 1 of 1 (latest)

hot beacon
#

I recently changed my addon from using runCommand to scripts, but it broke my commands and im trying to figure out why

#1067535608660107284 for context

#

With these do i use @s or @e?

wispy gyro
#

if ur using entity.runCommand then s is that entity ofc

fresh osprey
#

How short is the entity's lifespan btw

hot beacon
wispy gyro
#

what was orginal thing

hot beacon
#

after all necessary commands are executed by the one entity it despawns

hot beacon
wispy gyro
#

what were u doing before that need to be translated toto scripts

hot beacon
#

using runCommand

which is being deprecated

fresh osprey
#

Afterevents takes about 1 tick after the event trigger in script

hot beacon
#

runCommand was running the functions and controlling the despawning depending on conditions

hot beacon
fresh osprey
#

What if u extend the timer to 2

hot beacon
#

how do i do that

fresh osprey
#

In the entity.json

#

Oh well, I'd just convert most of those cmds into scripts if I were u

hot beacon
#

once again i cant do that

#

itll be too slow

fresh osprey
#

Hmm, fair point.

hot beacon
#

ok whatever it is its definitely the script

#

something is screwing up where the structures are placed