View Issue Details

IDProjectCategoryView StatusLast Update
0003228Dwarf FortressDwarf Mode -- Immigrationpublic2011-10-11 10:46
ReporterAzureAngelic Assigned Touser6 
PrioritynormalSeverityminorReproducibilityhave not tried
Status resolvedResolutionunable to reproduce 
OSWindows Vista 
Product Version0.31.13 
Summary0003228: Recieved migrant message "Migrants brave this terrifying place..." despite no deaths.
DescriptionPlaying .13 for the first time, using a fortress started in .12, in the second year's summer. Received a migrant wave with the message "Some migrants have decided to brave this terrifying place, knowing it may be their tomb".

No dwarves have died in this fortress to date. The only casualties on the unit screen consist of a puppy and a donkey. This includes elves, humans, dwarf caravans and goblins (whom haven't even arrived yet).

Migrant wave consisted of a mere 6 dwarves, including a bizarre lone dwarven baby. No animals.
Tagsmigrants

Relationships

has duplicate 0003296 resolvedLogical2u Recieved message "No one even considered making the journey to such a cursed death-trap this season" 
has duplicate 0003307 resolvedLogical2u Immigrants did not come. 

Activities

Eugenitor

2010-09-15 12:57

reporter   ~0012661

Last edited: 2010-09-15 12:58

Getting the same thing, albeit with a handful of dead dwarves- shouldn't be nearly enough to trigger this message.

HammerDave

2010-09-15 21:44

reporter   ~0012690

I'm getting it too, on a newly genned world in .13, so it's not due to transfers from .12. It came up during the summer of 1051, and a fairly typical 7 migrants arrived normally.

Well, typical except there was a LEGENDARY milker. Why a milker would emigrate to a new fortress with no milkable animals is a mystery, as well as how there could be enough milking activity to generate a legendary... but I'll take 'em any way they come. lol

Illeist

2010-09-15 21:57

reporter   ~0012691

I also received the same message on a world genned in .13 without losing any dorfs. Incidentally, one of them was a legendary hammerdwarf; I've never seen a legendary migrant before.

Quietust

2010-09-15 22:04

reporter   ~0012693

I believe I've received a few legendary migrants in version 0.31.12, though usually High Master is the best I get.

oolon1

2010-09-15 23:19

reporter   ~0012695

I got the "terrifying" message on the first wave. The second wave was the normal "Some migrants have arrived." Is anyone getting this on subsequent waves?

I also experienced the legendary hammerdwarf in my first wave, and initially reported it as a bug. It could be an intentional gift to jump start the military training, which was slow in 0.31.12 if you started from zero, but I'm not sure everyone is getting it. Just coincidental?

bunglero

2010-09-16 21:54

reporter   ~0012734

After updating and migrating over my save files, I too got this message, and whats more: my population cap is at 100, the fortress is at 120 (due to births). So, it may be ignoring the population cap...

uggi

2010-09-17 05:49

reporter   ~0012749

Last edited: 2010-09-17 05:50

In my current fortress, the population cap was set to 80 several years ago, when the population went over 120. I did not receive migrants since, until I updated to 0.31.13.

Now in summer 39 the population was 116 dwarves, and out of nowhere comes 8 migrants with the "Some migrants have decided to brave this terrifying place, knowing it may be their tomb." message.

So for some reason the population cap limit was ignored. Latest deaths were one dwarf in spring 38 and another in winter 38, both to infection.

maanahr

2010-09-18 04:04

reporter   ~0012784

Last edited: 2010-09-18 04:05

Same here. I had a population cap of 30 and a population of about 50, no migrants for the last decade or so, and only a few deaths during that time.

Moved the fortress from 0.31.12 to .13, got the same "Some migrants have decided to brave this terrifying place, knowing it may be their tomb." message and a migration wave led by a legendary lasher.

I thought I'd just forgotten to set the population cap in .13, but nope, it was already set to 30.

Aleks

2010-09-18 13:48

reporter   ~0012795

Last edited: 2010-09-18 13:48

And i just got a migrant wave of three babies. Strange. (31.13)

aimaisan

2010-09-18 23:14

reporter   ~0012808

I just received this message as well on my first wave, with no deaths previous. In my second wave I got the normal message, but the only dwarfs that showed up was a drunk who can't be assigned work and a baby with no parent as the second migrant wave.

I'm on .13 and have started fresh, no save transfer or anything.

Eurytus

2010-09-22 13:08

reporter   ~0012896

I just got this message. There have been no dwarf or domestic animal deaths, only a floating guts, a blind cave ogre, and two crundles have been killed.

Nidor

2010-09-22 15:18

reporter   ~0012902

Got the "death trap" version with no deaths (it was only the second year) save one raccoon that jumped into magma on a dodge.

akd

2010-09-22 18:21

reporter   ~0012908

Last edited: 2010-09-22 18:23

Another confirmation of the behavior of moving from 0.31.12 to 0.31.13 ignores population cap, and I've gotten a handful of migrant waves with the "knowing it may be their grave" message as well. The first migration message I got was actually "no one dared travel to this hellhole/deathtrap/whatever."

Additionally, I suffer no more than 5 fatalities per year. Of course, that's just counting dwarfs.

Logical2u

2010-09-23 16:40

manager   ~0012932

According to Toady this might be fixed in 31.14. Can anyone confirm?

maanahr

2010-09-28 00:36

reporter   ~0013034

My population is still above the cap I set, and I haven't received any migrants in .14 yet.

I do get the occasional message that my fortress didn't attract any migrants. I don't think .12 and before gave such messages when over the population cap. Maybe it's fixed; maybe I just happen to not get any migrants yet.

topace3k

2010-09-28 22:26

reporter   ~0013051

I've gone a couple years in .14 without any problems on a fort that used to get the message at random sometimes.

maanahr

2011-07-20 04:27

reporter   ~0018286

After 10 months, I think we can safely say that this is indeed fixed. :-)

