Print

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

[dwarfish]

can't mark for dumping. couldn't find a dfhack script to make it part of my fort's possessions so my dwarves will store it in the library. currently eating at my already low fps and interfering with some stockpiles

[Stadfradt]

I'd forbid it, then claim it, then forget about it. "A watched pot never boils" seems to be a basic operating principle of the game's programming.

[Bumber]

Assign it to a display pedestal in your library, then unassign or deconstruct the pedestal after the book has been stored.

[Dunamisdeos]

Anytime I get mad at things not being moved I simply drop magma on it with dfhack in a fussy rage state.

[Stadfradt]

Anytime I get mad at things not being moved I simply drop magma on it with dfhack in a fussy rage state.

Your plan > Bumber's plan > my plan

[PatrikLundell]

Apart from the 'f'orbidden flag set on items dropped on death by default, they also often have the trader flag set.

Here's a DFHack script to claim these books by removing the trader flag from them.

Spoiler (click to show/hide)

Code: [Select]

[code]
function claim_books ()
  local dumped = 0
  local dump_forbidden = 0
  local dump_foreign = 0
  local dump_trader = 0
  local melt = 0
  local trader_ground = 0
  for i, item in ipairs (df.global.world.items.all) do
    if item.flags.dump then
      dumped = dumped + 1
     
      if item.flags.forbid then
        dump_forbidden = dump_forbidden + 1
      end
     
      if item.flags.foreign then
        dump_foreign = dump_foreign + 1
      end
     
      if item.flags.trader then
        dump_trader = dump_trader + 1
      end
    end
   
    if item.flags.melt then
      melt = melt + 1
    end
   
    if item.flags.on_ground and
       item.flags.trader then
      trader_ground = trader_ground + 1
      if item.subtype.id == "ITEM_TOOL_SCROLL" then
        item.flags.trader = false
        dfhack.println ("Claiming scroll")
     
      else
        printall (item.subtype)
      end
    end
  end
 
  dfhack.println ("Dump designated: " .. tostring (dumped), "Foreign: " .. tostring (dump_foreign), "Trader: " .. tostring (dump_trader))
  dfhack.println ("Melt designated: " .. tostring (melt))
  dfhack.println ("Trader items on the ground: " .. tostring (trader_ground))
end

claim_books ()
[/code]

Also, dropping magma on artifact books is a sub optimal idea, since the magma will cause them to catch fire, but their artifact status will cause them not to be consumed, so you've got a perpetual fire that produces smoke and risks setting fire to things around them (like vegetation growing up next to them).

[xpi0t0s]

I just solved a similar problem, but had to remove the "foreign" flag. Removing "trader" didn't do anything (and troubleshoot-item showed its status hadn't changed either).
Also I found autodump wouldn't touch it.

[PatrikLundell]

The "foreign" flag indicates whether the item isn't fortress made, but doesn't have much of an effect apart from that. Selling things with the foreign flag doesn't count as sold products or fortress production values, I think. Thinks marked a forbidden and/or trader won't be affected by being dump marked, i.e. they won't be touched (and "artifacts" can't be dump marked using the vanilla DF interface). Thus, xpi0t0s' report sounds odd based on my experience.

I believe you can "disguise" foreign "stolen" goods (such as the junk from scuttled caravans) by modify them via encrusting, and melting them down won't retain the origin of the metal. These activities require the dorfs to handle them, though, and thus can't be performed if they won't even touch the items.

[dwarfish]

Assign it to a display pedestal in your library, then unassign or deconstruct the pedestal after the book has been stored.

doesn't show up in tools or artifacts for my display cases or pedestals.

The "foreign" flag indicates whether the item isn't fortress made, but doesn't have much of an effect apart from that. Selling things with the foreign flag doesn't count as sold products or fortress production values, I think. Thinks marked a forbidden and/or trader won't be affected by being dump marked, i.e. they won't be touched (and "artifacts" can't be dump marked using the vanilla DF interface). Thus, xpi0t0s' report sounds odd based on my experience.

I believe you can "disguise" foreign "stolen" goods (such as the junk from scuttled caravans) by modify them via encrusting, and melting them down won't retain the origin of the metal. These activities require the dorfs to handle them, though, and thus can't be performed if they won't even touch the items.

how do you guys advanced trouble shoot items using dfhack? how do you run custom scripts in dfhack? also what is the one used to remove foreign flags?

is anyone else getting a bug with scrolls like this or is it just me? (also for some reason it doesn't seem to affect codices, only scrolls)

[PatrikLundell]

gui/gm-editor is the standard tool for investigating DFHack structures, and it also allows you to manipulate the structures (including changing flags and other values). Once I've figured out what I want to do, I write a script to do it (assuming it's something I want to do again, of course).

You run scripts from the DFHack console by typing their names (without the suffix) in the console window. Many scripts need to know what they should operate on (e.g. a specific codex, or a dwarf), and thus are written to act on the item that DF currently selects (with one of the selection keys), while others operate on the current state (such as the one I posted above, which just looks through everything on the embark).

I assume the reason this happens only for scrolls is that whatever logic the game uses to give visitors "books" only gives them scrolls (or at least give them codices so rarely I haven't bothered to look for codices in my script).

As indicated, I do get the issue, but have never seen the foreign flag being a factor.

[dwarfish]

managed to get the script to work. but i don't know how to run a function, so i pasted the insides of the script itself into a fresh lua script and it seemed to work.

i can't find any documentation for many lua scripts for dwarf fortress. is there a way to get reference to a list of items by category instead of using df.global.world.items.all ?

[Bumber]

i can't find any documentation for many lua scripts for dwarf fortress. is there a way to get reference to a list of items by category instead of using df.global.world.items.all ?

Looks like "df.global.world.items.other" does that. Typing ":lua ~df.global.world.items.other" in dfhack with a fort running gives a bunch of vectors of items of each type.

"df.global.world.items.other.BOOK" is for codices. "df.global.world.items.other.TOOL" gives all tools, so you'd still have to check the subtype of each tool in that list anyway.

[pganon]

I had the same problem and solved it without any hacks:

Like all items dropped by invaders, the artefacts are forbidden. The shortcut k-f does not work on them, you need to view with k, then hit enter for full-screen view, then f to unforbid. Half my library is full of goblin prose...

[Libash_Thunderhead]

Well I know this topic is old.
But I just found recently if you build a library over the book, they will still be able to read the book.
Additionally, if you already have a library, you can paint a meeting area zone over the book and assign the zone to the library, a dwarf may carry the book to a table inside the main library to read it and leave it there. After that you can remove the one-tile zone.

[Goldbeard]

Assign it to a display pedestal in your library, then unassign or deconstruct the pedestal after the book has been stored.

This also works when dorfs don't recognize items lying around on a reclaimed fortress.