Print

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

[Cmega3]

snip

[Ravendarksky]

If you embark RIGHT on the edge of an ocean (or any other embark with hardly any map edge) you can quickly build bridges and seal off the map edge, thus having NO immigrants.

[Urist Mc Dwarf]

Generate looooong worlds with lots of things to kill dwarves.

[JoshBrickstien]

Try genning a world with dwarves set it Max Age: 1, then change it to normal after world generation

[Larix]

If you're willing to accept the first two migration waves, you can simply lower the population cap in /init/d_init.txt to something less than the expected population. I think you can set the limit down to four (notionally the minimum required for repopulation), but a limit of ten works, too - you're guaranteed to have more than ten dwarfs when both migration waves survive.

[Naryar]

Set popcap under 10, get two first waves, then kill off the following migrants until migrants cease to come.

Squad + dwarven atom smasher works wonders.

Although I must warn you, playing with 15-25 dwarves quickly becomes tedious because you just don't have any for all the jobs even a small fort needs, and large projects become looong.

I prefer 50 dwarves, it's just enough for me without being at 90-100 and thinking "by Armok why do half of these dwarves only have useless farming jobs and do nothing all day"

[gchristopher]

The population cap doesn't have any effect if there's only a few dwarves in a fortress. One option is to use dfhack and run a script at the start of each season to prevent the migration event.

stopmigrants.lua:

Spoiler (click to show/hide)

Code: [Select]

num_events = #df.global.timed_events
migrants_found = false
for ii = 0,(num_events-1) do
  if df.global.timed_events[ii].type == df.timed_event_type.Migrants then
    curr_tick = df.global.cur_season_tick
    event_dt = df.global.timed_events[ii].season_ticks - df.global.cur_season_tick
    print("Migration Event found in " .. event_dt .. " ticks. Deleting it")
    df.global.timed_events:erase(ii)
    migrants_found = true
    break
  end
end
if migrants_found == false then
  print("No immigrants are scheduled to arrive this season.")
end


If you copy that code into a text file and save it as stopmigrants.lua in your \hack\scripts\ subdirectory, then you can type stopmigrants into dfhack and it will run. That puts off the horde of immigrants for a little while.

[Larix]

The population cap doesn't have any effect if there's only a few dwarves in a fortress.

I'd like to mention that this "few" probably means "really, really few" - two or three or so. If you have eleven dwarfs and a population cap of ten, it will normally be respected. There may be exceptions when the dwarven caravan and/or outpost liaison come to harm, but a ten-dwarf cap has worked flawlessly for me on a dozen or more embarks, without any raws editing or DFHacking.

If you don't care for dwarven trade, you can also remove the active season from the dwarven civ's entry in entity_default.txt, which removes dwarven caravans and all migration past the first year.

[hiroshi42]

If you want to have no contact with the mountainhomes period you can remove the [] from [ACTIVE_SEASON:AUTUMN] in the dwarven entry in entity.txt file.  This should prevent caravans and the liaison from coming which also handily prevents future migrations.  This can be done to an existing world and can easily be undone if needed.


Darned ninjas