Hi! Without looking at the full code you had it's hard to see what went wrong, but you'll want to put quotes around "elementname (Hydrogen)". Since you're already "within" quotes, you can use single-quotes like so:

I just changed elementname (Hydrogen) to 'elementname (Hydrogen)'. Note sure if that'll solve it for you, but you might also like to take a look at the tooltip plugin: https://perchance.org/tooltip-plugin

Ah, yeah, it currently caches 2 results from each generator so it'll grab an hour's worth of tweets the first time you create the bot. So if you edit your generator on Perchance, those edits should propagate to your Twitter bot within an hour or an hour and a half. I've added a note about this on the create-a-twitter-bot page. Strange that Zapier doesn't like the &nbsp; character :S You could do something like this:

botOutput
[output.evaluateItem.replace(/&nbsp;/g, " ")]

since Twitter (unlike HTML) should respect multiple adjacent spaces (I'm assuming that's why you're using &nbsp; in this case) and you can add further replacements like this:

but note that the replace(...) function/method accepts regex as the first parameter, so you need to watch out for special regex characters (e.g. . means "any character" and .+ means "one or more characters").

u/abhoriginal Let me know how it goes! P.S. Your username could be taken the wrong way (abhor + aboriginal), so it might be worth starting over with a new Reddit account since your account is new and I'm sure that's not what you were intending :)

and then it should work since you've already got hue-rotate([hue]deg) in your code. The only down-side id that you need to click the randomize button to see the new color (it doesn't update live as you move the slider). It would be possible to make it "live", but it would be a bit harder.

Ah, so I'm pretty sure the problem here is that {Hill Dwarf|Mountain Dwarf|Duergar} is counted as a list, so when you call r = PRace.selectOne, lockableList(r) and then let's say Dwarf gets selected, then the lockable list plugin selects one item from the Dwarf list to "lock" on to, but there is only one item in the Dwarf list: {Hill Dwarf|Mountain Dwarf|Duergar}, so this gets selected and stored as the locked value. So now every time that r lands on Dwarf the lock will return {Hill Dwarf|Mountain Dwarf|Duergar}, and one of those will be selected.

When I made lockable-list, I really only intended for it to be used with plain old lists - not hierarchies with properties and stuff like that. locker-plugin was made with more complex use-cases in mind, and once you get the hang of it, it's actually much easier to deal with than lockable-list-plugin.

Hi! Whenever you need to generate something random based on something that you've already generated, "dynamic sublist referencing" tends to come in handy. You can learn about on the examples page. So a good approach is probably something like this:

You'll need to adapt that to your particular use case, but that should get you started :) I'll paste the code here as well because why not:

output
A resident from [c = city.selectOne], [c.state] has an income of approximately $[state[c.state].income].
// The `[state[c.state].income]` part means "get the sub-list of the `state` list called '[c.state]' and then get the `income` property of the result"
// Read the "Dynamic Sub-List Referencing" section of the examples page to learn about this: perchance.org/examples
city
Los Angeles
state = CA
New York
state = NY
San Fransico
state = CA
Austin
state = TX
state
CA
income = {100-120}
NY
income = {100-110}
TX
income = {90-120}

This is most likely just because you misspelled the locker name ("G1") or because you haven't yet put a value in the "G1" locker yet. Before writing [locker("G1_button")], you should have [locker("G1", someValueYouWantToStoreInG1)] somewhere before it. Hope that helps!

Ah, so the problem here is that you're creating a new consumableList each time. Instead you should create one consumable list (called ZEC in the example below) and then pass that to the fixedUntilReload plugin 3 times:

and that will remove the lag at the start that causes you to be able to see the [o = output.selectOne.evaluateItem] text before it is "filled in" by Perchance. The delay is more noticable for users that visit the template for the first time because the tippy library hasn't been cached by the browser yet.

Ah, so the exponentiation operator is actually **, so 2**3 = 8 and 10**3 = 1000, for example. Sorry about that - it's not documented anywhere on Perchance. It is documented at these places though, since Perchance is based on JavaScript:

The ^ operator is actually a bit-wiseXOR which is why it was giving you weird numbers. I admit that it's a bit counter-intuitive, and I'd definitely change it if I could, but its something that's built into the JavaScript engine and so it can't be changed :[

Great to hear! Unfortunately there's no way to copy the whole page other than print-screen, but I've just added a feature so you can double-click on the generated image and it'll open it in a new tab at full resolution, and then you can right-click and download it from there. Not an ideal solution, but there are some technical problems which are preventing me from adding a nice simple download button.