1.18 Saurian Campaign, Vendraxis Prophecy

[Refumee]

Thank you for your feedback. I consider it.

I check the code, when I'm back from work.
For now it would be better not to continue, until the next version.

What version of my campaign you are playing on?

[bssarkar]

Thank you for your feedback. I consider it.

I check the code, when I'm back from work.
For now it would be better not to continue, until the next version.

Okay, will wait for next update.
Meanwhile I've attached correction for scenario 2 and 3.
Also, I don't understand what this means so couldn't rewrite it :
S3 :

"I'll consider the dwarves and the goal, they look very close."

What version of my campaign you are playing on?

1.1.6

[Refumee]

Thank you
If you are on 1.1.6 you can continue. This is a stable version for 1.16 Wesnoth.

"I'll consider the dwarves and the goal, they look very close."

The proximity of the dwarfs to the goal is very close.
If the dwarfs see you they will recruit and attack, that will make reaching the goal more difficult.
It should be a hint for the player. Bad wording.

I will fix this sentence.

[Refumee]

Scenario 1 : Seemed fine. The player can probably get away by spamming ranged units (young saurian not needed), since all the units the Scorpion recruits are melee.
Perhaps this can be reworded :

Zanza has just finished her exam and succeeded

like this :
Zanza has just succeeded in her exam
Unit art for Saurian Wise is missing. See the screenshot.

I reworded it. It will be updated soon. As I can see, you build a lot of lvl 0 units. Hhmm maybe I remove the loyal tag from them. It seems a lot.
The Saurian Wise is a strange one. In my Version he is there. So sadly I don't know, what to fix.

[Refumee]

Thank you for your feedback. I consider it.

I check the code, when I'm back from work.
For now it would be better not to continue, until the next version.

Okay, will wait for next update.
Meanwhile I've attached correction for scenario 2 and 3.
Also, I don't understand what this means so couldn't rewrite it :
S3 :

"I'll consider the dwarves and the goal, they look very close."

What version of my campaign you are playing on?

1.1.6

I rewrote it:

Code: Select all

			{SPEAK Tarex ( _ "If you wish, I can recruit some more people of my band.")}
			{SPEAK Zanza ( _ "Good to know. I'll consider it. So, the dwarves city is close to the tunnels entrance.")}

[bssarkar]

I rewrote it:

Code: Select all

			{SPEAK Tarex ( _ "If you wish, I can recruit some more people of my band.")}
			{SPEAK Zanza ( _ "Good to know. I'll consider it. So, the dwarves city is close to the tunnels entrance.")}

So, the dwarves city is close to the tunnels entrance

should be

So, the dwarves' city is close to the tunnel's entrance

or

So, the city of the dwarves is close to the tunnel's entrance

. (Notice the (') apostrophes)

[bssarkar]

The Saurian Wise is a strange one. In my Version he is there. So sadly I don't know, what to fix.

Figured it out. Look at this line in Saurian Wise's cfg file :

Code: Select all

 image="units/saurians/campaign/S3-wise/wise.png"

But the actual folder is named

Code: Select all

Campaign

with a capital C. This didn't cause problems for you because I think you're using Win, which doesn't have case distinction in folder names (so Campaign and campaign are same folders). But Linux (and probably Mac too) does. I had to rename the folder to campaign in order for it to work.
Solution : Use small letters in folder names inside your Add-on folder. Or be consistent with the naming. If you use Campaign, then the image path above should be adjusted to :

Code: Select all

 image="units/saurians/Campaign/S3-wise/wise.png"

You might also need to check if you're using Captial vs small letters anywhere else. This is just one instance.

Hope this helps.

[Refumee]

You might also need to check if you're using Captial vs small letters anywhere else. This is just one instance.

It helps a lot. I checked all my other units. It seems the Wise is the only exception.

. (Notice the (') apostrophes)

You are right. I got now a spell checker for Notepad++, but it did not recognize this mistake.

I'm collecting more fixes before I upload a new version.

[Refumee]

I found a major bug while testing in 1.17.26 therefore I got no time for other stuff.
The Bug can be found in scenario 05. Maybe this scenario needs to be played again.

Now it is possible to control the allies in the beginning of the scenario or when they are required.

[Refumee]

New Update for 1.17.26.
I removed a lot of loyal traits. I read in some thread that they make the campaigns too easy and are unpopular.
Desert Saurians are now chaotic, like the other saurians. I think that synergizes better with the group. I also adjustet the illuminaten aura of the High Priest.

[bssarkar]

I removed a lot of loyal traits. I read in some thread that they make the campaigns too easy and are unpopular.

I wouldn't say unpopular, but restrict them only to hero units (an unit essential for the scenario) or someone very important. The most dramatic example is Legend of Wesmere, where after one scenario all of your non-loyal units will go over to the antagonist (Landar). Only your loyal veterans will remain with you. Mass spamming loyal units can be be bad to the campaign's economy, as you noticed already.

[bssarkar]

Corrections for Scenario 4. Be sure to check out my comments (###) in the file.

[Refumee]

I removed a lot of loyal traits. I read in some thread that they make the campaigns too easy and are unpopular.

I wouldn't say unpopular, but restrict them only to hero units (an unit essential for the scenario) or someone very important. The most dramatic example is Legend of Wesmere, where after one scenario all of your non-loyal units will go over to the antagonist (Landar). Only your loyal veterans will remain with you. Mass spamming loyal units can be be bad to the campaign's economy, as you noticed already.

I did so, I think. Zanza and Anexir are the two main heros both loyal.
Later on Tarex is important for one mission.
Salanix will also join the group, he is loyal and important for later missions.
Arnatrax will join for the last mission, he will get the loyal trait in the next patch.

Corrections for Scenario 4. Be sure to check out my comments (###) in the file.

### 'And this battle' -- what it means?

I do not know, if I understand the question right. Anexir will project himself into a battle scene and the elders think it is important for a saurian group to meet up Vendraxis later. They don't know really why, thats a mystery.

### What is an 'eremite'? Do you mean 'hermit', or something else?

Oh, I did mean hermit, you are right.
Are you playing on 1.17.26?

### Why 'fight, run, fight', what does it mean? Seems like a wrong idiom.

Good question. I'll think about that. It's a long time I wrote that.
Changed it in "NO! They are back! Fight!"

[bssarkar]

Are you playing on 1.17.26?

I'm not playing it, just editing the dialog in a text editor. (I used 1.16 for the Scenario 1).

And this battle

You can definitely keep it if you think it is important.

[Refumee]

I will change up the Factiontree in the next update.

I'll delete the "Guard"-Line for the Swamp Saurians and add them to the Deep Saurians. I think that will suit them more. Now I feel the Deep Saurians are complete, for now.
I also deleted the quiver for the Pike(Warrior) Saurians. They will be in the future a meele only unit. I didn't like that they are so versatile.

Here is the new Tree for this Image above. I'll change the whole Factiontree on the first page, when I upload the patch.

When I finished that up, I'll change up the bandit saurians. I really dislike those clubs.
If there are players in this thread who likes them, I'll keep them.
I consider to give them something like that (found it here in the forum):

gatherer.png (1.23 KiB) Viewed 1089 times

As an Endnote:
I'll delete the ability to recurit/advancement to the Guard. I'll keep the advancements in the data, so that the saves don't break.