The Battle for Wesnoth Forums

Cant explain why it works but it does # lua wesnoth.require("wml-utils").handle_event_commands(wml.load("~add-ons/EventLoader/action.cfg")) [lua] code=<< -- to make code shorter local wml_actions = wesnoth.wml_actions -- starting values local font_size_title = 70000 local font_si...

> N_("This unit is unhealable. It cannot be healed by healers or villages and doesn’t benefit from resting."));

[heal_unit] is not one of conditions mentioned.

Should be healed.

You need to use string concatenation then. Instead of f((image_original_width < 300) having f((]]..tostring(image_original_width)..[[ < 300) for example.

I cant tell if the wml you posted is expected inside [image]. By syntax it seems possible.

local image_original_width = ...
local image_original_height = ...
local portrait_mirror = ...
local portrait_image = ...
are not doing anything.

Now that you have wml you can use wml.parse # lua wesnoth.require("wml-utils").handle_event_commands(wml.load("~add-ons/EventLoader/action.cfg")) [lua] code=<< x = wml.parse([[ h="( if((image_original_width < 300) and (image_original_height < 300), image_original_height, ((i...

Start by creating unit types.

First get rid of macros, run preprocessor on them. Then convert macroless WML to Lua, by wml.parse or manually as fits your situation better.

[filter] x,y=$x1,$y1 [/filter]

Is always passing, so you can just remove that.

id probably means it wont give you 14 damage.

{~add-ons... is not linking, it is telling wesnoth to take data from there and put into current line. The instructions are carried out in the order written, so if {~add-ons/A_Addon_Test/scenarios} depends on {~add-ons/A_Addon_Test/utils} then {~add-ons/A_Addon_Test/utils} needs to be in earlier line.

It might be useful to wrap wml.load in wml.tovconfig if there is interest to use $ variables.

:alias e=lua wesnoth.require("wml-utils").handle_event_commands(wml.tovconfig(wml.load("~add-ons/EventLoader/event.cfg")))

Add [fire_event]name=teleport[/fire_event] after you teleport units. If you mean ability then enter hex should work.

Assign them with the API you have available to create wml variables. Including wml.variables if you prefer. Those like set_variable, set_variables, wml.array_access.set, wml.array_variables, wml.variables_proxy.

You cant put them to wml.variables. You can think of wml.variables as function, not as table. It reflects state of wml variables, but itself is not wml variables.