Issue History

Date Modified Username Field Change
2010-09-15 10:19 AzureAngelic New Issue
2010-09-15 11:31 Kennel Tag Attached: migrants
2010-09-15 12:57 Eugenitor Note Added: 0012661
2010-09-15 12:58 Eugenitor Note Edited: 0012661
2010-09-15 21:44 HammerDave Note Added: 0012690
2010-09-15 21:57 Illeist Note Added: 0012691
2010-09-15 22:04 Quietust Note Added: 0012693
2010-09-15 23:19 oolon1 Note Added: 0012695
2010-09-16 21:54 bunglero Note Added: 0012734
2010-09-17 05:49 uggi Note Added: 0012749
2010-09-17 05:50 uggi Note Edited: 0012749
2010-09-18 04:04 maanahr Note Added: 0012784
2010-09-18 04:05 maanahr Note Edited: 0012784
2010-09-18 13:48 Aleks Note Added: 0012795
2010-09-18 13:48 Aleks Note Edited: 0012795
2010-09-18 23:14 aimaisan Note Added: 0012808
2010-09-22 05:52 Logical2u Relationship added has duplicate 0003296
2010-09-22 13:08 Eurytus Note Added: 0012896
2010-09-22 15:18 Nidor Note Added: 0012902
2010-09-22 18:21 akd Note Added: 0012908
2010-09-22 18:21 akd Note Edited: 0012908
2010-09-22 18:22 akd Note Edited: 0012908
2010-09-22 18:23 akd Note Edited: 0012908
2010-09-23 07:57 Logical2u Tag Attached: Fixed in 0.31.14?
2010-09-23 16:40 Logical2u Note Added: 0012932
2010-09-24 05:25 Logical2u Relationship added has duplicate 0003307
2010-09-28 00:36 maanahr Note Added: 0013034
2010-09-28 22:26 topace3k Note Added: 0013051
2010-12-11 08:51 user11 Tag Detached: Fixed in 0.31.14?
2011-07-20 04:27 maanahr Note Added: 0018286
2011-07-28 10:01 user6 Status new => resolved
2011-07-28 10:01 user6 Resolution open => unable to reproduce
2011-07-28 10:01 user6 Assigned To => user6