The Battle for Wesnoth Forums

To access a container you can try: wml_vars.__children['return_guardian'][0].__attributes['return_x']

I suggest to test these things interactively on the formula console (press f) in-game first. (i.e. my_leader.wml_vars will print a representation of wml_vars of the current side's leader)

wmllint runs on whatever files you tell it to. If you don't specify any path it will work on the current directory.

Note that the attributes name and address do not exist.

I don't understand what exactly the problem is.

You create an account. You log into the multiplayer and it works. Then what? You save the password and at some point the saved password does not work anymore? And if you retype your password it does not work either?

It's not clear to me why you use [variation] at all. [female] is already a variation. The usual way is to have a unit type config that describes the male version and a [female] variation but you can just as well have a [male] variation. If your variation has nothing to do with gender you use ...

Fairly new laptop. It's had graphics lags for basic things in the past, but nothing after fixing an overheating issue. It's running Xen, and I was compiling/running on a clean Debian 12 VM. Changing CPU/mem allocation and limiting to a single core didn't change anything, and little else was ...

Indeed, this solution is not efficient compared to compiling Wesnoth to wasm directly using tools like emscripten. However, the latter seems much more challenging.

I do find one website by an ai company that compiles Wesnoth to wasm. But I cannot find its source code, nor the web files.

They ...

Summary: slowness introduced in 1.19.6, tracked to 12fa8f28447e21e7522dba608034a08b984c05ac

To reproduce from attached save game: end turn 7. The AI will (long) pause before its next move, and (less long) between moves.

Description: seems to occur when there are many combat options for the AI to ...

There is code in Afterlife Random, which was played here, that uncovers leaders so no ambush happened.

Similar code is in the original Afterlife: https://github.com/vgaming/afterlife/bl ... ua#L91-L93

Avoid using sdl2-compat and use actual SDL2 instead. There are many reports of crashes with sdl2-compat (a wrapper around SDL3 that mimics SDL2).

Just to make sure you are using the development version? Ideally 1.19.20?

The sand boxing issue is only on the mac app store version. Starting wesnothd works just fine otherwise.

You're supposed to give scenario files a .cfg extension. The current editor should not let you save scenario data as .map.

Without seeing more details who knows. I suggest starting with something simple and just open a PR.

Not much point in a debug build when you have the exact line number of the "crash". Doesn't happen for me though so the question is how to trigger the assert.