Weird *else fallout, unsure where it's originating from?

[Niki_Christopherson]

@Havenstone

very quick to write if you’ve got a macro that serves you multireplace

I’m curious what you mean about this.

@Nocturnal_Stillness

Does this work? Shouldn’t low be a number? I.e

*set bloodthirst %+10

Or something like that?

You can find out more about how I set this up here:

Diving Into Numerical Relationship Values (For The Numerically Challenged)

Similarly, you can also create variables to hold the values you want to test against. This helps you ensure consistent difficulty within a scene or chapter, lets you ramp up the difficulty over the course of the story, and makes it much easier (possible at all, really) to adjust the difficulty across the board if you find it needs tweaking once you start testing. *create AWFUL 25 *create BAD 35 *create DECENT 50 *create GOOD 65 *create GREAT 75 *if stat < AWFUL ... *if stat < BAD ... *elsei…

@Havenstone

I think this is actually a good example of why Dan has always been wary of Implicit Control Flow

To be frank, I’m wary of Implicit Control Flow too. I’m really not a good enough coder to be able to find these errors on my own, and to not have that warning there, it’s worrisome. And while ICF is helpful, I feel like the worry is that it could cause game-breaking bugs without my knowing about it.

@jojo

half-empty multireplaces

I just found out that these exist and are useful, so I’m not super afraid to use them.