The Battle for Wesnoth Forums

dialog.autorecall_tv[i].ar_up.on_button_click = move_up(i) No, what are you doing. That won't work. You can't call the function and assign its result as a callback. Just assign the function directly: dialog.autorecall_tv[i].ar_up.on_button_click = move_up If the issue is that your function needs a ...

There's no facility to disable saving. That goes against the spirit of the game.

The title of this topic is wrong. It should not be "How to modify wesnoth save files?" but rather "How to make an event one-time-seen?". You've started by deciding that you know the correct way to approach your problem and asking how to achieve that approach, rather than presenti...

I'm looking for samples of WML where the preprocessor or parser does something a bit unusual that you might not expect, or where you need to do something a little unusual to make it work correctly. Does anyone have any examples of such things? I'll start with one that I recently noticed: [my_tag] va...

However I am consufed because previously, re. the lua method, you said: That code doesn't clean up after itself though, so it'll leave all those variables littering the global scope when it's done. I'm not clear what you mean (sorry to be dim). By all those variables do you mean: These are WML vari...

I think the [data] support is missing a piece. It probably should be exposed either as something like $event_data or by injecting its contents as temporary variables. Your second attempt used the correct syntax, so if $event_data existed, you should've been able to access the sent variable as $event...

That's not even a village anymore, since you removed not only heals=8 but also gives_income=yes. If that's what you wanted, then that's fine, it just didn't sound like it was.

Just letting you know that I pushed several fixes to #7359, including the gui.simple_widget.label change you suggested. I also added |number to it, as there are probably use-cases where you want a label to just show a number, and we don't currently have functions to convert a number to a tstring.

You can also put [set_variable] inside [modify_unit]. That would change Ravana's example to this:

You can pretty much copy the feeding Lua file and customize it however you want. In this case, just deleting the test that the killed unit is not unplagueable should be enough.

It's probably better for gui.image to override the field to string, I think. Though I guess that doesn't really solve the issue of getting a warning when you assign it… I guess I could make it string|tstring…

Another one : it seems that the definitions for interface.remove_item interface.add_item_halo are missing in wesnoth/interface.lua Those ones are a little weird. They're actually defined in lua/wml/items.lua, since they access local variables in that file. I'll make the other corrections you noted....

I wouldn't recommend just taking #7359 wholesale, as some of the changes to code seem to be incorrect. Cherry-picking all the [LuaDoc]-tagged commits should be safe, however.

Those annotations are used throughout the parts of our Lua API that are implemented in Lua. The engine does nothing special with them, however – it's up to you to choose an editing program that supports them and set it up to recognize them correctly. I know Visual Studio Code's Lua plugin supports t...

wesnoth.current.event_context is all the information about the currently-running event.

I don't understand what the second line of your post means.