When it works on your mobile, are you connected to your home wifi, or using mobile data? That’ll tell us whether it’s caused by your router or something on your PC. If it works on your mobile when you’re connected to the same internet as your PC, then as Edward suggested, it seems like it might have something to do with DNS (since you mentioned switching browsers didn’t help, and I assume using incognito doesn’t either), or some other PC networking settings.

seems like my PC as a whole is being blocked

Note that you’re not being “blocked” here - it’s an error with the request/response. E.g. router or computer is adding weird headers to the request, or DNS stuff is broken, or something weird like that.

Another thing that might be worth trying is creating a new guest login account on your PC (i.e. go into OS settings, add a new user account, then login to that account) and testing from there. And if that still doesn’t work, and you’re willing to get your hands dirty, then you could create a bootable USB so you have a fresh installation of your OS. And if that doesn’t work, then it’s almost certainly something to do with your router/wifi. One thing to test before going to the trouble of doing that is to hotspot your phone’s mobile data connection to your PC if possible - and if it works, then your wifi/router is the cause.

One approach that might work here is to load your feedback button as the very first thing on the page - i.e. before any of the code that could have errors. That way there’s always a feedback button hovering in the corner of the page. Or you could have a “loading screen” that sits in front of all your content, and has a feedback button in the middle, and that loading screen is deleted/hidden once you’ve detected that the page has successfully loaded.

Thanks for that! So the problem is that the anti-bot verification is failing. Next step is to work out why. Can you show screenshots of the console in Guest mode? i.e. click the profile pic in the top-right of a normal chrome window (next to the 3 vertical dots) and click “Guest”. This will open a browsing session with all Chrome extensions disabled. Then open the console and see if you get the same “Cloudflare Turnstile” errors. Screenshot the logs you see there.

Also, some questions:

1. Is there anything unusual about your internet connection? Or is it just a regular home ISP? Or business connection? etc.
2. If you visit https://ip-api.com/ and scroll down to the data on your ISP, does it say this at the bottom:

    "mobile": false,
    "proxy": false,
    "hosting": false

I.e. are they all false, or is there a true value?

If sel_case is a string (i.e. the name of the top-level list that you want), then root[sel_case] will give you the actual reference to the list. The special root variable refers to the “top-level” / “root” node in your Perchance “tree” of lists/sub-lists.

Heads up that __currentPerchanceErrorCount, and all other global variables that begin with __ are “private” (engine-internal) variables, meaning that I may change their name at any time, causing generators to break that were using them. As I mentioned to Bluepower, if you find a variable in the console, you should first check if it’s officially documented (likely on perchance.org/advanced-tutorial ) before using it, and if it’s not, then it should be assumed to be private.

Hmm, I think I misunderstood some stuff with my earlier comments. With the caveat that this is frying my brain a little, I think there are cases that this change would break - e.g. https://perchance.org/bm1vp6py5a#edit Try swapping the plugin import to see the behavior change.

If it turns out it isn’t really possible to fix this issue, then it may be time for me to make a new plugin which fixes this issue and some others, and perhaps introduces some handy features that people tend to need. Let me know if you have any requests in that department - e.g. everything gets fixed by default, but if a property name begins with * (or something), like *foo, then character.foo would be a random property, instead of being fixed/resolved. And another thing I think is to call evaluateItem after selectOne if the selected item has no children. Not sure though - would definitely need feedback on this from people who use the plugin extensively.

Another alternative is to just add an extra “mode” to create-instance-plugin (like the existing "deep" one), which fixes all the issues and makes everything intuitive, but that might make it a bit more complicated and cumbersome, since the behavior would vary so much, which could be confusing to newbies.

No problem! Btw, it looks like you edited your post’s content instead of the post’s title. Your post’s content was already fine :)

Hmm, yeah this has been asked for before, and the reason I haven’t done it yet is because it would make it easier for people to impersonate others. I.e. set their nickname to the same, and set their color to the same, and then rely on people not noticing that the letters are different. This might not trick many people, but it would make it more annoying since there’s a lower chance of at-a-glance check being correct.

Ideally I’d replace the letters with a dingbat font or something so there’s more visual distinction between the tags. Also now that usernames are a thing, this potentially makes the impersonation issue less relevant. I’m still a bit indecisive on this one though…

Here’s a simple example: https://perchance.org/drop-down-list-example#edit

