Lemma Soft Forums

I had a problem like that a little while back - I solved it when I realized that I originally defined the variables in an 'init:' block. Making sure they were defined as 'default' solved my problem. (Note: If you're doing serious Python coding, you might need to declare the variable twice - once as...

I've noticed that some varialbes I'm setting don't seem to be participating in rollback properly, leaving to unexpected behaviour when rolling back and forth. They are arrays in a particular namespace, and it appears they are unchanged by rolling back. I've tried making a toy example, but can't repl...

Ok, many thanks, I think I've got a better handle on what's going on. With some significant experimentation, I've got it behaving. I think my problem was how renpy.show parses the arguments; the image you use can be given as a string that names a renpy image object, but you can't do the same thing f...

Okay, so to do that: How can I get a Transform object (which is what the at_list is expecting, based on the error message) when the Transform is defined in a renpy statement? or How can I define a Transform object in a python block? It looks like a Transform object is specific to a child displayable...

Well, the random part isn't actually relevant; what I'm having trouble with is duplicating:
in a python block, as I don't think renpy statements support lists (or, at last, I can't find a way to define such lists in a renpy-friendly manner).

I'm having difficulty getting my head around some the proper python statement equivalents. I want the python equivalents in order to avoid a 100-branch ifelse tree. init: image image1="someimage" image image2="otherimage" $ image_array=["image1","image2"] transform pos1: xalign=0.2 yalign=0.5 transf...

Hmm, that doesn't seem to work with the implicit say or menu statements, although I suppose it might in other places where you might use interpolation.

Ah, well, I can live with that. Just wanted to make sure I wasn't missing a cleaner way of doing it.

Cheers!

This doesn't seem to work: $ somearray=['A','B','C'] $ someindex=2 "[somearray[someindex]]" with: File "game/script.rpy", line 68, in script "[somearray[someindex]]" TypeError: list indices must be integers, not unicode If there a way of achieving this that doesn't involve creating temporary variabl...

Monochrome would definitely remind people of manga. I'd say go for it, if you think it fits. It'd be something different about the game. I'm a sucker for high-contrast inked work. You could use colour super sparingly, to suggest particular themes (Schindler's List style). Or tint the entire scene wi...

The menu choices must begin with strings, showing what the choice is. If you want a condition on when the option appears, you put the if statement afterwards: "build a hut" if wood >=10: ... It gets called an indentation error because ren'py's best-guess as to what you were trying to do is that the ...

Yeah, ren'py reloads scripts and resources and tries to carry on from the previous position, but it doesn't always do so perfectly. For example, if you added the line that defined 'password', then reloaded, then the variable would not be set because it wasn't in the array of stored values before the...

Yes.

Worst-case scenario, you would need to find a midi->ogg converter and convert it yourself, something like this: http://audio.online-convert.com/convert-to-ogg (Note I do not recommend them, they were just the first google hit that came up and they seem to offer what you would need).

Not sure, but I think the nulls in there are the problem.

Instead try: And the same for the other use of null.

By default, when ren'py reaches the end of one label, it will carry straight onto the next one. Screens are probably not the way to approach this problem, actually, at least as a novice. the menu command offers choices and handles different branching, with simpler syntax. living_1: menu: "right": ju...