Print

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

[mifki]

I've updated the script, it now accepts parameters as below:

-civ HUMAN -race [ GOBLIN TOAD ] -count [ 2 10 ] -undead -debug -cleanup

-civ is optional. If not present, will find a civ for the first race. If present, it can be a race name (will find a civ), or a part of english civ name. Can also be "self" if you can't think of anything better.
-race is require and can be either one value or a list.
-count is required and can be either one value or a list with number of items matching races.
-undead is optional if you're a fan of corpses.
-debug is optional.
-cleanup is optional and will delete the created army controller.

I think doing the cleanup if generally better, but it needs more testing. I've had some crashes when generating a 100 goblin siege both with cleanup and without but not sure whether it's a vanilla DF crash because of a large number of units or is caused by the script.

[Rumrusher]

so if I remember correctly you could point 2 bandit armies to one spot and have them both auto attack each other due to their ai is targeted to attack Brigands and being apart of an army.

[Ggobs]

Where do I add this script?

[mifki]

Where do I add this script?

To hack/scripts folder.

[Warmist]

Oh cool. I when i was doing army stuff the controller was not researched enough. IIRC you can add hist figures to the armies for more fun

Also has anyone tried to use "friendly armies". Maybe you could already do the "your units leave to offsite targets" scripts for some more modding fun? This way they could actually return.

[Roses]

So I was working on thoroughly testing the unit create script since I was getting crashes trying to create 50+ units at once (to replicate sieges) when I remembered this gem. Part of this post is just to bump this up so other people don't forget about it like I did, but I also have a couple questions (sorry, I know some of them could be answered by me simply trying out the script, but I am traveling right now and sadly DF doesn't work on my phone)

1. Have you done any more work on the script? You mentioned you are more into research that maintaining, but just wanted to check if you fleshed out any more of the unknown values.

2. Are units spawned with items and materials accessible to the civ as normal?

3. If using -undead is the entire army spawned undead, or just some of them?

4. What does adding the creature class to the army do? Does that mean only creatures with that creature class will be spawned?

5. Do you mind if I include this script in my repository (with appropriate credit of course)?

[Rumrusher]

completely forgot about this script/thread, and that I got my question answered.

hmm probably a good time to mess with this script.

oh and thanks roses.

I guess with 3 it's similar how inhabitants of forts can start off with syndromes or interaction classes that turn them into a vampire or a necromancer on a site level.

[mifki]

1. Have you done any more work on the script? You mentioned you are more into research that maintaining, but just wanted to check if you fleshed out any more of the unknown values.

No, I was sort of waiting for feedback whether it works ok or causing any problems after some time in game maybe. In particular, there's a "cleanup" command-line flag which will case army controller to be deleted after siege has started. That's because there's an unknown structure unk_58 in army_controller which is filled with some data seen in other controllers, and I don't know whether it's better to leave the controller with that data or delete it manually. In my tests I didn't experience crashes in either case, but I didn't play for too long.

2. Are units spawned with items and materials accessible to the civ as normal?

I guess yes, the actual units are spawned by the game, so it should just like during normal sieges.

3. If using -undead is the entire army spawned undead, or just some of them?

Entire army. However currently it puts 100 in some field to do this, don't know why this particular value.

4. What does adding the creature class to the army do? Does that mean only creatures with that creature class will be spawned?

Don't know, not even sure what creatures it's supposed to affect.

5. Do you mind if I include this script in my repository (with appropriate credit of course)?

Sure, if it doesn't corrupt anything I'd be happy if more people knew about the script.

[Putnam]

I tried to force a siege by creating an army, a controller and targeting the fort. It seems to work just fine, so now I'm unsure whether just no one tried that, or there are known issues with this approach.

Could never get it consistent and armies weren't as well-mapped way back in 2014 when I was trying it. I also just sort of forgot over the years.

[pikachu17]

PTW

[iii22]

How do I make the army controller?

[FantasticDorf]

Just saw this was necro'd and wanted to chip in with a bit of information.

I dont have any experience with army controllers, but on account of 44.12 (current of time of post) raiding system, is there any elaboration on whether we could manipulate these controllers instead? Mainly as a side note of forcing them to come back home or clearing them off the map.

Since 44.12 (or implementation of raiding in general), if they are the only kind of applicable army availible to them, positions overlaps onto [CAPTAIN] like [MILITIA_CAPTAIN] for fortress mode will send historical units in sieges, whereas the default of [CAPTAIN] (this is hardcoded and auto-provided by generated positions over sites) will send fodder generated out of thin air, which can be tracked from the new c civilisation screen as historicals actually depopulate sites as they get their armies together while captains do not.

A additional criteria of position captain leaders would be interesting, since then you could arrange for things like:

Code: [Select]

-civ EVIL -position [CAPTAIN] -addposition [MONARCH] - race [GOBLIN] - count [60 100]
A evil siege, forcing the attendance of the monarch (demon) but lead by a captain.

[iii22]

Just saw this was necro'd and wanted to chip in with a bit of information.

I dont have any experience with army controllers, but on account of 44.12 (current of time of post) raiding system, is there any elaboration on whether we could manipulate these controllers instead? Mainly as a side note of forcing them to come back home or clearing them off the map.

Since 44.12 (or implementation of raiding in general), if they are the only kind of applicable army availible to them, positions overlaps onto [CAPTAIN] like [MILITIA_CAPTAIN] for fortress mode will send historical units in sieges, whereas the default of [CAPTAIN] (this is hardcoded and auto-provided by generated positions over sites) will send fodder generated out of thin air, which can be tracked from the new c civilisation screen as historicals actually depopulate sites as they get their armies together while captains do not.

A additional criteria of position captain leaders would be interesting, since then you could arrange for things like:

Code: [Select]

-civ EVIL -position [CAPTAIN] -addposition [MONARCH] - race [GOBLIN] - count [60 100]
A evil siege, forcing the attendance of the monarch (demon) but lead by a captain.

It says that it can't find a civilization, even though I settled near a goblin pit.

[Meph]

Damn... Why did I never see this?

[iii22]

I've updated the script, it now accepts parameters as below:

-civ HUMAN -race [ GOBLIN TOAD ] -count [ 2 10 ] -undead -debug -cleanup

-civ is optional. If not present, will find a civ for the first race. If present, it can be a race name (will find a civ), or a part of english civ name. Can also be "self" if you can't think of anything better.
-race is require and can be either one value or a list.
-count is required and can be either one value or a list with number of items matching races.
-undead is optional if you're a fan of corpses.
-debug is optional.
-cleanup is optional and will delete the created army controller.

I think doing the cleanup if generally better, but it needs more testing. I've had some crashes when generating a 100 goblin siege both with cleanup and without but not sure whether it's a vanilla DF crash because of a large number of units or is caused by the script.

So I decided to try this script again ( -civ HUMAN -race [HUMAN] -count [5] ) but it still didn't work. The error message was something like "couldn't find available civ". Does anybody have a video demonstration for something?