The AI Chat is powered by the AI Text Plugin which uses Llama-based AI model, though I’m unsure what version it is, since it is recently being “upgraded” by the Dev I think. However, you can’t actually run or save the generator locally. It is possible to save or download it, but the AI chat functionality won’t work in the offline downloaded version, since the AI stuff can only be run on the website (see this reference as to why).

• If you’d like to play around with running AI text generation models on your own machine (“locally”), then r/LocalLLama is a good community to join.

—Notes of ai-text-plugin

Yeah thanks for pointing out the issue, I definitely missed that one. I’ve corrected it on the second generator and it worked now.

The former should probably be throwing an informative error though…

It is interpreted as a valid, unevaluated string value so that’s probably why it didn’t throw any error. Maybe instead should create a warning for this import mistake so newbies can easily point it out (especially if they noticed something wrong with it) 🙂

Update: After some more testing, the URL params in A Venture Poem Generator now works using the plugin import but not with the view counter experiment one (that link has ?performanceMode=true inserted for testing). It still greets with the default input Hello, user without mentioning the inputted name in the URL. It still works in url-params-plugin-example though.

@perchance@lemmy.world would be nice to take a look at this issue. Is that caused of something with the generators or something else?

Another great use of evaluateItem (from my experience) is that it helps evaluate strings containing arbitrary code into proper output behind-the-scenes before modifying them with other properties or functions. For example, running ["[conjugate(verb).gerund] [adjective.pluralForm]"] outputs as expected, a phrase consisting of a gerund verb and a pluralized adjective word. The Perchance engine evaluates the unevaluated string right away after any modifications (for example, through titleCase) were made. And so, running ["[conjugate(verb).gerund] [adjective.pluralForm]".titleCase] will result in a mixed undefined or (syntax error) output (e.g. intending undefined) because it converted the unevaluated string (which is the Perchance code) into title case before it was evaluated, and results in an unwanted output.

But prepending evaluateItem right before any modification would do the opposite - it evaluates the string before any modifications was made. Using that, running ["[conjugate(verb).gerund] [adjective.pluralForm]".evaluateItem.titleCase] would output a properly title cased phrase in that same format because the Perchance code inside the string is evaluated before the final output was eventually made title cased.

You can replace the square brackets inside with parentheses, otherwise it’ll just be interpreted as an array:

[r.roleBrawn + (s.subBrawnMod || 0)]

While the event is starting, I want to mention some more thoughts I’ve been keeping earlier after hosting the event midnight, about some planned updates for the Events page in the future (and probably going to implement them in the next Preview updates right away):

• Some of the big events (like image contests and big moment updates like “A Venture for the Big Update”) will be integrated into the Hub for greater visibility (so the event will also be shown as a Hub event in the Events tab), but some smaller events (like break times or Silent Days) will only be exclusively shown on the Generator Manager Events page
• The description will also use Markdown since I feel that wasn’t well-polished enough and would sometimes break out when writing down for the first event
• Probably also planning for an entire UI overhaul/rearrangement for the event page as well
• Also planning to implement an events flyout somewhere in the sidebar or the Home page (similar to the Events flyout in the Hub)
• etc, etc…

(Will write down more once they start to pour in)

You can prevent the output from accidentally evaluating the selectOne of empty n arrays by just not evaluating the <span contenteditable ... part when that empty array has no length (basically you put a condition in which if n isn’t empty then evaluate the span word element, which eliminates that syntax error problem):

You can also check for n.length > 0 instead of n.length. Also pretty cool generator concept! A random letter generator button might be a good idea. Here’s how would you implement this using a list and a button:

letter
  ["{A-Z}".selectMany(Math.floor(Math.random()*4)+1)]

<input id="acronymInput" oninput="acronym = this.value" placeholder="type an acronym :)" value="TPK" />
<button onclick="ltr = letter.evaluateItem, acronymInput.value = ltr, acronym = ltr, count = -1, update()">random letter</button>

Bonus feature: If you type “rain”, “Go rain mode”, “Let it rain”, or “Just rain” in the comments of the plugin page, it’ll activate the rain effect right on the page. Otherwise, if you comment “stop”, “Please stop the rain”, or “This plugin is so cool, I’d wish to stop the rain”, it’ll stop the rain effect.

My solution is quite simple here. You just create a list of races (in this example, list of fruits) that has a sublist of race types (in this example, fruit types),

