The Battle for Wesnoth Forums

This is indeed a bug in the messenger AI. When considering the "next hop" for the messenger, it is not taking into account that own units might be blocking the way. Most of the time that does not matter, but you found a use case where it does. I'll fix that for 1.15.17. If you want to test...

Thanks! I can see what you are talking about now. In my case, the secondary orc does move out of the way, but the orc leader does not move to the waypoint this turn (he does, however, on the next turn). I will have to look into what exactly causes this and what to do about it. Thanks much for puttin...

I cannot reproduce this, unless I am misunderstanding what you mean. I tested things in the messenger escort test scenario and things proceed just fine even if you put escort units on the last waypoint. It is conceivable that there is a situation when all the escort units think that they are already...

Thanks. I'll fix those when I port Grnk to 1.16, assuming they are present there also. I am probably not going to update the campaign for 1.14 any more and, as another UMC author explained much more eloquently than I could very recently, I am not going to bother with making a version that works in b...

On a Mac, open a terminal. For example the one in /Applications/Utilities. Then type:

cd /Applications/The\ Battle\ for\ Wesnoth.app/Contents/MacOS/
./The\ Battle\ for\ Wesnoth --all-translations

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 ...