#StartupEvents Registry Validator runs before all registries have been registered?

25 messages · Page 1 of 1 (latest)

little zealot
#

validation check is being run when the script is read

astral auroraBOT
#

Once your ticket has been resolved, please close it with </ticket close:1054771505520717835> command!

little zealot
#

ran through different stages of startup to test when an example registry would show

odd aspenBOT
#

Paste version of registries.js from @little zealot

little zealot
#

you can see here it's the first 'error' is that the registry isn't accepted

odd aspenBOT
#

Paste version of startup.txt from @little zealot

little zealot
#

StartupEvents Registry Validator runs before all registries have been registered?

little zealot
#

@gilded verge is there a good workaround for this?

astral auroraBOT
#

@little zealot Unresolved thread still hasn't been closed! If your question was answered, please close this post with </ticket close:1054771505520717835> command!

astral auroraBOT
#

@little zealot Unresolved thread still hasn't been closed! If your question was answered, please close this post with </ticket close:1054771505520717835> command!

karmic pumice
#

love how this is so old it's gotten two of these now

little zealot
#

@merry cypress if you have time could you take a peek?

astral auroraBOT
#

@little zealot Unresolved thread still hasn't been closed! If your question was answered, please close this post with </ticket close:1054771505520717835> command!

karmic pumice
#

I am currently in an unresolved support thread

little zealot
#

I've thought about going ahead and closing it now that lat has worked on it

merry cypress
#

there you go

#

i feel like it's unfortunately gonna get really murky with like

#

when the registries get populated

#

because forge does this right before registry itself

#

while i'm guessing the validator runs at evaluation time

little zealot
#

validator is now just looking directly for it to be a resourcelocation, not that it exists