The Battle for Wesnoth Forums

No worries, I'm glad to hear that that worked. There are a whole bunch of reasons why this might have happened, and it's probably impossible to figure out after the fact. You may now also be able to leave fullscreen mode, resize the window, and then use it in windowed mode again (as long as it's not...

No, no editing. Just open a terminal (e.g. from Applications -> Utilities -> Terminal) and then enter those two commands.

I thought that's what you had done to get the log in the first place. Apologies if I misunderstood.

One thing to try, given the error message, might be to start Wesnoth from the command line in full screen mode. For some reason Wesnoth seems to remember a window size for you that appears too small to open one of the dialogs. Repeat the same two steps you used to get the log, with a minor change (t...

I finally got around to dealing with this and have created a pull request with the suggested fixes to the retreating behavior. The default behavior is different and there are now two additional AI aspects with which the retreat behavior can be customized, retreat_factor and retreat_enemy_weight . Yo...

In principle it should work in a prestart event, I think, but then it will be lost if you start from a not-start-of-scenario save.

Where did you put the [lua] tag? In the Simple Attack MAI test scenario (which is where the code example on the wiki comes from) it's in a preload event.

There are at least 3 ideas of how to connect with an external AI listed here. But which one is the easiest/best? Are these methods still viable? Will they work in future Wesnoth versions? All of these methods should still work, and continue to work with future versions. As for which one to use, tha...

First, sorry for taking so long to reply, I've been away for quite some time. I'm still not fully back and don't know when, or even if, that is going to happen, so any non-trivial progress might be slow. Second, just for the record, you can still use the 1.14 AI in MP (in the computer player selecti...

Lord-Knightmare wrote: ↑November 26th, 2020, 11:36 am 7. Fix the Lua Error I reported.

This is now fixed in bf3cdeb1. Thanks for reporting.

Konrad2 is very polite in not mentioning who his anonymous helper is, so I'll own up to it. You can direct the blame my way. ;-) I have in the meantime checked out the situation and can confirm that the retreating candidate action is most likely what causes this behavior in 1.15. So removing the CA ...

That should be possible to do, since it'd essentially mean the AI should highly prioritize units that are about to level up rather than avoid them, but I'd need to ask mattsc to know for sure. Units about to level up are already prioritized by the high_xp_attack candidate action. We need to find ou...

If the Fast MAI is enabled, you should see the following in the AI Component Structure inspect dialog for the side (scroll down to the bottom). Note the three candidate actions starting with "mai_fast_".

Really quick update: Pentarctagon did the bisecting, and gfgtdf fixed the bug in this commit. The error was only triggered when it was an AI side attacking another AI side and when the unit leveling up was the defender, that's why it was hard to track down.

Hi vghetto, Thank you for putting that demo together, that's been very helpful! I may open a github issue for it later. For now, I'm still looking into what might be going on myself. So far I can tell that the problem appears to have been introduced somewhere between the 1.15.2 and 1.15.3 releases. ...

Hi vghetto. Thanks for the save. I can reproduce the error now and have started looking into it, but I do not understand what is going on. The error happens at the end of attacks on units that are 1 XP from advancing, but the attack (and the advancing afterward) seems to execute just fine. Strangely...