Children of the Dust [SP campaign for BfW1.14]

[skeptical_troll]

Hello adventurer!

Finishing "The Enemies Meet" I was told that I would start the next scenario with +100 gold. But the next scenario, not counting a dialogue-only scenario, I started with 120 gold. It seems hard to believe that the minimum gold is 20.

After that scenario dwarves and aragwaithi part ways, so that carryover refer to the next dwarf scenario. The scenario with aragwaithi only always starts with default gold.

At the end of The Gates of Aerthelka, if Formythlin tries to exit before Wahlort, he says "I can't leave! I must stay close to the gate until everyone has entered" or some such

You need to use the right-click menu and order Formythlin to close the gate while he's there. It's written in a note in the objectives, but perhaps I can make it more clear in a dialog or something.
Hope this helps!

[saturday]

Playing BfW 1.16.2 and CotD 1.0.5 (normal difficulty), the program always crashes on turn 5 of The orcs have returned.

If I don't move any units on the turn there is no crash, but if I do move during the turn the program always crashes while side 4 is active

[skeptical_troll]

I was trying to replicate the crush but I couldn't. Do you have a savefile from the beginning of that scenario? If so if you send it to me I can check if it's dependent to something happened beforehand in the campaign. Otherwise it might be some deeper bug related with the particular operative system you are using, in which case I wouldn't be able to help. The weird thing is that nothing special should happen on turn 5

[EarthCake]

Campaign choosing screen:
millennary -> millenary
(I was actually really puzzled about this one since it's correct to say 'millennial', 'millennia' (with double 'n'), but it turns out that this one you spell with only one 'n'.)
https://www.merriam-webster.com/dictionary/millenary

S1 intro:
...nations in the underground where... -> ...were

S1 ending sequence:
Walhort -> Walohrt

S2:
worshiping -> worshipping

The campaign looks cool so far, I'm looking forward to playing the rest of it.

EDIT:
S6 intro:
Walhort -> Walohrt

[skeptical_troll]

Hi EarthCake, thanks for the corrections!

millennary -> millenary
(I was actually really puzzled about this one since it's correct to say 'millennial', 'millennia' (with double 'n'), but it turns out that this one you spell with only one 'n'.)

right, and know that I see its definition, it seems that's now quite the word I needed here. It seems to be a false friend with a word in my language, so I'll replace it with 'ancient' , 'glorious' or something like that. Thanks!

[Razlobo]

Hi,

I'm new on the forum although I'm playing Wesnoth since first versions.

Writing here only to say that this campaign causes Wesnoth 1.18 to crash on 5th scenary (The Orcs have returned), like other user says, and in the last scenary (Dawn of a kingdom).

In the 5th scenary I can found the cause of the crash that occurs when you start a second fire with a miner. (I have a save from that and I attach it.)

In the last scenary I can't found the cause of the crash.

My system information:

Code: Select all

Operating System: Garuda Linux
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.6-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-1060NG7 CPU @ 1.20GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Plus Graphics

I tried 5th scenary crash even in Flatpak version of Wesnoth and it crash too. Tested too in X11 with the same behaviour.

The crash on the last scenary I only can evit jumping to 1.19 Wesnoth version, but occurs that is the turn of the 4th band, Wesnoth takes until 10 minutes to move. (The delay disspaears when units of the others band are reduced but Wesnoth 1.19 still makes some strange things.)

I can attach a save too.

I was played this campaign after, perhaps with 1.16 version with no issues, but I forgot it and replay now.

Great campaign anyway, I'll hope that you can found bugs and repair.

So many thanks.

Salud y Revolución.

Lobo.

Ps.: Sorry for my bad english, is not my mother language.

[skeptical_troll]

Hola Razlobo, welcome to the forum!
Thanks for reporting the bug and investigating the causes.

In the 5th scenary I can found the cause of the crash that occurs when you start a second fire with a miner. (I have a save from that and I attach it.)

I tried what you said but I am not able to reproduce the bug in either of the two scenarios
The two things I noticed however are

1. The units still retain the 'key' icons from the previous scenarios, they should have been removed once they open the door.
2. It often takes a long time for the enemy turn to run, so maybe it's some performance issue?

Could you try retrieving the log file after the game crashes? If you don't know where to find it, you should see the folder address through the info button at the bottom left of the home screen. Maybe that can give some hints?

[DrakeAdventurer]

At the end of The Gates of Aerthelka:

You need to use the right-click menu and order Formythlin to close the gate while he's there

I had this problem again (playing again after many years), with the right-click menu not appearing, because I had Formythlin not standing AT THE ENTRANCE, but on or adjacent to the marker. Apparently the entrance means the mountain at the mouth of the cave. I had to read the instructions a few times to notice the "at the entrance" key-words.

[skeptical_troll]

I had this problem again (playing again after many years), with the right-click menu not appearing, because I had Formythlin not standing AT THE ENTRANCE,

hmm, I see, I'll think about how to make it clearer. Any suggestions you thought about?

[DrakeAdventurer]

So instead of "at the entrance", you could say "the mountain at [X, Y]" (coordinates) or describe it as N hexes (directions) from the marker. Or you could make a signpost appear there when the lock is originally opened at scenario start.

[skeptical_troll]

I recently uploaded an updated with something like what you suggest. I hope it's not confusing anymore.