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

[Konrad2]

Another weird bug, the variable

Code: Select all

bradson_fate

disappears after S12, when you return to the inn (the fifth time you see the inn).

(Yes, this means I've almost finished the campaign. And all the side quests. The end is nigh!)

EDIT:
Fun bug in Fury and Bloodlust (24)

Spoiler:

When Totalomir has 0 hitpoints for the first time, he recovers health, right? But what if he dies because of bleeding? Now he is gone, but not recognized as dead, so you are stuck.
Skip the replay until turn 19, and then watch.
Also, the 'skeletal dragon crusher' can circumvent Totalomirs invincible, as it sets his impact res to -40%. xD

(FTR, I've finished the campaign. Thanks again for creating and maintaining this campaign, it was fun playing it, both times.)

[DrakeAdventurer]

Hello oh mighty and wonderful Ravagers creators and maintainers,

I am experiencing a bug in a scenario where the Headless Horseman appears due to my drunken stupor. Try to attack him with the heavy longbowman, and the game crashes, just before it would ordinarily ask you to select your attack.

[Konrad2]

Hey, I just had a thought:
It would be really cool if the player could access the dwarf mini campaign without having to play The Ravagers. It's disconnected from the whole narrative, and cool in and itself. Especially the first scenario.

[WhiteWolf]

It would be really cool if the player could access the dwarf mini campaign without having to play The Ravagers.

It could be done.
For now it can be launched by keeping a save from Inn-4 and launching from there. But yeah, making it standalone could be a plus.

rest of the feedback from all past posts

Not forgotten.

I am experiencing a bug in a scenario where the Headless Horseman appears due to my drunken stupor. Try to attack him with the heavy longbowman, and the game crashes, just before it would ordinarily ask you to select your attack.

Thanks for the report, unfortunately I have no idea when I can check on the issue. For now I'd just suggest avoiding to attack it that way, or if all else fails, try reloading the scenario, that way you get a different random enemy that hopefully won't have this bug.




-- Notice: I'm aware Wesnoth 1.18 has launched. (Hopefully I'll get to porting Ravagers before the next decade is out.)