SP Campaign: A Knight's Tale

[zx_speccy_gamer]

Played it on 1.18.5 and it got out of sync, looked different (the placement of the enemies was different) and it ended after about 5 turns with a console debug kill command. Might try the campaign again on easy or wait for an update to drop.

[Lord-Knightmare]

Played it on 1.18.5 and it got out of sync,

This is expected. Since you are playing a 1.19.x save on a 1.18.x client. Both units in the game core, and the dependency add-on had stat adjustments.

Yeah, playing on the normal/challenging difficulty would be good for now. As I am still making prepping the update.

[Telfast92]

I just played “A Knight's Tale” for the first time. First of all, thank you for your great work.

In my opinion, the levels are balanced and fun, except for the last one. Unfortunately, I find the last level much too difficult.
Due to constant waves of enemies, it was almost impossible to leave the fortifications.
When I finally reached a leader, additional enemies spawned as a penalty. Without a time limit, I think I would have made it eventually, but as it was, I only managed to defeat the leader in the northwest before time ran out.

What I also found a bit frustrating was that I had already gained the upper hand in the penultimate level and had even defeated a leader (also the one in the northwest).
However, this progress was then completely ignored in the last level and I was trapped in the city.

[shevegen]

The initial scenarios were quite ok-ish.

I also, in principle, liked the scenario where one has to destroy the obelisks,
but I ended up giving up because there seemed to be so many golems and
orcs, whereas my units were kind of screwed and stuck at level 1. I also lost
the high level units in the prior flee-quickly scenario; should have had only
level 1 units I guess, but I just wanted to go past that flee-quickly scenario
as it wasn't a lot of fun.

Not sure what I would change. Perhaps make it easier to destroy all
obelisks in time before having to deal with the orcs. The orcs do too much
damage for my puny army, so while the heroes can continue to hunt down
the obelisks, they are slowed down by the golems and meanwhile the
stay-behind army at the castle loses to the orcs. In hindsight I probably
could have had a few more high level units. One thing that should be added,
IMO, is a group-heal unit. Perhaps one cleric hero that can come? Or a paladin
that can be trained up as hero to accompany the lead knight?

Also, I think it is not good level design to have multiple units of enemies appear
on the game map. Let me explain why.

In a normal scenario, I have the enemies all on the map. The enemy recruits
new units; these are on the scenario and I can typically see them, unless in
e. g. a cave.

Whereas with the scenario now, more and more orcs keep on being spawned,
often in locations that are detrimental to my own units. So I can not take
advantage of position, since the insta-spawning cancels this to some extent.
Normally I can navigate my units to block enemy units' movement to some
extent, but not when they are just randomly put onto the game map. There
are some other campaigns where this happens, even on the epic To Lands
Unknown, but here it is only spawned once. It would be better to spawn those
orc units only once rather than more than once. They have the benefit of
"teleporting" onto the map (aka being placed as-is), at the least twice, whereas
I as a player do not have this ability - all my units are on the game map already
at that moment in time. I think this is unfair, which is why I dislike this.

[Lord-Knightmare]

Released version 1.1.5 for both Wesnoth 1.18 and 1.19. Changelog is as follows.

Code: Select all

v1.1.5
--> S2: add a healer unit if you miss the bonus in S1 by chance
--> S4: there is now just one goblin wave instead of two

Next release, I will look into implementing the feature request by Telfast92.

[Sebas38760]

Hello,
I’ve made the Spanish translation for this campaign.

[Lord-Knightmare]

Gracias. I will add it to the next version once my playtesting is done.

[Lord-Knightmare]

Updated to version 1.2.1

Code: Select all

v1.2.1
--> S3: slightly easier
--> S7: slightly easier
    --> turn limit set to 60/60/58
    --> I won on "Difficult" (the middle one) on turn 54. So, I think this is doable.

v1.2.0
--> S6: improved enemy AI
--> S7: improved enemy AI
--> S6 and S7: fixed an oversight bug with AI recruitment
    --> thank you to Dalas and Telfast98 for pointing it out

v1.1.5
--> S2: add a healer unit if you miss the hidden one by chance
--> S4: there is not just one goblin wave instead of two

[shevegen]

I recently played it again on wesnoth 1.19.x.

The scenario called "Ambush" is quite difficult. Here we have to rush west while the orc
army advances from southeast and southwest.

