Print

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

[Vincie]

Saw alot of threads regarding this issue, in 0.44, making goblins [SITE_CONTROLLABLE] required to take out the [CHAT_WORTHY] tag from nobles, since it conflicted with the demon's lord [CHAT_WORTHY] or similiar. Now with 0.47 no matter what, all nobles in the entity file under goblins make the game crash during world gen, when placing civs, except with some luck when you have maybe 5 civs in total and very a short history. I worked around this and simply replaced the goblin's [DEFAULT_SITE_DARK_FORTRESS] with the dwarven fortress type [...CAVE_DETAILED], made a second goblin civ in entity without [SITE_CONTROLLABLE] and their [.. DARK_FORTRESS] so I still have these fortresses on my map. Works 100% every world gen.

tl, dr
[SITE_CONTROLLABLE] conflicts with [DEFAULT_SITE_DARK_FORTRESS] replace with [DEFAULT_SITE_CAVE_DETAILED] or other site for tempoary fix

[Iä! RIAKTOR!]

PLAYER_FORTRESS generate civ of only hillocks, and this hillocks may be unretired if playable civ. Whats new with MONUMENT site type?

[Vincie]

PLAYER_FORTRESS generate civ of only hillocks, and this hillocks may be unretired if playable civ. Whats new with MONUMENT site type?

I don't exactly understand what you mean, is it related to the new problem of the latest df release 0.47, where people reported that their costum entities cause the game to crash upon placing civs during worldgen, because either they have a entity race with [NO_EAT], enabled fish cleaner job and some positive cleaning tendencies OR because the entity has [DEFAULT_SITE_DARK_FORTRESS] AND defined noble positions, yet it worked in df 0.44 when you simply removed [CHAT_WORTHY]

[Iä! RIAKTOR!]

PLAYER_FORTRESS generate civ of only hillocks, and this hillocks may be unretired if playable civ. Whats new with MONUMENT site type?

I don't exactly understand what you mean, is it related to the new problem of the latest df release 0.47, where people reported that their costum entities cause the game to crash upon placing civs during worldgen, because either they have a entity race with [NO_EAT], enabled fish cleaner job and some positive cleaning tendencies OR because the entity has [DEFAULT_SITE_DARK_FORTRESS] AND defined noble positions, yet it worked in df 0.44 when you simply removed [CHAT_WORTHY]

Yeah, I remember this new issues. And also in 47 special tokens now not add divine materials to civs.

[Shonai_Dweller]

PLAYER_FORTRESS generate civ of only hillocks, and this hillocks may be unretired if playable civ. Whats new with MONUMENT site type?

I don't exactly understand what you mean, is it related to the new problem of the latest df release 0.47, where people reported that their costum entities cause the game to crash upon placing civs during worldgen, because either they have a entity race with [NO_EAT], enabled fish cleaner job and some positive cleaning tendencies OR because the entity has [DEFAULT_SITE_DARK_FORTRESS] AND defined noble positions, yet it worked in df 0.44 when you simply removed [CHAT_WORTHY]

Yeah, I remember this new issues. And also in 47 special tokens now not add divine materials to civs.

Still not seen any proof that they ever did.

[Fatace]

Saw alot of threads regarding this issue, in 0.44, making goblins [SITE_CONTROLLABLE] required to take out the [CHAT_WORTHY] tag from nobles, since it conflicted with the demon's lord [CHAT_WORTHY] or similiar. Now with 0.47 no matter what, all nobles in the entity file under goblins make the game crash during world gen, when placing civs, except with some luck when you have maybe 5 civs in total and very a short history. I worked around this and simply replaced the goblin's [DEFAULT_SITE_DARK_FORTRESS] with the dwarven fortress type [...CAVE_DETAILED], made a second goblin civ in entity without [SITE_CONTROLLABLE] and their [.. DARK_FORTRESS] so I still have these fortresses on my map. Works 100% every world gen.

tl, dr
[SITE_CONTROLLABLE] conflicts with [DEFAULT_SITE_DARK_FORTRESS] replace with [DEFAULT_SITE_CAVE_DETAILED] or other site for tempoary fix

In 44.x, you didn't need to take out [CHAT_WORTHY] for Dark Fortress civs.

With 47.x, Dark Fortress civs masters (demons) create the noble positions from year 0, and onward over time. and if any position collided with a position that you customly created, it causes the crash.