@[email protected] 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"]
...
If you are using HTML inputs, you can easily access their values like checkbox.checked
for checkboxes and radio buttons, textinput.value
for input values and select dropdowns, in which you can also set their default values for each one natively, unless the function that you've made is for 'resetting' to default values.
I would also go with the way that you have a single global object for all of your variables, just for organizing and ease of access.
You should select the actor
first, to filter the clothes that it can wear. Then, select the camera to further filter the clothes that would be displayed that depends on the framing.
EDIT: Here is a test gen for it: https://perchance.org/ho5e2n0vwt
I think I see the idea you have. What is the scope of the variable you are trying to set it to? You currently have it as:
for (const [key, value] of Object.entries(variablesMapping)) {
if (this[key] === undefined || this[key] === null) {
this[key] = value;
}
}
You are using this
, which refers to the function. It should probably be set into what you have your initial variables, e.g. if you have your variables as properties in a variable called inputs
, then it should be:
for (const [key, value] of Object.entries(variablesMapping)) {
if (inputs[key] === undefined || inputs[key] === null) {
inputs[key] = value;
}
}
So that if you use it like inputs.charNum
, it would be set to the default that you have set with the defining()
method.
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.
@[email protected] 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.
Well, the purpose of the
showFeedback
property is to 'show' the actual comments sent on the feedback comments section, not to 'hide' the button. On the fork that you mentioned, the feedback button is deliberately commented out, which is why it is hidden.