I make generators on Perchance.org and do a bunch of other cool things.
Links:
Got some space images while waiting for the forever-stalling loading/saving problem (I just moved to Firefox for Perchance stuff btw because of that)
https://perchance.org/power-rain-plugin
Just made a decorative plugin that adds a rainy effect into your generator. You can also make snowy effects with this, and also any kind of rain effects as well! 🌧️
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 rename 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>
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., [
to ][
). ]
Updated with a date because yes, there will be another update coming out this month. And I’ll also be rolling out the gradual UI revamps teased before within even more updates coming in July! 🚀🚩
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
)
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.
Good luck! I remember the times where I took a break off Perchance for a few weeks on early 2023 (before the huge rest) just because I got a new device and I have to move along everything to it.
Here’s what it would look like on the Advanced Comments Plugin Demo:
The JS library is a very nice importable out there. I’d somehow eventually import this into my generator if I ever need it. It even contains some actually useful functions like celToFah
and fahToCel
, degToRad
, and radToDeg
.
Also regarding to the name-squatting, I think it’s already on the backend behalf of the Perchance engine. I’ll ping the dev for this issue. @[email protected]
You can possibly 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?
You can also add
settingsButtonStyle
,fullscreenButtonStyle
,submitButtonSuccessText
,hideSettingsButton
,hideFullscreenButton
.
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 @[email protected] just like what I’m about to do.
Also @[email protected] 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. @[email protected]
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.
Just a heads up for someone who happened to find this post, there’s a solution written down here: https://lemmy.world/comment/10611524
Also a tip for OP: you can crosspost the post from the Perchance community instead if you want to post in both communities, so the post from this community will get “linked” to that post and everyone would be able to look up on the solution more easily 😄
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.