The Battle for Wesnoth Forums

BLIT works on images, not animations. So no.

Since the default defend animation is pretty formulaic, you might be able to get away with just substituting $this_unit appropriately into the definition of the DEFENSE_ANIM macro (which requires you to use [modify_unit] to add the animation), and otherwise do just as I described above. However, it ...

The [animation] tag doesn't support "apply_to." …what are you talking about? Yes it does. The [animation] tag is rarely actually used for animations though, so you won't see it very often. None of the animation tags that are generally used support apply_to – only [animation] specifically....

Thank you. If you could get that info onto the wiki, I think it would help a lot. Or maybe it's there and I skimmed the page looking for what I wanted instead of reading from start to finish. I added more info clarifying that the content of [if] is the same as the content of the toplevel animation,...

I agree, a variable condition with no valid condition should raise an error, not simply return always true.

1) The only thing I see for the animation-if is hits=yes|no. I can't find a list of conditionals. Is there a list? My understanding is that the content of the [if] and [else] subtags are essentially just an animation – that is to say, anything that can be put at the top level of the animation can a...

You could combine the graphics for the two overlays in any decent image editor, …why would you do this? Just use both sets of graphics for your custom terrain. But in this specific case it's even easier, because one of the sets of graphics is nothing (except for the editor overlay), so you can pret...

Celtic_Minstrel wrote: ↑April 17th, 2024, 1:10 pm I recommend you look at the file gui/dialogs/wml_message.cfg in the Wesnoth data folder to see how the WML message actually does it.

Look at how it's done there. The variables in question are used – specifically, look at where x, y, width, and height are set in the resolution tag.

You're right, the issue doesn't have anything to do with WFL. It just happens to more frequently come up with WFL for various reasons. I'm thinking something really simple like: #define MY_MACRO "bar"#enddef [message] speaker=harry message="foo {MY_MACRO}" [/message] Yup, that lo...

That's technically true, but you, personally, don't need to know those numbers. There are variables in the GUI2 positioning system that already contain the correct numbers. You may also need the height of the menubar, which strangely isn't in a variable (it seems to be 30). I recommend you look at t...

You can display dialogs on top of each other, but only the one on the top can be interacted with, even if it's completely transparent.

The Lua API only lets you use a single [resolution] (you pass the content of that tag to gui.show_dialog ). You could of course have your own logic to choose between resolution tags, though I think you don't have access to the screen size… So in other words, you can't use the [window] tag for a Lua ...

I'm pretty sure there's no need to do that. There's allowance in either [window] or [window_definition] for specifying where the dialog window should appear on the screen, so you really just need to work out the right numbers or formulas to get the effect you want. (If it's in [window_definition] yo...

WML has very few special characters. Any character that appears after the = , with a few exceptions, is considered to be part of the value of the attribute. It doesn't matter how convoluted it looks or how many punctuation characters appear in it – as long as none of the special characters appear, i...

Don't worry, there are people experienced with WML who are also confused by this.