Colbex

Happy Birthday!

Yeah. I used to play TNRPG a lot. I'm a C1 vet. I had BBE back then.

That's... I didn't follow any of that. I'm just glad I found the answer before having to wade through all that thinking it might help.

I've also extensively modified the scripts too to incorporate a different control style (sorry, no spoilers, but it's good!), so it may have been that any answers wouldn't have helped me in my situation anyway.

Humour me...

I solved it just now, actually, while replying to you. Turns out Ruby is weird, and if a variable is defined within a block (e.g. a "do" loop), then it becomes undefined again once you exit that block. The solution is to define the variable before the "do" loop begins (i.e. copy the line "ret=false" to before the "do" loop), and then it'll be usable after the loop finishes.

It's not a bug as such, because sometimes programmers will want to use that property of blocks (e.g. use the same name for two different variables, one of which is in-loop only and the other is out-of-loop only), but in those cases I think it's just bad programming style.

I considered this possibility before, but I dismissed it because it was a stupid thing for Ruby to do. Turns out that's how it works.

So yeah, it's fine now. Thanks for the offer of help anyway. Might be interested to see what you came up with, though, if you want to PM me your working.

"Best of luck on your project, although, this seems to me like one that'll become popular."
How did you know xD?

No problem. Just pass on the good deed, if you can.