I'll try not to think about what text this thing is spitting out--yikes!
Anyhow... I see no errors at all.
This is a Lemmy Community for perchance.org, a platform for sharing and creating random text generators.
Feel free to ask for help, share your generators, and start friendly discussions at your leisure :)
This community is mainly for discussions between those who are building generators. For discussions about using generators, especially the popular AI ones, the community-led Casual Perchance forum is likely a more appropriate venue.
See this post for the Complete Guide to Posting Here on the Community!
1. Please follow the Lemmy.World instance rules.
2. Be kind and friendly.
3. Be thankful to those who try to help you.
4. Only post about stuff related to perchance.
5. Refrain from requesting Prompts for the AI Tools.
text-to-image-plugin
and ai-text-plugin
) e.g. "What is the good prompt for X?", "How to achieve X with Y generator?"6. Search through the Community Before Posting.
I'll try not to think about what text this thing is spitting out--yikes!
Anyhow... I see no errors at all.
It seems like either the OP responded to my message, or they just figured it out by themselves.
Ah okay 👍
You can't assign variables in the middle of a list, instead you would move this part to the output
assignment so it would actually create the variable that could be evaluated by the ..., r = recipies.selectOne, r.name]
instance:
[f=createInstance(ingredients.flour.selectOne), createInstance(b=ingredients.flour.selectOne)]
Like this:
Why does this happen?
Perchance recognizes and evaluates the f
variable assignment block I've mentioned before as the child of the list pie
which is a child of the list recipies
, making it unusable when called it directly within the variable's name. To fix this you'd need to execute that assignment before the recipies
list is evaluated (as I've said before).