(For future reference, there are actually a lot of example generators built and so if you type “drop down selector to choose list perchance” into google, the above link is the first result :) Also, if you wouldn’t mind, please edit your post’s title to be a summary of your question - that way it’s more easily findable via Google, which helps others who happen to type their question in a similar way that you summarized it, and so reduces the need for people on this forum to answer lots of duplicate questions. Thanks!)

Also, as a bonus: Here’s an example where multiple drop-downs are used to select a list + sub-list/item: https://perchance.org/multiple-drop-down-lists-example#edit

There is a reason! But it’s a silly one, so discovering it wouldn’t be very satisfying ^^’

Thank you! Should be fixed now. Sorry about that - accidentally introduced that bug when fixing the null subdomain query params issue that you reported. I was adding “?” to end of the redirect URL even when there weren’t any query params, which messed with the Cloudflare cache clearing code.

Don’t know where we’d be without all your excellent bug reports 🙏

Ah good point. I think for this what I’d ideally need is a global ‘onUpdate’ function so plugins can ‘do something’ when the update function is called (as happens with the auto-reload checkbox thing). There are hacky ways to do this (effectively “wrapping” the update function), but it might be about time for a proper solution.

Fair point! I think I can fix this (using MutationObserver), but it’ll need to be opt-in (e.g. via an extra keyword like @includeProgrammaticInputs or something [but ideally shorter…]), since it’s a “breaking change”. But before I do: Another flaw is that you can’t choose to only remember specific inputs, right? My memory is a little fuzzy and I can’t see anything about that on the page or in the code. If so, I’ll try fixing both issues at once.

Hmm. Thinking about this more, I’m really reluctant to do this in case it breaks old generators - even though it’s hard to imagine someone relying on this ‘bug’ on purpose. So what I might do instead is expose a new window.generatorLastEditTime variable (like window.generatorName and window.generatorPublicId), and only enable the new behavior if the last save time of the generator is newer than today. So if people are still actively working on their generator now then they’ll get the new behavior, and if it does break something they’ll be able to notice and fix it. But for old generators, they get to keep the old behavior until the author comes back to it and makes an edit.

I think that strikes a good balance here. What do you think?

Thanks for this! I was just looking into it, and I noticed this comment at the bottom of the code in create-instance-plugin:

// Important counter-intuitive thing to take note of: https://www.reddit.com/r/perchance/comments/nh31xq/the_best_hack_for_methods_in_list_instances/gz0rebt
// the "deep" option of the createInstance plugin is kinda messed up. I should warn people that the [child] list should ONLY have properties - no sub-lists. That basically solves everything, but it's a bit annoying in many cases. Ideally I'd have only called selectOne on a list if it has no properties (i.e. with equals sign). If it has properties it should be treated just as part of the hierarchical blueprint, and those sub-items should get fixed, rather than having selectOne called on it.
// I basically need a new plugin. createInstance2 = {import:create-instance-2-plugin}
// That's the ideal solution here.
// https://perchance.org/hiad2okk9w

Which, IIUC, is exactly what you’re talking about here.

So I was reluctant to make that change back then due to potentially breaking peoples’ generators. With the number of generators that use this, it’s possible that people are “using” this ~bug. On the other hand, it is hard to see why someone would use “deep”, and not want the deep properties fixed. It does seem like the current behavior would be causing more pain to people trying to use it right now than the pain caused by breaking old generators that actually wanted random sub-sub-properties even though they used the “deep” mode.

I.e. seems like the generator would already have to be “buggy” for this change to cause any issues. Hmm. Yeah, on balance this does seem like it should be categorized as a bug, and fixed. The lower-level lists should be treated just like the upper-level lists - intuitively, that’s exactly what is meant by “deep”. Thoughts?

Thanks! 🙏 Should be fixed now.

Ohh, specifically the admin “delete” button, you mean? If so, thanks! Fixed. I’ve just placed it properly between the reply and block buttons.

No, it must be user-uploads.perchance.org URL. I don’t like seeing generators break, due to people using random file hosts that later shut down (or worse, using random links to e.g. pinterest images, fandom/wiki images, etc. which are often only temporary CDN urls), so my plugins in the future will require using perchance URL uploads in most cases.

Can you share screenshot? Not sure what you mean by message bubble buttons

Okay, I made it so it falls back to the default pattern rather than emptying the pattern in case of broken pattern. Hopefully that’s a better fallback. Thanks!