Sorry about that! I've fixed the issue so it should work now.
If I understand your question correctly, I think you're looking for this example: https://perchance.org/programmatic-get-set-submit-comments-plugin-example#edit
Basically, if you have this in your HTML panel:
[com = commentsPlugin(options)]
Then you can write com.submit("the text you want to submit on behalf of the user")
, and you can of course generate that text via the ai-text-plugin.
You can get existing comments (to give them to the ai-text-plugin as part of the instruction which gets it to generate a comment) using com.comments
. Also see these examples:
- https://perchance.org/simple-comments-plugin-oncomment-example#edit
- https://perchance.org/comments-plugin-oncomment-example#edit
There is code in https://perchance.org/tabbed-comments-plugin-v1#edit which does what you want, but there's a lot of other code in there too, so it's not a very 'educational' example. Or if you just want to use that plugin, you can of course do that. Here's an example: https://perchance.org/m56h7orowv#edit
My bad, sorry about that! Should be fixed now. Let me know if you still have issues.
This is a good point. I should be creating more "high-level config" layered on top of the examples that I create, so people can change a line here and there, and see how easy it is to create something new, and then maybe dive deeper from there. The ai chat/rpg/etc. generators that I've made aren't very "configurable" in the same sense as the t2i framework thing.
Thanks! create-instance-plugin problem is fixed. Not sure about the ai-character-chat problem. It's possibly a browser-cache-related issue where for some reason Cloudflare cache returned a faulty response at some point (for a scipt tag in ai-character-chat), but then it was cached by a bunch of users before the issue resolved itself.
I've just tried adding a quick fix to work around the issue in the meantime, so hopefully it's solved now.
Hmm, I'm not sure what is causing this, but I've just tried to add a fallback/workaround in case of this type of error. Can you please try again and let me know if there's still an issue?
(I'm assuming this bug report is referring to perchance.org/ai-character-chat - please check the URL exactly matches that)
If you refresh the page, does it fix the issue? I think it might have been a temporary problem related to caching. Let me know if it's still a problem for you.
VPNs are not blocked on Perchance - you should be able to access the site and create/edit/view/use generators (including AI-based ones) regardless of whether or not you're using a VPN.
Are you perhaps talking specifically about the comments plugin? If so, yeah it's unfortunate. I had to disallow VPNs from posting comments because they allow you to switch IPs instantly, which removes any ability for moderation, user-blocking and spam prevention.
I have ideas about how to remove this constraint (at least partially), but for now my todo list is too long to get to it any time soon.
Note: If you want to allow comments from VPNs on your own generators, then "one weird trick" (which I should formalize into an actual feature) is to put "feedback" in the channel names. Another trick is to embed Disqus, or some other comments system (or of course create your own comments plugin if you know how to code).
Thank you!! I did a bit of refactoring on the engine recently and introduced a bug. Fixed.
Thank you pestering me on this, this was a bug with how customCode
was being handled on /ai-character-chat
It's all fixed now, and I've updated the rentry doc with the Python example, and also created an example character for you to test here:
https://perchance.org/ai-character-chat?data=Python_Helper~986c80bf8a26a3b156a5be6c34805540.gz
Thanks! Also ty @[email protected] for looking into this, and for the ping 🙏
Thanks! I've just fixed a bug in the be-plugin
which was the cause of this. But it looks like there's a bug in the have-plugin
, and that's not mine. Whoever owns it needs to change this:
let thisNode = document.querySelector(`.${elementId}`);
to this:
let thisNode = document.querySelector(`.${elementId}`);
if(!thisNode) return;
I.e. just add if(!thisNode) return;
below it.
Hi, sorry, I'm not able to reproduce this issue. Can you please make a minimal example that shows the issue? You can e.g. create a remix of this generator: https://perchance.org/comments-plugin-admin-example#edit and make minimal changes which cause the issue to occur.