Print

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

[PatrikLundell]

@martinuzz: Yes, it's possible, and I think there was a discussion recently where someone wanted to do something similar.
I've got the script parts to get the preferences, so it should be a matter of just applying that to all units while filtering out visitors. I'm not sure whether it would include or exclude residents, though (I don't think I've got any in my saves). I should probably be able to put something together today.

Edit:
OK, here's an attempt:

Spoiler (click to show/hide)

Code: [Select]

[code]function add (list, item)
  for i, element in ipairs (list) do
    if element == item then
      return
    end
  end
 
  table.insert (list, item)
end

-----------------------------

function sort (list)
  local temp
 
  for i = 1, #list - 1 do
    for k = i + 1, #list do
      if list [k] < list [i] then
        temp = list [i]
        list [i] = list [k]
        list [k] = temp
      end
    end
  end
end

-----------------------------

function favored_food ()
  local my_civ = df.global.world.world_data.active_site [0].entity_links [0].entity_id
  local foods = {}
  local drinks = {}
 
  for i, unit in ipairs (df.global.world.units.all) do
    if not unit.flags1.dead and
       not unit.flags1.tame and
       not unit.flags2.killed and
       --unit.flags2.resident to be used somehow?
       not unit.flags2.visitor and
       unit.civ_id == my_civ then
      if unit.status.current_soul then
        for i, preference in ipairs (unit.status.current_soul.preferences) do
          if preference.active then
            if preference.type == df.unit_preference.T_type.LikeFood then
              local material = dfhack.matinfo.decode (preference.mattype, preference.matindex)
             
              if preference.matindex ~= -1 and
                 (material.mode == "plant" or
                  material.mode == "creature") then
                if preference.item_type == df.item_type.DRINK or
                   preference.item_type == df.item_type.LIQUID_MISC then  --  The state in the preferences seems locked to Solid                   
                  add (drinks, material.material.state_name.Liquid:lower ())
             
                else
                  if material.material.prefix == "" then
                    add (foods, material.material.state_name.Solid:lower ())
                 
                  else
                    add (foods, material.material.prefix:lower ())
                  end
                end           
           
              else
                add (foods, df.global.world.raws.creatures.all [preference.mattype].name [0]:lower ())
              end
            end           
          end
        end
      end
    end
  end
 
  sort (drinks)
  sort (foods)
 
  dfhack.println ("Drink preferences in the fortress:")
  for i, drink in ipairs (drinks) do
    dfhack.println (drink)
  end
 
  dfhack.println ()
  dfhack.println ("Food preferences in the fortress:")
  for i, food in ipairs (foods) do
    dfhack.println (food)
  end
end

favored_food ()[/code]

[Novaris]

I started a new fortress in the altest release and am now waiting for the caravan and siegers to arrive. I hope that I can reproduce the issue /or can confirm that autosave wasn't the issue. I'll keep you posted and upload the save if confirmed.

[Rumrusher]

so yeah it seems like quicksave Quickens armies you send to return back home in the 44.05 version of the game.
though I kinda was wondering what was crashing the game for a bit

[Novaris]

Do you see the same with a save/load cycle?

[Rumrusher]

Do you see the same with a save/load cycle?

just booted up a save where I sent a queen to a 9 day hike and yeah looks like the game just brought them back instantly.
kinda wonder if save and load skips the timer on these and or either returns everyone to their last Site which for raid parties from fort mode means they return to the fort?
seems like this could be used to speed up sieging sites. now if there was only a way to Tell your army to Murder everyone at the site and not try to steal artifacts.

[lethosor]

Rumrusher, you're talking about something (probably) different from the issue with caravans/migrants/etc. not arriving properly. (And sounds like it's not quicksave-specific, in any case.)

Martinuzz: it turns out that you can search for preference types in the "dwarfmonitor prefs" screen - does this help?

Spoiler (click to show/hide)

Note that you can get to this screen with Alt-M from the main fortress mode screen (with the default keybindings, anyway).

[flyteofheart]

Anyone here know how to make legends export to a diff folder? I dont like that it just dumps a shitton of stuff into the main DF folder. i would love if I could 'exportlegends all" -> into a legends export folder. even better if i can make each regions export go into a different sub folder but its ok if it doesnt do that.

[lethosor]

It's not possible right now, but it could be added.

[jecowa]

How many items does it make when exporting legends? I wish the vanilla exports would also go into a folder. I always print an image of my world after generating a new world. Might not be as important to print those anymore now that there's an in-game map, though.

[lethosor]

Looks like "exportlegends info" exports 3 XML files, 2 text files, and a bitmap image (note that this is from running it some time ago, so I might be a bit off). I think "exportlegends maps" can export a lot of images, depending on the world.

Note that the exportlegends script only has control over where the "...legends_plus.xml" file is saved. DF writes the rest of them, and they all go in the DF folder. exportlegends could probably move them afterward, but it might be a little tricky because DF truncates region names in those filenames to 20 characters (except ...world_gen_param.txt).

[martinuzz]

Rumrusher, you're talking about something (probably) different from the issue with caravans/migrants/etc. not arriving properly. (And sounds like it's not quicksave-specific, in any case.)

Martinuzz: it turns out that you can search for preference types in the "dwarfmonitor prefs" screen - does this help?

Spoiler (click to show/hide)

Note that you can get to this screen with Alt-M from the main fortress mode screen (with the default keybindings, anyway).

Oh awesome! That's basically what I asked for, I see I should have searched harder, for it's already there!

[strainer]

@PatrikLundell

Would you be able to push the histfig relationships.list structural info? I had a look but not sure where to alter. Im using the anon names at the moment but think its a good idea for these to be updated soon.

These names would work:
relationships.list(#).anon_3 : attitude //or standing
relationships.list(#).anon_4 : counter //(experience)
relationships.list(#).anon_5 : position //(display)

And the enum for the attitude codes:

Code: [Select]

relations_list_attitude_type : int16_t

None = -1,
Hero,
Friend,
Grudge,
Bonded,
ConsidersViolent,
ConsidersPsychotic,
GoodForBusiness,
FriendlyTerms,
ConsidersKiller,
ConsidersMurderer,
Comrade,
MemberOfRespectedGroup,
MemberOfHatedGroup, 
EnemyFighter, 
FriendlyFighter, 
ConsidersBully, 
ConsidersBrigand, 
LoyalSoldier, 
ConsidersMonster,
ConsidersStoryteller,
ConsidersPoet,
ConsidersBard,
ConsidersDancer,
ConsidersQuarreler,
ConsidersFlatterer,
Hunter,
ProtectorOfTheWeak

[PatrikLundell]

@strainer: The main reason I haven't generated a "pull request" is that there was an unknown hole in the anon_3 enum type (which you're filling in), and because I still don't understand the role of anon_4.
However, I guess we're not getting further for the time being, so I'll make an attempt.

[strainer]

No pressure Patrick, i just thought id bring it up again. I dont know whats done with that counter either, but seems safe to call it counter. And I have observed the keys which are filled in. There is some mechanism involving the counter which juggles the most important 'attitude' or decides friendly terms or whatever, but it may be guessed/ resolved later.

[PatrikLundell]

Well, I've made a "pull request", so we'll see what the judges say.
The enum type actually did exist already. Slightly different names, but the same values (plus two additional ones at the end, one of which I think was Thief). The enum was used for the reputation structure nearby, so it's a fair bet it's really the same type used in both cases.
I changed the name of "position" to "rank", and added a comment block trying to summarize the sort order determination, as well as that being based on limited data. I also mentioned that the function of "counter" was unknown.