Topic: "Northmen" Tribe Page

Thanks for your feedback!

I changed the message headers´ colours to green for the chieftain, light blue for the advisor, dark red for the enemy. The clay pit instruction now advises to build some sentinels.

After the brick economy is done, the scenario waits until no rations are left in the warehouse and at least one mine is out of rations. This is when the advisor reports about the hungry miners.

I added the hint to build the bee-keeper near a berry farm to the objective. Which gold mountain are you referring to? There are two – one that triggered the expand objective, one further west, northeast of the iron mountains. I intended for the gold mine to be placed on the western one, but I found that it can be overlooked if sentinels are placed only near the southern shore. I removed the gold mine from the objective. The charcoal kiln is unlocked at this point.

As soon as the mining objective is done, the chieftain demands to start recruiting soldiers now. When that is done, he orders further expansion and says it gives more space for farms and it might be good to recruit more reindeer. I renamed the fur clothes to fur garment.

When the enemy is sighted, soldier training is demanded. The objective contains a list of the required new buildings; the soldier may be sent to a warehouse now.

The problem with the long expansion chain is AI-related. I intended for it to expand much faster than it does and even added precautions in the code in case it reached the second gold mountain first. It will get much more generous starting conditions, perhaps that will make the expansion and fighting more interesting. If that doesn´t work, I might even build some free outposts for the AI after the enemy is sighted to force it to be a more interesting opponent.

I think the problem with weaving mill and shipyard was that the map was for some reason not tagged as seafaring. I´m testing the scenario with the changes now, then I´ll upload it…

Top

Quote

I now pushed a new revision with the changes to the scenario. I solved the seafaring problem by adding a second port space under the player´s headquarters. I tested it (with some cheating, to make it faster) and adjusted the flood speed so it is now actually possible to win, provided one is very quick building the seafaring buildings.

The enemy is much stronger now, I gave him lots of building materials, so his speed of expansion was just fine, he appeared at my border five minutes after the defeat-the-enemy objective was unlocked. Instead of 100 rookies, I gave him 50 soldiers with maximum attack and 150 with maximum health+defence. I haven´t played a full battle yet, but as the AI can´t train or recruit soldiers, this should be doable.

There is one spot of bother. The stormflood consumes lots of memory; the further it progresses, the more memory is flooded. In the end, it sometimes gets so bad that Widelands no longer responds and I have to force-close it. I´m unable to find the reason for this…

Top

Quote

I´m trying to script another feature for this scenario: I want the island to have a special terrain, since the northern frisian islands have salt meadows with completely different plants than on the mainland. At first, I tried setting the parameters of the terrain types in the script, but Widelands complained that they are read-only. So I added a script that defines a new terrain type and sets all normal land fields to salt meadow:

wl.World():new_terrain_type{
   name = "salzwiese",
   ...
   textures = {"campaigns/fri01.wmf/pics/salzwiese_00.png" },
   ...
}
function halligwelt()
   local x = 0
   while x < wl.Game().map.width do
      local y = 0
      while y < wl.Game().map.height do
         local field = wl.Game().map:get_field(x,y)
         if field.terr == "summer_meadow3" then field.terr = "salzwiese" end
         if field.terd == "summer_meadow3" then field.terd = "salzwiese" end
         y = y + 1
      end
      x = x + 1
   end
end

The result is always a crash due to a "Gleitkomma-Ausnahme" with no further information. gdb points to this line in terrain_description.cc:

const Image& TerrainDescription::get_texture(uint32_t gametime) const {
    return *textures_.at((gametime / frame_length_) % textures_.size());
}

Since the crash is always the same independent of whether I run the function before everything else or during the game, I guess the problem might be the texture image path. I tried setting "textures = {"world/terrains/pics/summer/steppe_barren_00.png" }" as a test, but the same exception occurred. I hope there is an easy fix for this, as this would make it possible for me to place the scenario in the real geographical context. This is not really necessary but would be a very nice addition.

What am I doing wrong?

Top

Quote

I don´t think new terrains should be added to the entire game for a not-even-that-important improvement to a scenario. I deleted the code from the campaign and won´t use custom world additions. It wouldn´t have been a very accurate representation of the salt meadows anyway, as the terrain parameters have nothing like "saltiness".

Top

Quote

GunChleoc wrote:

Or come up with an eyecandy immovable to place on them - that would have to become part of the default immovables too though.

there are a few immovables that cannot be removed and can look a bit like salt. some of the "ruins" type. I used it extensively in the dolomites map to force roads to follow the valleys

Top

Quote