Print

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

[AncientEnemy]

I really don't want to have 80 dwarves to get seiges, my comp just can't handle it. Can I change the raws and have them start seiging an existing fort or am I screwed.

[LegoLord]

Sieges are hardcoded for populations higher than 80.  There are still ambushes, however.

[GetAssista]

Sieges are hardcoded for populations higher than 80.

Not true.
OP, you should lower

Code: [Select]

[PROGRESS_TRIGGER_POPULATION:2]
[PROGRESS_TRIGGER_PRODUCTION:2]
[PROGRESS_TRIGGER_TRADE:2]tags in entity_default.txt for goblins. 1s would be enough to get your sieges in a couple years. Regenning is required though, I guess

[Sinergistic]

Sieges are hardcoded for populations higher than 80.

Not true.
OP, you should lower

Code: [Select]

[PROGRESS_TRIGGER_POPULATION:2]
[PROGRESS_TRIGGER_PRODUCTION:2]
[PROGRESS_TRIGGER_TRADE:2]tags in entity_default.txt for goblins. 1s would be enough to get your sieges in a couple years. Regenning is required though, I guess

Wrong tags. You want to remove the baby snatcher tag. This is what makes them send babysnatchers, then ambushes and finally sieges at 80.

@OP: If you don't want to regen (modifing the entity file = regen in almost all cases, see the sticky at the top) you could try pissing the humans off. IIRC they don't have any siege modifying tags beyond [SIEGER] (which makes them camp out for a little while before attacking) so if you piss them off, they should start siegeing (sp?) you, even at sub-80 dwarfs.

[Blakmane]

Sieges are hardcoded for populations higher than 80.

Not true.
OP, you should lower

Code: [Select]

[PROGRESS_TRIGGER_POPULATION:2]
[PROGRESS_TRIGGER_PRODUCTION:2]
[PROGRESS_TRIGGER_TRADE:2]tags in entity_default.txt for goblins. 1s would be enough to get your sieges in a couple years. Regenning is required though, I guess

Wrong tags. You want to remove the baby snatcher tag. This is what makes them send babysnatchers, then ambushes and finally sieges at 80.

@OP: If you don't want to regen (modifing the entity file = regen in almost all cases, see the sticky at the top) you could try pissing the humans off. IIRC they don't have any siege modifying tags beyond [SIEGER] (which makes them camp out for a little while before attacking) so if you piss them off, they should start siegeing (sp?) you, even at sub-80 dwarfs.

Actually, those are still good tags to change, but removing [BABYSNATCHER] would also be useful. Also, removing [CAN_SPEAK] will make them more aggressive due to their lack of treaties. Mix all of the above and you should start seeing seiges as early as the second year (or earlier if u are productive)

Requires regen though, sorry. Try pissing humans and elves off.

[AncientEnemy]

hmm, does hitting 80 trigger them to start sieging (even if you go back below 80) or does it check your population every time? if it's a trigger maybe i can set up an elaborate peasant deathtrap, let the final wave of migrants come, and then kill em?

also, what will changing [intelligent] to [can_civ] and [can_learn] do? i thought it was part of making them siege earlier but apparently that's [babysnatcher]..?

[Erom]

All 3 tags change seige behaviour.

The first requirement for a civ to trigger a hostile action against you is that it is hostile to you - removing CAN_SPEAK means the civ is _always_ hostile to you (and everyone else) so you never get the situation where you get a goblin trade caravan instead of attacks.

The second requirement for hostile action is the relevant PROGRESS_TRIGGER tags. Turning these up or down lower or raise the amount of generated wealth or population necessary to initiate hostile action.

Now, the BABYSNATCHER and AMBUSH(?) tags change how that "hostile action" works. The default hostile action is a seige, so if a civ has neither tag, every hostile action will be a full seige. However, if a civ has one of those tags, your population is checked, and if you are below a certain threshold (which you can't change to my knowledge, sorry) you get a snatcher or ambush instead of a full seige. Removing those tags forces the race to do a full seige anytime they want to do anything bad to you.

The final seige related tag is SEIGER - this doesn't do much, it just changes the behaviour during a seige. If the race has the tag, they make bonfires and attempt to wait you out for a few seasons before attacking. If they don't have the tag, they make their attack almost immediately after spawning.

[Skelodwarf]

So if 2 = 80

would say, 5 equal 220? Because I want a mod that would so kindly enable sieging only after 200 or so for a custom race.

[Sinergistic]

So if 2 = 80

would say, 5 equal 220? Because I want a mod that would so kindly enable sieging only after 200 or so for a custom race.

There have been a couple threads on this, neither of which I can find now, but the general consensus seemed to be that the numbers where linked to outpost 'levels'. See here: http://www.dwarffortresswiki.net/index.php/Fortress

So (for the population tag) 1 = outpost, 2 = village, 3 = town, and so on. The hardcoded 'sieges at 80' is, from my understanding and general hearsay, linked to the baby snatcher tag, which makes the race send baby snatchers, then ambushes and finally full on sieges.