fruit
  Apple
    Green Apple
    Red Apple
    Blue Apple
  Grape
    Red Grape
    Green Grape
  Berries
    Blackberry
    Blueberry

and then reference them in the output like this:

  Fruit: [fr = fruit.selectOne, fr.getName]
  Fruit type: [fr]

You can then change the references of fruits to races and modify them as you like.

races
  Elf
    High Elf
    Wood Elf
    Dark Elf
  ...

Did you put the Death_Chance and Illness_type variables into a parent list like this?

someListName
  Death_Chance = Moral Blow
  Illness type = Whitecough

If so, you’d need to change the aListName part of the syntax to reference the name of the sublist:

<br>Death Chance: <select oninput="someListName.Death_Chance = this.value">
  <option value="Moral Blow">Moral Blow</option>
...
<br>Illness type: <select oninput="someListName.Illness_type = this.value">
  <option value="Whitecough">Whitecough</option>

[someListName.Death_Chance == "Moral Blow"]

I’ve had the exact same thing, the com object was undefined’d while testing out. But I think this was a bug on the behalf of the com object handling, that it should retain the object without refreshing the comments section altogether.

<br>Death Chance: <select oninput="aListName.Death_Chance = this.value">
  <option value="Moral Blow">Moral Blow</option>
  <option value="Tragedy">Tragedy</option>
  <option value="Destruction">Destruction</option>
  <option value="Devastation">Devastation</option>
  <option value="Calamaty">Calamaty</option>
  <option value="Plague">Plague</option>
  <option value="Eradication">Eradiction</option>
  <option value="Extinction">Extinction (WARNING: DON'T) </option>
</select>
<p id="out1">[warningList]</p>
<button onclick="update(out1)">Show</button>
<br>Illness type: <select oninput="aListName.Illness_type = this.value">
  <option value="Whitecough">Whitecough</option>
  <option value="Carrionplace Disease">Carrionplace Disease</option>
  <option value="Tainted prey">Tainted prey</option>
</select>

Here is a modified code for the dropdown menus so that they assign the values to the variables properly (since Death_Chance and Illness_type are apparently stored into some sort of parent list, so you can rename aListName to the name of that list). Also, if the dropdown menu doesn’t work, try changing oninput to onchange.

You’ll also need to associate the variables written in dynamic odd notations in lists to reference the parent list as well (e.g., [Death_Chance == "Moral Blow"] to [aListName.Death_Chance == "Moral Blow"]).

Okay, so first you add the quotes between these curly brackets wrapped syntaxes (and remove the quotes around the none part) so they’ll be evaluated properly:

And then change the rarity picking mechanism (evaluateItem first, create a matchable version, and then display the evaluated version instead of just selectOne and then display) so it’ll be matched properly when picking a gimmick and an ability, to this:

[ra1 = rarity.evaluateItem, ra = ra1.match(/[A-Z]+/g)[0], ra1]

In the output syntax I see some of the if statements are not in lowercase, so you need to lowercase them in order to work:

(You can also just find-and-replace If with if btw, w/keyboard shortcut Ctrl+H)

@perchance@lemmy.world ping dev.

Yeah, I could see the overflow issue spreading across many generator pages, even into the plugin page itself. I think the Dev should apply the possible fix that would get applied across generator pages.

This issue did not appear on Firefox though upon checking.

You can actually set the settingsButtonStyle’s and fullscreenButtonStyle’s overflow parameter to hidden as a temporary workaround so that the scrollbars at the bottom would disappear.

commentOptions
  settingsButtonStyle = overflow: hidden;
  fullscreenButtonStyle = overflow: hidden;

Also did you notice a few more customization options were added to the Comments Plugin?

There is, however, another possible way to clear the gallery besides duplicating, which is by overriding the generatorName value to something else e.g. ai-text-to-image-generator-0324.

I think so. If you want to make feature requests then you can make a post and/or make a comment with tag @perchance@lemmy.world just like what I’m about to do.

Also @perchance@lemmy.world when I click on the download page on any image it always brings me into a new tab with the image file. Is this some sort of bug?

There isn’t quite a way to unless there’s a “copy seed” button somewhere in the info overlay. @perchance@lemmy.world

Also a tip: you can also bring the info section by clicking on the title or description at the bottom of an image in the gallery.