The Ravagers - SP campaign for Wesnoth 1.16 [Feedback and development]

[BTIsaac]

It was 1.1.0 upon porting. To me, this sounds like you updated to 1.1.14 right after starting the game, that is why the heroes who appeared before this point (Dothar, Gallien, Elvyndiel) are bugged from the initial version, but those who appeared after (Maggoth, Tharos, and those who are to come I suppose) are fine.

I recall downloading it along with A New Order (I know because I noticed they use the same music pack), then I spent weeks playing A New Order, started playing this, and immediately after I started up and finished the first scenario, I realized I probably should update. Yeah, that must've been it.

Anyway, fixing manually right now.

[WhiteWolf]

Sounds good Let me know if there is anything else fishy.

[Konrad2]

Just a small thing, but the campaign awards (most times) the wrong laurel/wreath upon completion. (Apparently caused by using the old difficulties syntax.)
Details as to why and how to fix it can be found in issue #3983.

[WhiteWolf]

Thanks for the heads up I'll address this in the next version.
(Sorry for the late response, I was absent for the weekend)

[WhiteWolf]

Double post because of the update of 1.1.18.
Nothing particularly new, only two new whess cards, but there are a couple of bugfixes, including the laurel fix.

Changelog 1.1.18:

- Two new whess cards: Impenetrable fog and Preachers of Faith
- Fixed armament of slaves to Footman
- Fixed Dayton's runoff point on FoV-5 if finished early (impossible to pull of, but a theoretical bug nonetheless)
- Hardwired Maggoth's traits to Weak and Loyal
- Updated the difficulty codes of to game, so that the correct laurel is awarded at the end of the game
- Some updates to the code

Cheers

[Mathel]

Hello.
I have noticed two strange things today in the add-on.
In Interception, I was intercepted by a Soulbeast. I had a ghost finish it off, and the phantom (it leveled up) is now named "the Nemesis of Orcs".
Koash Graet got that title from killing an orcish emperor earlier, so I find it strange that one would get it from a soulbeast.

Second is spoilerific, so I will put it in a spoiler.

Spoiler:

In Nemesis, I encountered General Isurdiel again. He started the scenario bleeding because the last time I met him I made him bleed.
It may be a good idea to not just restore his HP, but also remove any statuses when unstoring him.

[WhiteWolf]

Hello

In Interception, I was intercepted by a Soulbeast. I had a ghost finish it off, and the phantom (it leveled up) is now named "the Nemesis of Orcs".
Koash Graet got that title from killing an orcish emperor earlier, so I find it strange that one would get it from a soulbeast.

Apparently there's a typo in the code, and a wrong title is given if the Soulbeast dies while being the defender. Feel free to rename the unit to "the Soulkeeper", that is the title that should have been given.

Second is spoilerific, so I will put it in a spoiler.

Spoiler:

In Nemesis, I encountered General Isurdiel again. He started the scenario bleeding because the last time I met him I made him bleed.
It may be a good idea to not just restore his HP, but also remove any statuses when unstoring him.

And that's missing as well, yeah.
Thanks, the issues will be fixed in the next version

[WhiteWolf]

1.1.19 is out It brings some minor bugfixes, including the ones mentioned above, and a few interface and sound effects improvements, and improvements to Whess's AI.

Changelog 1.1.19:

1.1.19
- Included the forum topic to the campaign description
- Whess: added sound effect to some cards
- Whess: on difficulties harder than easy, the AI leader will no longer leave it's castle in offense
- Whess: the AI may now use it's leader card any time between it's moves (no longer only at its turn start)
- Fixed missing weather effect animations if Whess is started right after finishing a sidequest
- Fixed wrong hero name for killing a Soulbeast
- Fixed Isurdiel not correctly resetting at map 12

Developer's notes on 1.2.0's probable release in August:

It has been a little quiet here for a while now, and recent bug reports have luckily been rather short The game is arriving at a nice, stable state, ready for 1.2.0.
The 4 unfinished and yet unavailable sidequests are not forgotten, but I won't have any time to spare for it up until July. Hopefully then, I can finish at least 3 of them in late August. But we will see.
Until then, sadly, the campaign is only being maintained, with very small occasional additions.

[RainerT]

Hi,

I noticed the conversion of the slaves in scernario 5 doesn't work as intended. According to the description they keep one trait and get loyal. However, the second trait is still valid. I also found a unit where the trait in the description doesn't apply at all. It has the quick trait, but still 5 movement points.

Wouldn't it be a better idea to let the slaves start with only one trait, if this is possible? This might avoid the problem with the conversion and from a player point of view, you know the type of trait the loyal charachter has. This way you can better choose a proper unit type in case of the male slaves.

[WhiteWolf]

Hello,

Wouldn't it be a better idea to let the slaves start with only one trait, if this is possible? This might avoid the problem with the conversion and from a player point of view, you know the type of trait the loyal charachter has. This way you can better choose a proper unit type in case of the male slaves.

