Print

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

[eerr]

Alternatively, is there a way to slow down massively the coming of migrant waves? (as in, adding a lot more time between each waves).

Been a long time reader of these full of wonders forums, Hi!

Digging, building and wealth creation attract dwarves.

That value and space attracts migrants.

If you don't want dwarves, just dig less and make less.

Use stuff like communal barracks, quantum stockpiles/universal stockpiles.

Then you can regulate the arrival of dwarves based on how much you create.

[Fereval]

I see! I wonder if  developing exclusively  above ground (small space, no digging, using the cheapest materials) would help or worsen the fortress attractiveness in the end...
Thanks for the hint.

[feelotraveller]

Then you can regulate the arrival of dwarves based on how much you create.

Easier to control by editing the POPULATION_CAP in ~/data/init/d_init.txt.  Set it below your current population to stop migration.  When you are ready for more (next season) set it above again.

[SpeardwarfErith]

if you are fine with some very serious downsizing, I suggest playing a 1x1 embark on a pocket world. The FPS difference is ridiculous- There is barely any lag, even at ~100 dwarves.

[Fleeting Frames]

Alternatively, is there a way to slow down massively the coming of migrant waves? (as in, adding a lot more time between each waves).

Been a long time reader of these full of wonders forums, Hi!

If you're willing to use dfhack, I recommend max-wave.lua. Though I edited mine to also count residents when raising the cap.

A similar approach would be possible for invasions as well.

[lethosor]

Mind sharing your edits? That looks like something useful to include in DFHack.

[Fleeting Frames]

Just replacing line simple 34's isCitizen check with

Code: [Select]

if dfhack.units.isCitizen(v) or (dfhack.units.isOwnCiv(v) and dfhack.units.isAlive(v) and not dfhack.units.isTamable(v)) then
I imagine there's probably some edge case that check doesn't quite work out for; i.e. possibly kidnapped unicorns and beak dogs. Could use `not df.global.world.raws.creatures.all[unit.race].flags.CASTE_CAN_LEARN`, but it seems like there should be a better way (I combine it with isTamable check elsewhere, but cba...).

[Putnam]

I'm actually pretty sure that df.creature_raw.find(unit.race).caste[unit.caste].flags.CAN_LEARN is the best way to do it--CAN_LEARN combined with citizenry is (again, as far as I know) the only thing that determines if labors can be done on a unit now.

[Fleeting Frames]

Hm, odd. I initially tried that first, but got an error and reworked. Must have been a typo, though, since works now.