Now it is possible to beat it; I did so before. I think the mistake I made this time was
that I had no high level dragoons or riders. These are quite useful at blocking off
orc units. But there are also some minor things I don't quite like.

One is the perpetual night. That just seems to break game mechanics and giving
the orcs a perpetual advantage. It's not the biggest issue but I did not quite like
that. An even slightly bigger issue I found was that I could only recruit 4 units per
round as we had four slots in total. I think recruiting 6 would have been nicer; I could
have gathered more fodder units that block off the orcs, thus securing my main hero
to escape to the west. I also disliked that we were limited in how many units we could
recruit. So I clicked and recruited three dragoons or so and then clicked for a fourth one
but the dragoon recruitment option was already taken and I clicked on that useless
melee sergeant guy. Who is just caught by the second orc army. And I clicked on it
mistakingly because we can only recruit three dragoon riders? I could have reloaded
of course but I just wanted to see if three dragoons are enough to break through. Well,
wasn't for me. Luck also plays a role in this and one can bait the warg riders but still,
I ended up retiring after failing for the second time here.

Not sure anything should be changed, but the scenario before this one was much
better and more interesting. The Ambush scenario is basically just a "try to ride
through quickly".

[WLFobe]

I just went back to try this scenario after some time away. I ended up deleting it. The ally's AI is just so bad that they can lose the game for the player in either of the last two scenarios. You've got a fortress. There is no way to win if your ally jumps out into the middle of the hordes of the enemies. If you were to stay in the fortress until you wore down the horde to manageable levels and then go out that would be different.

But no, they see a unit, they attack the unit, they get swarmed.

[Lord-Knightmare]

I just went back to try this scenario after some time away. I ended up deleting it. The ally's AI is just so bad that they can lose the game for the player in either of the last two scenarios. You've got a fortress. There is no way to win if your ally jumps out into the middle of the hordes of the enemies. If you were to stay in the fortress until you wore down the horde to manageable levels and then go out that would be different.

But no, they see a unit, they attack the unit, they get swarmed.

I am not sure which version you played, but the one I tested recently had the AI behaving quite moderate in defending. I believe I attached a replay file in an earlier post about me passing it on the middle difficulty.

[Lord-Knightmare]

I have updated the add-on to version 1.2.7

Key change is I edited the allied side AI for scenario 7 and just...well deleted most dumb behavior.

--> S7: Restrict allied AI
--> Added scripted instructions to strictly defend only
--> No dumb moves outside of the fortress as that behaviour has been deleted
--> Only stay instead Halstead map area

[WLFobe]

This is hilarious. I deleted the add-on from my system and reloaded it. Ver. 1.2.5. I played the first scenario and then went online to post my question below. And I saw the comment about above about ver. 1.2.7. Is there any effect to play if your game is upgraded while you are playing?

Is there any way to reset the achievements? When I restarted my game, I seem to have started with credit for three of the Loyalist upgrades. In my current playthrough I have earned none. And I have credit for 3/7 scenarios (but 6/7 are highlighted).

[Lord-Knightmare]

This is hilarious. I deleted the add-on from my system and reloaded it. Ver. 1.2.5. I played the first scenario and then went online to post my question below. And I saw the comment about above about ver. 1.2.7. Is there any effect to play if your game is upgraded while you are playing?

Is there any way to reset the achievements? When I restarted my game, I seem to have started with credit for three of the Loyalist upgrades. In my current playthrough I have earned none. And I have credit for 3/7 scenarios (but 6/7 are highlighted).

New scenario code is in effect when you load a "start of scenario" save file. Turn X saves or autosaves will not have it.

Is there any way to reset the achievements?

I asked for this feature from the dev team but it was declined. Only known way is opening the "preference" file in your user data and deleting the achievement code.

In my current playthrough I have earned none. And I have credit for 3/7 scenarios (but 6/7 are highlighted).

It is client bound actually. If you earned 6/7 for the first playthrough, you have earned for the current wesnoth1.19 or wesnoth 1.18 actually.

About the Loyalists types one, did you get all? For me, I think I gotta redo this as thing seems session specific. I got all, but no "completion". Was told that i had to do them all in one session. No client restarts. It's a bug for the devs to fix though, not me.

[WLFobe]

I asked for this feature from the dev team but it was declined. Only known way is opening the "preference" file in your user data and deleting the achievement code.

Not something I will be doing.

Thanks though. I'd like to reset many of my achievement files.