The Battle for Wesnoth Forums

- In scenario 8, where you get to recruit four Spearmen/Bowmen, I don't think that the "limitations of the Wesnoth engine" mentioned in this immersion-breaking comment on the objectives screen exist any longer (since there are now separate recruit and recall events): - In scenario 13, the...

Another issue: Lorin has Skirmisher at level 1 (manually given by 01_Breaking_the_Circle.cfg), loses it at level 2, and then regains it at level 3 (since the L3 Queen unit type has it.) Thanks for report. I've fixed it by making all Lorin levels SKIRMISHER by default. But I'm not sure, if it is goo...

Elvish Pillager wrote:

tapik wrote:It works fine on my 1.8.0 on Linux (current version 1.1.93), but I do not change this scenario.

I am also on 1.8.0 on Linux, and it doesn't work with 1.1.93. Huh.

So please send me your save from the beginning of the scenario and I'll compare them. May be any stored variable do this...

I'm glad ANO is being maintained again. It is, without hesitation, my favorite Wesnoth campaign ever. Issues so far: - In scenario 8, where you get to recruit four Spearmen/Bowmen, I don't think that the "limitations of the Wesnoth engine" mentioned in this immersion-breaking comment on t...

I've reported the problem as a bug and silene has fixed it
So from 1.8.2 can everybody use kill under recall, but till the release I have to workaround it

... [store_unit] [filter] side=1 # or whatever is the side of the player x=1-15 # put the size of the map here! It's to say "on the map and not in the recall list" y=1-15 # put the size of the map here! It's to say "on the map and not in the recall list" canrecruit=no # remove t...

on scenario 16 "Choosing the Best" I replaced name=recruit with name=recall and it still does not let my veterans move after recall; only my new recruits can be moved. Currently the Separation makes my Linux segfault. There are some problems with combination of recall under recall. I'm tr...

on scenario 16 "Choosing the Best" I replaced name=recruit with name=recall and it still does not let my veterans move after recall; only my new recruits can be moved. Currently the Sepration makes my Linux segfault. There are some problems with combination of recall under recall. I'm try...

... [store_unit] [filter] side=1 # or whatever is the side of the player x=1-15 # put the size of the map here! It's to say "on the map and not in the recall list" y=1-15 # put the size of the map here! It's to say "on the map and not in the recall list" canrecruit=no # remove t...

A New Order contains a macro CLEAR_RECALL, which in loop recall unit using recall and clear the unit: [...] So do you know any workaround for this? If I've understood what you wish: why don't you simply [store_unit] the whole Recall list (with kill=yes, thus clearing it) and then [unstore_unit] on ...

Actually, you should probably disallow recruits, too (or better yet, copy the same event also for recruiting). You can now first recall 11 troops, then recruit 2, and finally recall the last one. This way you get two more troops to your recall list (the recruited ones stay on the recall list, but d...

A New Order contains a macro CLEAR_RECALL, which in loop recall unit using recall and clear the unit: [do] [recall] side=1 x=1 y=1 [/recall] [if] [have_unit] x=1 y=1 side=1 [/have_unit] [then] ... The problem is that a recall is called in recall event. [recall] tries to recall already recalled unit ...

turist wrote:In ano-16.cfg replace name=recruit by name=recall

Thanks, the same bug in Separation, fixed in 1.1.91-1

Theron wrote:Here are my files: ANO for Wesnoth 1.7.8 (based on ANO 1.1.6)

Thanks a LOT!

Theron wrote:And the background of the portraits need transparancy.

I don't think that a simple backgroundization will work. But I have an idea...

Theron wrote:Hello Tapik,

I once had ANO running under Wesnoth 1.7.8.

And you lost ANO with changes, am I right?

Thanks for your hints, especially about the units.