It would definitely be a better idea. I switched it to this system, this will be the way it works after the next version

[WhiteWolf]

And, released 1.1.20 with the mentioned improvement, some other bugfixes, a redesign of Whess's AI (see spoiler) and a minor addition to the story, making a decision a choice for the player.

Changelog 1.1.20:

1.1.20
- Whess: leader-card playing AI rehaul: now playing the leader card is not done through events but is an actual move for the AI (like a regular move of a unit). This also retains the fact that the AI may play its card any time during its own turn.
This brings a better balance between what the AI can do, and what the player can do. For example, in earlier versions the AI could counter applied weather before taking initial damage, whereas the player was never allowed this. This kind of inconsistency is gone - the AI can only play its cards as a human player could.
The AI also gets "more clever" with difficulty, hard and nightmare AI will try not to throw away its cards at the first given opportunity, but use it as much to its advantage as possible.

- Wulfius and Wolfras now only stay with you if you allow them to stay.
- New Whess card: Leadership
- Whess: Tidal flood now creates Soulless instead of WC.
- Whess: Fixed plague units
- Slaves now only have one trait, and retain that during arming them.

[BTIsaac]

So this just happened to me. I just played 16 - The Wail, and a legendary enemy spawned. Not sure if this was fixed or not, because i haven't updated the game since last time.

[WhiteWolf]

16 - The Wail, and a legendary enemy spawned. Not sure if this was fixed or not

No, that is still live in the current version. However, I fail to see why that is a problem. Yes, the point of view belongs to a different character on that map, but it is still Dayton who is narrating (something previously narrated to him by someone), at the Inn. So I don't think it's out of viewpoint that Dayton is commenting on the spawning of a legendary enemy. It's not out of context either - why wouldn't a drunk Dayton decide to spice up a story previously told by someone else?
Yeah, gameplay-wise you may feel robbed a little because you don't get to keep the unit that kills the legendary enemy. However, it's just a title (and the lvl 5 XP) that's "lost", you still retain the intoxication reduction reward. By the way, in the long run, this is the same as with the side-quests that allow drinking.
In conclusion, I don't think that map should be excluded from the list of those that allow legendary enemies. There are many that are, but I don't see why this map should be.

[BTIsaac]

Yes, the point of view belongs to a different character on that map, but it is still Dayton who is narrating (something previously narrated to him by someone), at the Inn. So I don't think it's out of viewpoint that Dayton is commenting on the spawning of a legendary enemy. It's not out of context either - why wouldn't a drunk Dayton decide to spice up a story previously told by someone else?

Actually, the enemy spawned was the orc emperor, which specifically adresses me as Dayton Blackwood, and Dayton describes him as someone he fought before.

You still retain the intoxication reduction reward.

Actually, i didn't get the reward, because the scenario ended before he reached me. The enemy heroes reach me before he does, and when they do, it's pretty much over.

Now, I haven't encountered a single legendary enemy until 13, despite Dayton being almost 90% drunk at all times. I figured if there are missions where it makes sense for legendary enemies to not spawn it's the plot-heavy ones, and the flashbacks. Especially the ones told from the perspective of the bad guys.

[WhiteWolf]

Actually, the enemy spawned was the orc emperor, which specifically adresses me as Dayton Blackwood, and Dayton describes him as someone he fought before.

Oh, I haven't considered that. Yeah, that's quite a strong point against having them there.

Actually, i didn't get the reward, because the scenario ended before he reached me. The enemy heroes reach me before he does, and when they do, it's pretty much over.

That's also a point. If Addicus is faster than the epic boss, then it's definitely another issue.
I'll see what I can do, but probably I'll add the map to the blocked list then.

Now, I haven't encountered a single legendary enemy until 13, despite Dayton being almost 90% drunk at all times. I figured if there are missions where it makes sense for legendary enemies to not spawn it's the plot-heavy ones, and the flashbacks. Especially the ones told from the perspective of the bad guys.

That's strange. If Dayton is drunk, you should first encounter epic enemies on map 12. Here's the list where epic enemies are allowed:

List of blocked and not-blocked maps up to 16:

It is a general remark, that epic enemies are usuallly not allowed on a map where there are 2 or more opponent sides, and they fight each other as well. This is done in order to avoid having the epic enemy killed by another AI. This is reason #1.

Inn 4 - drinking is introduced
10 Dwarvish Mines - blocked: I found this map is already twisty enough, and the unit could always spawn too early, behind a wall you've yet to blow up. It's just not right.
11 Forbidden Memory - blocked: and come think of it, must be blocked for similar reasons map 16 has...
12 - Face of the Enemy: allowed.
13 - Orcish Vanguard: allowed.
14 - Ancient Battlefield: allowed
15 - Prison of the King: blocked for reason #1. Trolls and undead fight each other.
16 - The Wail: Allowed in 1.1.20, will probably be blocked from now on.