Bay 12 Games Forum

Quote from: ldog on January 28, 2021, 07:01:51 pm

Does anyone have a good set of filters, either for this or any of the clones (soundcense, soundsense rs) to filter out sparring?
I have gotten rid of just about every sound I can think of that I could and yet still the noise is constant. My soldiers are always sparring, which defeats the purpose of the sound engine like the boy who cried wolf. I've gone back to this version since the other ones fail to work more often than not (rs plays when it feels like it, c just doesn't want to load).

The problem seems to be NOT "(.+), lightly tapping the target!" needs to be appended to every hit entry if possible (which wouldn't be too bad) or every stinking hit entry needs to be created with every combination other than "(.+), lightly tapping the target!" which would suck in the extreme. I can't believe I am the only one who has slowly been driven insane by this over the years.

There isn't any way to differentiate between an attack that's attempted in combat versus sparring, since the "lightly tapping" message never occurs. That means you can't have any sound for misses or dodges, for starters. It should be possible to differentiate between some of the blows that land, however. I don't think wrestling joint locks occur in sparring, for example.

What I ended up doing is just commenting out most of everything in battle.xml, hitevents.xml, and strikes.xml that doesn't relate to taking damage. (I also disable the vomit sounds in status.xml.) It's unfortunate that you can't hear when creatures are merely trying to kill each other, but it's better than turning off combat sounds altogether.

TODO:

• Heavy feeder stockpiles for corpses, boulders, and ores. this includes designing and implementing a mechanism for blueprints to specify (at stockpile creation time) how many wheelbarrows a particular stockpile should have

Notes:

• From your reports, it seems that the current lye-soap order chain is the best we can do (for now). is that right?

• It wouldn't be too difficult to extend combine-plants and combine-drinks to iterate over all stockpiles and automatically combine stockpiles that have the appropriate item types enabled. I suggest filing a feature request bug

• If you want walls/floors built out of a particular material, you can set the filter in buildingplan and quickfort will use it. for example, to set walls to be made out of quartzite: bCwPM{Right}quartizite{Enter}{Shift}{Enter}. you just have to set the filter before you run the quickfort blueprint.

• I forbid tallow in the cookables pile since it's enabled in the 'goods' quantum on the industry level (for use in soap). the kitchen will still use it, but with it stored so far away, all the higher-quality cookables will be used first.

• Right now I only enable crafts in the trade depot QSP. are there any other item types we should add here?

• I normally dig a quarry below the apartment levels for more stone for the masons. would this be useful to add to the blueprint set?

• The traps outside the main gate aren't very useful for sieges (since you can't protect them with bridges to reset them during the siege), but they're great capturing wildlife that are pathing past your fort in peacetime. I found they are excellent for harvesting wild meat.

• Barracks on the surface is in it's own stage, true, but the roof needs to be completed first, otherwise we can't place the beds (need to be "indoors"). When I split the roof construction, though, I can make sure the beds tiles are covered in an early stage

• Re: I unsuspended jobs that didnt have materials ready for them -- yeah, this is buildingplan's bane. It's on my backlog to see if I can prevent buidlingplan-managed buildings from being manually unsuspended from the jobs list. They're already protected when querying the building itself, but, as you found, there are other ways to unsuspend.

• Sandbags in metal QSP - I'm having second thoughts about this one. I'm worried splitting furniture across two stockpiles will cause confusion. the current furniture QSP is really not that far away -- just 12 tiles (true, the metalworker QSP is only 4 tiles away, but is the increased efficiency for making glass worth the added complexity?)

New aliases needed in your aliases.txt:
(until the next DFHack release, when they'll be in the standard alias library)
[/list]

Code: [Select]

crafts: {finishedgoodsprefix}{Right}f{Right}{Down 9}{togglesequence 9}^
forbidcrafts: {finishedgoodsprefix}{Right 2}{Down 9}{togglesequence 9}^
permitcrafts: {forbidcrafts}
bronzeweapons: {metalweapons}{forbidmetalweapons}{permitbronzeweapons}
forbidbronzeweapons:  {weaponsprefix}{Right}{Down 2}{Right}{Down 6}&^
permitbronzeweapons:  {forbidbronzeweapons}
bronzearmor: {metalarmor}{forbidmetalarmor}{permitbronzearmor}
forbidbronzearmor: {armorprefix}{Right}{Down 6}{Right}{Down 6}&^
permitbronzearmor:  {forbidbronzearmor}


I tested the new layout and ironed out the obvious bugs, but I got distracted: since you've been seeing crashes, I've been running DF in a debugger while I playtested the new layouts, and I finally got it to crash. With lethosor's help, I think I tracked down the reason. It shouldn't be too hard to fix, but it might take me a few days to write and test the code. Once it's merged, you could pick up a dev build and overwrite your LNP version. Fewer crashes might be better for your psyche : )

I like how compact everything is now - it really makes it easier to get settled.

Btw, the new trade goods quantum needs a new alias: crafts. I'll post the definition when I get back to my computer (on phone).

If you're updating the automation orders in your fort, could you export the json and upload it somewhere (or post it here)? If you are already expanding the orders and updating the conditions, I'd hate to just be duplicating your work.

What do you think of this design for the surface level? https://docs.google.com/spreadsheets/d/1vlxOuDOTsjsZ5W45Ri1kJKgp3waFo8r505LfZVg5wkU/edit#gid=232787567
compact enough?