It’s always funny when I get a perchance error in the red box that’s some obscure problem internally. It’s like “here’s some common mistakes,” but the mistake is actually not the user’s fault and they’re not making any mistakes–the perchance engine is 😅

Main thing is… the error message will mean absolutely nothing to most creators, and just look real scary. (I’m able to figure things out to some degree because I’m a web dev.)

It would be good to either catch problems early and handle them without erroring, just logging a warning perhaps.

Or maybe throw up more useful/readable messages, careful to mark it as an internal perchance issue–so then average creators can report that issue, and more advanced “hacky” users like me know it’s because they’re poking around with the internals.

Or you could have it just marked as an “internal error” and have an expandable <details> panel with the real error inside. Again, so advanced users can figure things out, but average users aren’t like AWHAAAAAAAAAA~~~?!

  • @perchanceM
    link
    English
    122 days ago

    It’s always funny when I get a perchance error in the red box that’s some obscure problem internally

    Can you give an example generator with an engine-internal error? Sounds like you’ve found a bug.

    • @wthit56OP
      link
      English
      122 days ago

      I think the ones I’ve found are from my __evaulateText shenanigans ;p

      But also, there was another example. I’ll see if I can find it again and get back to you…