On how you have your data, you can probably just add a url property for each instance of the source e.g.:

   {
      name: "original",
      label: "Original",
      placeholder: "Click the button below to generate an original quote.",
      data: [
        {
          quote: "Happiness beckons you once you forget you were looking for it.",
          source: "Eleanor Trent, 'Where's Joy?'",
          url: "link here"
        },
        {
          quote: "Memory is just the past asking for a permanent residence permit.",
          source: "Dr. Selim Farouk, 'The Mind's Archive'",
          url: "another link here"
        },
        {
          quote: "No one knows how Sentience is born, but we sure know how to kill it.",
          source: "Dr. Marcus Webb, 'The Philosophy of Consciousness'",
          url: "link here"
        },
        ...

Then you can access it with .url (quoteEntry.url) and set it as the href of the quoteSourceEl.

The Automatic1111 link should have installation procedures on how to install it (and automatic installations) for your device. Here is for NVidia GPUs: https://github.com/AUTOMATIC1111/stable-diffusion-webui/wiki/Install-and-Run-on-NVidia-GPUs

As for the other one, here is the steps on how to install it: https://github.com/Raxephion/Old-Perchance-Revival-WebUI/tree/main?tab=readme-ov-file#-easy-setup-windows---download--run

You need to make the quoteSourceEl to be an <a> tag e.g. <a id="quoteSourceEl" class="source" href="#"></a> , then after you add a href value, it would be a hyperlink.

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.

Consecutive ~ will do that e.g. ~~Test~~, you can maybe just add a space or reduce the number of ~.

If you want ~ you can just use it as is e.g. ~Testing~ no need for escape.

Best way I would think is use the default comment options that you have on the Perchance lists:

defaultCommentOptions // for comments plugin: https://perchance.org/comments-plugin
  width = 100%
  height = 350
  commentPlaceholderText = Leave friendly comments..
  submitButtonText = submit comment
  bannedUsers = [bannedUsersList]
  customEmojis = {import:huge-emoji-list}
  adminFlair = 👑 Creator
  adminPasswordHash = 4b7a8a671d949baf24756f731091d13018de5c2ab4dd2cc1c1612a6643986933

As the base options like so:

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);

Can you link the page you are working with?

See this related thread for importing through JS.

Instead of manipulating the iframe src, I just re-instantiated the galleries with updated options: https://perchance.org/gwn80163bc

Used createPerchanceTree to create a new perchance list for the banned prompt phrases.

So, on your:

<div class="flex">[output]</div>

You need to enclose the [output] in a div for the Update Rows to work since it looks for the number of div on the .flex container like so:

<div class="flex"><div>[output]</div></div>

Also, you changed the start of the ‘for loop’ on the update rows with let i = numRows - 1 which would mean it can only update one row since the loop terminates if it exceeds the numRows. Just use the let i = 0.

If you want to only update the ‘last’ row, you can do:

function updateLast() {
  let lastRow = [...document.querySelector(".flex").querySelectorAll('div')].at(-1)
  lastRow.innerHTML = output
}

So, on the .flex container, every time you add the output on the innerHTML, it would essentially re-run the ‘evaluation’ of the square brackets, which would also update the container - which updates the previous images. Best way is to not alter the InnerHTML by concatenating and use .appendChild instead. Ex:

  function addImageRow() {
    let con = document.createElement('div');
    con.innerHTML = output
    document.querySelector(".flex").appendChild(con);
  }

But since this wouldn’t have any square brackets, you cannot use the regular update() function to reload them. Here’s a function to update them:

function updateRows() {
    let numRows = document.querySelector(".flex").querySelectorAll('div').length
    document.querySelector(".flex").innerHTML = ''
    for (let i = 0; i < numRows; i++) {
      let con = document.createElement('div');
      con.innerHTML = output
      document.querySelector(".flex").appendChild(con);
    }
  }

The generators on the /generators page are updated in intervals, so it would take a little bit of time for the server to update the changes before the changes on your generator to be reflected on it.

You can do something like this on the second generator:

importInputs
  gravity = default
  atmosphere = default

output
  [lifeform] // output of the second generator

lifeform
  lifeformOne ^[importInputs.gravity == "something"]
  lifeformTwo ^[importInputs.atmosphere == "methane"]

Then on the first generator:

genTwo = {import:gen-2}

generateGenTwo
  [genTwo.importInputs.gravity = selectedGravity, genTwo.importInputs.atomsphere = selectedAtmosphere, ''] [genTwo.output]

This way, you set the variables of the second generator from the first generator, so that the lists used have the correct odds used.

Here are also some references from previous threads:

• https://www.reddit.com/r/perchance/comments/6gscyk/transferring_variables_between_generators/
• https://www.reddit.com/r/perchance/comments/bgphrz/how_do_i_pass_variablesreferences_to_imported/

Maybe explain the process that you want to achieve and have some test generators? It should simply be something like:

// gen-1
genTwo = {import:gen-2}

output
  [genTwo(something)]

// gen-2
genThree = {import:gen-3}

$output(input) =>
  genThree(input)

// gen-3
$output(input) =>
  // process code here

Here’s something I’ve cooked up: https://perchance.org/3on4b1h5qt

It uses functions to reselect the value on the ‘select’ if the ‘image select’ is changed and vice-versa. I’ve also changed a little bit of the CSS for the image dropdown.

By private gallery, you mean you clicked the ‘shield’ button below the image? If so, then clearing the browser cache deleted them and there is no way to restore them. The private gallery saves them in your browser cache, compared to the other way which saves it publicly on the server.

If you saved them into the public gallery, by hovering on the image, clicking the heart button, then clicking save to gallery, you can use the page I linked.

If you remember the gallery name, you can try finding the images using this: https://perchance.org/prompt-hunter

If you saved it in the public gallery and not using the new private gallery, then deleting your cache wouldn’t delete the images. It would delete the ‘pinned’ gallery selector though.

The “Chat With This Character” button is exclusive to t2i-framework-plugin-v2-based generators. Essentially, it wraps the text-to-image-plugin in another container and adds that button, something like so: https://perchance.org/t2i-with-create-media-gallery that is also imitating the save to private gallery in the t2i-framework-plugin-v2 generators.

If you want buttons that are also like the ‘hover’ buttons, as Koto said, you can relative + absolute position those buttons to wrap the main iframe.

You can manipulate the iframe element itself, but not the contents within the iframe which are the buttons.

I haven’t misunderstood your post, and I’m just giving my ideas on how to implement some of them by utilizing the custom code feature. Having those natively implemented would be the best, but in case it isn’t, there are still ways to ‘implement’ it ourselves. We can even create our own fork of the page and implement them natively although there might be a lot of finicking around the current code (some of examples of forks are: TPS Group Chat that allows other characters to auto reply and Petrafied ACC further fork of the TPS Group Chat and gives approximate number of tokens that your Role Instruction would add to the context length, for multiple characters).

I can’t speak for the Dev (so I’ll ping them) on how hard these would be to implement natively, but I would think that this would be implemented on the ‘thread’ level of the chat (at least if I would create a custom code, it would be stored there). The statuses (away from/with character, avatar/portrait states) would be stored on the thread and there would be triggers (maybe through keywords) that would replace those statuses and also automatically set if the character would auto-reply to the messages or the narrator. There would still be a lot of ‘micro-managing’ with the increase of additional factors. You would have to ‘set up’ the unknown character(s), how you would meet the new character, how frequent would the character be sending the ‘how are you’ messages, how the story progresses outside of the user’s view, etc.

Just to clarify, ‘model’ refers to the AI model that we use that generates the responses. ‘ACC’ or ‘AI Character Chat’ is the user interface or page that use the ‘model’. Using custom codes usually modifies the ‘ACC’ and not the ‘model’, so essentially, we’re ‘modding’ the user interface.

A new ‘model’ would make the AI smarter, as long as the ‘context length’ would be increased (since the AI would have more context for its next response/replies) but the longer the chat goes, the more it also takes up the ‘context length’ and will degrade over time.