Bay 12 Games Forum

Quote from: Oaktree on June 10, 2013, 06:12:11 pm

I understand fortress wealth and/or export-import ratio triggering them.  But that also also affect how many goblins actually turn up in terms of absolute numbers per siege?

So, for instance, if I go on a masterpiece steel weapon production spree will I possibly start seeing 5-6 squads of cavalry at that point?  Or simply get a stretch where the goblins simply appear every season for the year?

Both are possible.  You'll see more frequent large numbers.

For value, what you really want are large serrated disks, and cloth.  Disks are incredibly high value, and cloth can be infinitely produced.  A single bolt of cloth can value in near 168 (masterwork cloth) + 2,400 (masterwork dye) + 2,400 (masterwork rope) or something like that, I forget exactly how the formula works, but it multiplies on itself pretty quickly and builds enormous value.  If you then decorate it with wood and cloth, or obsidian, you can have fully renewable immensely valuable items.

Lavish meals can get truly ridiculous.  Once my cook gets good, I'll have 20,000 dwarfbuck meals laying around all over the place.  Sometimes they get up to 100,000 or more, although I think that requires an unusually large stack of meat from some large creature.

A while back I had a guild representative killed and then raised by a necromancer.  I killed the necromancer, then resurrected his corpse (Masterwork Mod has a way to get a resurrect interaction).  A few years later, he showed up as a ghost.  Now I've got a ghost haunting people while his friendly body stands around dumbly.

Is there a way to put his soul back in his body?  With DFHack lua commands, say?

Does changing the auto collect webs order help?

If you want to do what I do, you have to disable both auto collect and auto loom, to prevent them from showing up in the same workshop.  Building the web collection loom(s) next to the webs is nice because each web collection job takes much less time, but it's still only one job at a time per loom.

If someone asks on the forums what the reagents are for a reaction I will search for them.  It takes a fraction of a second to search in the text raws.  But copying the exact same information from thousands of reactions into an HTML or PDF that becomes quickly out of date, and is no longer easily searchable, makes very little sense to me.

Hmm, wasn't someone making an automatic documentation generator?  I forget where I saw that.  That would be the way to go, though.

and if your dwarfs don't have any place to turn it into thread when they get back, you would probably get constant job cancellation spam, see them drop the web, get caught in it if that actually makes it deploy, and break free... thus destroying the web.

which would be a much more annoying and wasteful way of only being able to generate one (useful) web collection job per loom, so... personally, i prefer the version where only one job is generated per loom.

No, they would just dump the web in the loom and leave it there for a dwarf with a bin to retrieve (in older versions, they would carry it to a bin themselves).  I build looms right next to clusters of webbing (where a GCS was recently slain) and don't allow weaving at those looms, and the resulting thread gets piled into bins and carried up to the weaver stockpile just fine.

Once the dwarf picks up the web, it becomes a thread, and it can't change back under any circumstances.

Quote from: Brilliand on June 13, 2013, 05:19:01 am

Hmm... Wolframite in Masterwork Mod has a 100% droprate, but I don't see any [IS_GEM] tag in the raws.  There is a [SPECIAL] tag, if that matters.

Oops, that's right. Adamantine (DEEP_SPECIAL) and gems both have a 100% droprate. The cluster shape or size still has no effect, though.

Uh... this is just [SPECIAL], not [DEEP_SPECIAL].

You're claiming the wiki is wrong (and none of the usual sources of wiki wrongness seem to apply).  I think you're going to have to provide something much stronger than your word on the matter.  Really, only tests with screenshots could overcome that hurdle.

Ask Cherish if she knows more about the key, like if it will respawn when lost. (chuck it into the void?)
or if it was made somewhere.

Nothing else has shown that tendency... though I suppose we might have a shot at it respawning if we completely destroy it. 

Quote from: Brilliand on June 12, 2013, 10:20:39 am

Quote from: Goran on June 12, 2013, 03:11:34 am

Would it be possible to do a script which would turn constructions into rock? Games with a lot of constructed buildings get sluggish, and I expect they would work better if they had a few thousand stone blocks that were used to build the dwarven city be turned into natural rock formation and the items deleted. Just a thought, I have no idea how this would work out or if it would affect pathing, temperature, indoor, outdoor and stuff. But it would be a neat way to clean up the fort.

If this works on smooth constructed walls, it would allow multiplying rare stone.  Not sure whether that matters.  Also, it probably could only work on constructions made of rock materials.

Digging a tile as a 1/4 probability of giving you a stone. A stone can be turned into 4 blocks. 4 blocks can make 4 walls. You can do a random walk with the number of resources you have, but you can't reliably use this to gain resources.

On the other hand, gems and adamantine always drop stones, so just making it so you can't reconstruct gem tiles or adamantine tiles would prevent cheating.

All small clusters always drop stones.  I forget whether there are any small cluster stones in vanilla, but there definitely are in Masterwork.  The script should ignore blocks made of any small cluster material (as well as adamantine and non-stone materials).  Reconstructing adamantine or small cluster tiles with uncut stone would be fine, since you'd only get back what you put in.

Although, that feature could be used to turn all of your floors to adamantine for extremely valuable rooms... not that room value is in short supply very often.  Constructed walls also do something screwy with the floor, but it's more localized (that is, the resulting floor material has to be native to the layer).