Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Giant Dwarf]

Hi

I know, that there is a population cap, which you can set to prevent Migrant Waves (after the first 2).
But I personally would rather want really small Migrant-Waves instead of none at all.
(Also I'd still like to have normal child production!)
Is there any way to do this?

In my current game, it was like this:
- 7 Starting Dwafs (one was eaten by an alligator, but anyways ...)
- 2 Migrants in Summer (good!)
- 9 Migrants in Autumn (too much already!)
- 25 Migrants in the next Spring (-.-)

I think 1-4 Migrants each Season would be ok.

Those huge waves kinda destroy my relation to the Dwarves.
I'd like to Micromanage them properly, give them names, know them a bit better. But with such big waves, it gets kind of annoying/impossible to do that.

[Raven]

the last scripted wave in the first spring is always large, next waves will be shorter and based on your wealth

[greycat]

As far as I know, the only way to enforce small migrant waves is to micromanage the population cap every season.

[PatrikLundell]

As greycat said, increasing the pop cap to the current value +4 will probably give you 1-3 migrants (I increase the limit to current+10, and don't think I've ever gotten 10, but don't take that as an absolute truth). This limit will work on the hard coded waves as well, so you can restrict the size of both. The pop cap doesn't restrict births (that's taken care of by the strict pop cap).

I think Raven confuses things a little, as the two hard coded waves arrive in spring and autumn, so the spring one is the first "regular" one.

It can also be noted that the "hard coded" in the hard coded waves are just their appearance (unless blocked by pop cap or sieges). If you save scum you'll find that the size and composition of both of these two waves vary.

[Niddhoger]

They vary... but they still have small ranges. Iirc, their max is 9? You'll never see them hit the 40+ that have been reported in later waves. The main driver is fortress wealth as reported by the fall caravan. I can't remember if it's just the profits you trade them, or if they size up your fortress wealth and report that. 

What I am saying is, you can try limiting wealth production and trading if you don't want to constantly tweak the Raw files.  Consider always settling near humans and using them as your main partners while only trading bare essentuals/specific requests with the mountainhome. 

[ragincajun]

As greycat said, increasing the pop cap to the current value +4 will probably give you 1-3 migrants (I increase the limit to current+10, and don't think I've ever gotten 10, but don't take that as an absolute truth). This limit will work on the hard coded waves as well, so you can restrict the size of both. The pop cap doesn't restrict births (that's taken care of by the strict pop cap).

I think Raven confuses things a little, as the two hard coded waves arrive in spring and autumn, so the spring one is the first "regular" one.

It can also be noted that the "hard coded" in the hard coded waves are just their appearance (unless blocked by pop cap or sieges). If you save scum you'll find that the size and composition of both of these two waves vary.

Do you change this in the raws?
If using LNP, if you save and then reload the game with a change in the pop cap does that work or is just the initial setup used?

[Giant Dwarf]

Thanks for all the answers!
I guess I will just "micro manage" the Population Cap then.
Thinking about it, it's actually not that much work, if you consider, how much you have to do to actually keep your fortress running.

Still a more elegant solution would be cool.
Maybe as a mod?

@Niddhoger
Can't be trading profits, as I didn't even trade anything to the first caravan.

[Dunamisdeos]

Kill the useless ones and build memorials.

[Mostali]

As far as I know, the only way to enforce small migrant waves is to micromanage the population cap every season.

I do this from the start.  I usually go with a cap of 10 or 12 the first year and the summer/august waves have yet to exceed my cap.

I also manage visitor and child caps according to need.  I usually go in once per year (in winter) and change everything at once.  Yeah, it would be nice to have an in-game way to manage both dwarf and animal pops.

[PatrikLundell]

As greycat said, increasing the pop cap to the current value +4 will probably give you 1-3 migrants (I increase the limit to current+10, and don't think I've ever gotten 10, but don't take that as an absolute truth). This limit will work on the hard coded waves as well, so you can restrict the size of both. The pop cap doesn't restrict births (that's taken care of by the strict pop cap).

I think Raven confuses things a little, as the two hard coded waves arrive in spring and autumn, so the spring one is the first "regular" one.

It can also be noted that the "hard coded" in the hard coded waves are just their appearance (unless blocked by pop cap or sieges). If you save scum you'll find that the size and composition of both of these two waves vary.

Do you change this in the raws?
If using LNP, if you save and then reload the game with a change in the pop cap does that work or is just the initial setup used?

I use LNP, but you could just as well change the file LNP changes (LNP doesn't do magic, but it's quite convenient). Since I use LNP I haven't located the file, but it's not a RAW one, but rather one with regular parameters intended to be adjusted without the game being modded. I save, quit, change, and restart. DF reads the values at startup (I don't know if it reads them on "continue", but I doubt it, hence the quit).

[Raven]

As greycat said, increasing the pop cap to the current value +4 will probably give you 1-3 migrants (I increase the limit to current+10, and don't think I've ever gotten 10, but don't take that as an absolute truth). This limit will work on the hard coded waves as well, so you can restrict the size of both. The pop cap doesn't restrict births (that's taken care of by the strict pop cap).

I think Raven confuses things a little, as the two hard coded waves arrive in spring and autumn, so the spring one is the first "regular" one.

It can also be noted that the "hard coded" in the hard coded waves are just their appearance (unless blocked by pop cap or sieges). If you save scum you'll find that the size and composition of both of these two waves vary.

I've read in the past that the third (big one) wave is hardcoded too

[PatrikLundell]

It's definitely the case that dead civs receive two waves and no more, so your source(s) might either be incorrect or obsolete (I don't know much about the state prior to 0.40.X).

[greycat]

Do you change this in the raws?

It's in data/init/d_init.txt

If using LNP, if you save and then reload the game with a change in the pop cap does that work or is just the initial setup used?

The LNP launcher program just modifies files for you.  The files are read when Dwarf Fortress starts, so after changing the population caps, you have to save, exit and restart DF.

[Loci]

I played around with dfhack a bit and created this script:

Spoiler (click to show/hide)

Code: [Select]

--Dynamically limit the next immigration wave
--[[=begin

max-wave.lua
============
Set the population cap to the lesser of current_pop + wave_size or max_pop.
Use with the `repeat` command to set a rolling immigration limit.

Usage examples::

    max-wave wave_size (max_pop)
   
    repeat -time 1 -timeUnits months -command [ max-wave 10 200 ]

The first example is abstract and only sets the population cap once;
the second will update the population cap monthly, allowing a
maximum of 10 immigrants per wave, up to a total population of 200.

=end]]

local args = {...}

local wave_size = tonumber(args[1])
local max_pop = tonumber(args[2])
local current_pop = 0

if not wave_size then
  print('max-wave: wave_size required')
  return
end

--One would think the game would track this value somewhere...
for k,v in ipairs(df.global.world.units.active) do
  if dfhack.units.isCitizen(v) then
   current_pop = current_pop + 1
  end
 end

local new_limit = current_pop + wave_size
 
if max_pop and new_limit > max_pop then new_limit = max_pop end

df.global.d_init.population_cap = new_limit
print('max-wave: Population cap set to '.. new_limit)


To use it, copy the code and paste it into "hack/scripts/max-wave.lua" in your Dwarf Fortress directory. You can run it directly in the dfhack console ("max-wave 20 20") to set the population cap without reloading, or use it with repeat to create a rolling population cap (like "repeat -time 3 -timeUnits months -command [ max-wave 10 200 ]") to slow down immigration to whatever rate you desire. You can probably even set it up in an init file so it's entirely automatic.