Bay 12 Games Forum

I thinks it's worth trying, and for performance issue, i don't thinks it's the case. I have currently on a world vastly more hist figs that pops of human. So it will decrease my perfs by less that a factor 2 if i transform all the human pops into hist fig.
Alos, notice that in the begenning i made this test to reduce the popping of population in a natural way without the limit of site so the goal is to have less population, and so less hist fig.

Of course, it would be bad to simulate 5000 years old worlds. But for 250/400 years i can manage to wait ^^ and i have a good CPU ^^

So,
By digging in the work of [ORIENTATION] tag, i was surpised to discover that a full range of parameter did not apply to "non tracked population" during world gen, aka : "non historical figure".

This make large problem between worldgen behaviour of a race and its behaviour in game. Ans as we can have now (since tavern and co) a lot of other race in fort, it should be usefull to improve a bit this type of gap.
Example of a fail : make a race with 100% assexual men and female and show it spread like bunny during worldgen. Or observe simply the explosion of birth during worldgen while you have all the difficulties to make marriage in a fort in a same period of time (let's say 10 years).

My suggestion is that all parameters applied to races that limits the briths etc... should apply to populations, even non historical figure, during worldgen on simulated pops. And it should be relatively easy to implement as all these parameter are perfectly predictible.

For example : ORIENTATION tag which create assexual percent of the population, gay population, bissexual or heterosexual should result in only hetero and bi population being a part of the simulation for poping pops during world gen. (by simply substracting individual pops)
I don't know if the age is taken too, but if not, it should too.

Also, in fortress mod it seems that sharing gods helps for marriage, it should play a role too on race with a PANTHEON. It could be simulated costlessly through statistical estimation.

I didn't know the other parameters but i imagine this could be tracked too. ^^

An other way could be to let the player set a [ALL_HISTORICAL] tag that track all its populations despite the high processing charge. But both could be done : An improvement of the simulation and an avaibility of this tag.

That was my idead, sorry for bad english

It's not listed on DF2014:Titan, so what page did you visit?

Quote from: KittyTac on August 16, 2017, 10:19:44 pm

Except titans can't be killed in worldgen! But the problem with losing sites still stands.

A quick gen of the world I created for cowmuffin (outdated now due knowing better worldgen techniques, but still neat) reveals this:

||

Eyeless meaty dino, struck down by giant monarch butterfly in forest retreat. FBs can also die, so maybe your worlds don't have enough fighting for titans?

Trying to use megabeasts to cull site populations tends to be almost all or nothing results, where either megabeast dies or non-goblin civs suffer and lose most of their sites.