Print

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

[ChairmanPoo]

Hello, I have searched for this to no avail, even though I´m sure others have asked for it (and I´m pretty sure I asked this myself in the past for previous versions): is there any way to stop migration altogether, be it through game mechanics or through modding?

The main point is to prevent FPS death, of course. I really want to try the new version, but I groan at the thought of getting invested and then suffering FPS death.

Likewise, if there IS a way, I´d appretiate a reminder on how you lower the pop reqs for invasions and megabeast attacks...

[KittyTac]

The siege triggers are in the goblin entity raws.

[DG]

To stop migrants: DF folder -> data folder -> init folder -> d_init file



If you set POPULATION_CAP to 7 you'll get no migrants. If one of your dwarves die, you'll get a migrant. Set it to zero and you will never get any. It's really good these days because it doesn't force the initial migrant waves of the past and you don't need the diplomat to visit/leave for the number you've set or updated to be respected by the game.

To customize megabeast reqs, in-game choose Design New World with Advanced Parameters and then hit e for advanced parameters and scroll down to here:



It does say Titan but the wiki on the fields in question says that it affects megabeasts. http://dwarffortresswiki.org/index.php/DF2014:Advanced_world_generation#Titan_Parameters I can't give you a firsthand assurance of that because I've never really paid attention to it. I can confirm that there are advanced parameters not labeled as well as they could be, such as Number of Evil Rain Types. Setting that to zero wont remove evil rains, it'll just remove all syndromes from them.

[Shonai_Dweller]

Wiki is wrong. Megabeast attack triggers are in their raws.

[Putnam]

Wiki is wrong. Megabeast attack triggers are in their raws.

Then fix it.

I did this time, but the point stands.

[Shonai_Dweller]

Wiki is wrong. Megabeast attack triggers are in their raws.

Then fix it.

I did this time, but the point stands.

Someone asked a question I told them what the answer was.
Doubt I can edit a wiki on my phone even if I had the time to find out how you're supposed to do it. Not my damn fault the wki is wrong.

[ChairmanPoo]

Changed the thread title because I think this might be a relevant topic for people.


I´ve fiddling with some of the variables stated above. So far I´ve edited the raws to lower the pop thresholds of goblin sieges (and emphasize wealth created instead), decreased max pop to 26, and severely downsized max invasion and visitor pop sizes as well. I reduced the absolute popcap inc babies too, but not as much as that one is slow

So far it seems to have had a very positive impact on FPS, as they seem to remain manageable. I am going to raise the popcap to 35 as some projects take longer than expected, but I also think that with careful management of assigned duties even 26 would suffice for large forts.

It changes the emphasis of the gameplay a bit because it makes your individual dwarves more important. Also combat management. But overall the change feels... good. As far as I´m concerned, at least.

[Xyon]

There used to be a mod out there that reduced the number of wood, leather, and stone types to fewer numbers so that there would be less unique object types to keep track of, might have made the game run better too if I remember.

EDIT:

Masterwork

[Putnam]

accelerated DF, in fact, masterwork still exists, there is another project underway for genericized materials etc.

[Bumber]

It's included as a module in Modest Mod.

[Enemy post]

Does messing with the population cap interfere with sieges?

[Shonai_Dweller]

Does messing with the population cap interfere with sieges?

Each civilised race (except dwarves for some reason) has a trigger at which point they can consider you as a siege target. There are wealth and population triggers. In vanilla DF, each race has a population trigger of 80. No wealth triggers are set so wealth isn't taken into account.

So if your pop cap is set below 80, you won't ever reach the trigger. Raiding any civ will override these triggers.

If you want to maintain a small population but play with the risk of sieges, you need to alter these triggers (or raid everyone).

Sieger numbers can be capped with a seperate option, that's not effected by pop cap.

[Enemy post]

Thanks, that sounds like fun. I'll probably do that sometime. I always liked having only a couple dwarves.

[ChairmanPoo]

Altering the triggers is fairly straightforward. Wiki explains how to do it. You have to go to entity raws and alter the relevant numbers.

I'm playing with a popcap of 35 and doing well, but I'm thinking of setting it at 50 mostly to be able to afford a large army.

Also an interesting tidbit: even if your civ is dying you can regrow it by settling and retiring fortresses. Pop will grow by itself in retired fortresses, too. And you might meet some of your old chars as migrants

[Fereval]

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!