@perchance@lemmy.world pinging dev.

You can have each of the suits into a single list, then control that parent list. E.g.

Uniform
  https://user.uploads.dev/file/53321b33603b8f9f386fb870db73ad65.png
  [Top] ^[camera.includes("top") && actor != "dryad"]
  [Mid] ^[camera.includes("mid") && actor != "angel"]
  [Low] ^[camera.includes("low") && !["mermaid", "minotaur"].includes(actor)]
  [Rear] ^[camera.includes("rear") && actor != "angel"]
  [TopMidLow] ^[["top", "mid", "low"].some(a => camera.includes(a))]


Top
  batman mask ^[specificCostume == "batman"]
  ...

Mid
  batman suit with batman logo on the chest, batman gloves, batman belt ^[specificCostume == "batman"]
  ...

There should be no problem with linking the defaultCommentOptions on JavaScript, it would be on this part of your code on the HTML:

    ...
    let othersChatDiv = document.createElement('div');
    othersChatDiv.id = 'others-chat-container';
    othersChatDiv.style.display = 'none'; // Hide others chat by default
    
    let mainChatOptions = defaultCommentOptions.createClone;
    mainChatOptions.channel = "qine-main-chat";
    mainChatOptions.commentPlaceholderText = "Casual talk, memes, fun — all here!";
    mainChatOptions.onComment = function (comment) {
      // Handle new comments in Main Chat
      console.log("New comment in Main Chat:", comment);
    }
    let mainChatPlugin = commentsPlugin(mainChatOptions);
    ...

The problem is bannedUsersList is not in the generator, so it gives errors. Removing that from the defaultCommentOptions makes it work.

Since it doesn't use the previous prompting, then it wouldn't work anymore. Anything in the prompt is taken into account in generating the image. I also don't think there is any Flux prompting shenanigans (or hidden/secret annotations) included in the new model that can hide hidden messages on the prompt (as far as I'm aware).

Best way is to set up the image generation locally. You can use Automatic1111 since it was the basis of the API before, where (( tag )) emphasis syntax is based on.

Okay, so since you used a 'Style', it would essentially add additional text/prompt to your input prompt to 'steer' the image to the selected style.

Here is how the prompt is set up using the 'Fantasy Portrait' style on the t2i-framework-plugin generators like ai-text-to-image-generator:

, d&d, fantasy, highly detailed, digital painting, artstation, sharp focus, fantasy art, character art, illustration, 8k, art by artgerm and greg rutkowski. It's an absolute world-class masterpiece artwork. It's an aesthetically pleasing artwork with impeccable attention to detail and impressive composition.

So, with the prompt adding 'greg rutkowski' (and artstation) it would add some kind of signature (or watermark) with it. You can view what the styles are adding on this styles import page.

Thanks for the heads-up 💯

If you have any questions regarding the AI, a lot of it has been answered here: https://rentry.org/perchance-ai-faq

You can also just ask the questions here if it is related on the platform itself, unless it is regarding on how the server is set up and such.

It is here in Petra's Guides.

First of all, I'm not the Dev of the site, just a regular user/helper.

As for the NetworkError if the response is taking long enough, it might timeout which may cause the network error. Or a lot of users are using it, in which case the server is getting a lot of requests.

As for contributing, finding bugs/errors helps as well as sharing the pages/generators you've made. Also note that AI tools are sustained by advertisements (not sure about the AI Helper, how it is sustained since the AI Text Plugin and Text to Image adds an advertisement on the bottom of the page).

Can you provide more info?
What device + browser are you using? Are you using incognito/private browsing? Does your browser has auto-delete cache/browser data?

@perchance@lemmy.world pinging dev. The problem is in the line 3269 on setting the usageStats.

...
// line 3269
    if(result.exportUserData === "no") {
      json.data.data.find(d => d.tableName === "usageStats").rows = []; // Throws error here
    } else {
      let usageStats = json.data.data.find(d => d.tableName === "usageStats");
      if(usageStats) {
        usageStats.rows = usageStats.rows.filter(entry => keepThreadCheck(entry.threadId) && keepCharacterCheck(entry.characterId));
      }
    }
...

Seems like on the DB Schema (line 2813), usageStats is no longer used, so maybe just removing them in the export fixes them.