v50 Steam/Premium information for editors
  • v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
  • Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.

Editing Wagon

Jump to navigation Jump to search

Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.

If you are creating a redirect to the current version's page, do not use any namespace. For example: use #REDIRECT [[Cat]], not #REDIRECT [[Main:Cat]] or #REDIRECT [[cv:Cat]]. See DF:Versions for more information.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 107: Line 107:
 
As of v50.05, there are two requirements for a caravan to bring wagons for their goods.
 
As of v50.05, there are two requirements for a caravan to bring wagons for their goods.
  
The first is that the civilization has access to wagons through their KILL_PLANT [[ethic]] response (which is why [[elf|Elves]] lack wagons), as well as wagon pullers through the [[Entity_token#COMMON_DOMESTIC_PULL|COMMON_DOMESTIC_PULL]] token. Both of these tokens can easily be added to vanilla civs by modifying the game's raws, though the former will alter their behavior during [[trade]].
+
The first is that the civilization has access to wagon pullers through the [[Entity_token#COMMON_DOMESTIC_PULL|COMMON_DOMESTIC_PULL]] token. (The fact that elves lack this token in vanilla may be mistaken as the reason they do not bring wagons, but the real reason is because of their [[ethic]]s). This token can easily be added to vanilla civs by modifying the game's raws.
  
 
The second is that the player's fort is either the current home of the [[monarch]] or that the site has been elevated to a landholding with an on-site living landholder such as a [[baron]], [[count]] or [[duke]]. Currently, these landholder titles corresponding to player forts will never be inherited, so if the holder of the title dies and the player's fort is not the residence of the monarch, caravans will permanently stop bringing wagons.
 
The second is that the player's fort is either the current home of the [[monarch]] or that the site has been elevated to a landholding with an on-site living landholder such as a [[baron]], [[count]] or [[duke]]. Currently, these landholder titles corresponding to player forts will never be inherited, so if the holder of the title dies and the player's fort is not the residence of the monarch, caravans will permanently stop bringing wagons.
Line 113: Line 113:
 
Players using [[DFHack]] can work around the second issue by using the ``gui/gm-editor`` tool to edit the title assignment so that the title is reassigned to another (preferably less ''dead'') historical figure.
 
Players using [[DFHack]] can work around the second issue by using the ``gui/gm-editor`` tool to edit the title assignment so that the title is reassigned to another (preferably less ''dead'') historical figure.
  
Step by step instructions for fixing a corrupted or dead landholder position '''as of v50.05 and DFHack 50.05-alpha3.1''':
+
Step by step instructions for fixing a corrupted or dead landholder position ***as of v50.05 and DFHack 50.05-alpha3.1***:
  
# Backup your saves. The ``gm-editor`` tool can cause irreversible save file corruption.
+
1. Backup your saves. The ``gm-editor`` tool can cause irreversible save file corruption.
# Select the unit you wish to make into a noble and run ``gui/gm-editor`` from the DFHack terminal or launcher. This will bring up a page where you can (s)earch for the unit's ``hist_figure_id``. Write down this id, which from now on will be referred to as ``desired_histfig_id`` in this guide.
+
 
# Now that you have the required hist_fig_id, run ``gui/gm-editor df.historical_entity.find(df.global.plotinfo.civ_id).positions.own``. This a list of '''types''' of titles your civilization can give out (e.g. monarch, duke). Find the entry with ``code`` equal to your desired position (e.g. ``COUNT``, ``DUKE``, ``BARON``). Note the ``id`` for this entry, which from now on will be referred to as ``desired_position_id`` in this guide.
+
2. Select the unit you wish to make into a noble and run ``gui/gm-editor`` from the DFHack terminal or launcher. This will bring up a page where you can (s)earch for the unit's ``hist_figure_id``. Write down this id, which from now on will be referred to as ``desired_histfig_id`` in this guide.
# Run ``gui/gm-editor df.global.plotinfo``. (s)earch for both ``civ_id`` (write this down for later, we will call it ``desired_civ_id``) and ``site_id`` (write down as well, we will call it ``desired_site_id``).
+
 
# Run ``gui/gm-editor df.world_site.find(df.global.plotinfo.site_id).entity_links``. Find the link here where ``entity_id`` is equal to ``desired_civ_id``. This is the game's information for connections between your site and your civ. Write down the value in ``position_profile_id``; we will refer this to ``desired_position_assignment_id`` in this guide.
+
3. Now that you have the required hist_fig_id, run ``gui/gm-editor df.historical_entity.find(df.global.plotinfo.civ_id).positions.own``. This a list of **types** of titles your civilization can give out (e.g. monarch, duke). Find the entry with ``code`` equal to your desired position (e.g. ``COUNT``, ``DUKE``, ``BARON``). Note the ``id`` for this entry, which from now on will be referred to as ``desired_position_id`` in this guide.
# Run ``gui/gm-editor df.historical_entity.find(df.global.plotinfo.civ_id).positions.assignments``. This is a list of '''actual titles''' given out by your civ. Find the entry where ``id`` is equal to ``desired_position_assignment_id`` (in these entries, confusingly, ``id`` is the position_assignment_id, and ``position_id`` is the id of the '''type''' of title in ``positions.own`` from step 3.) This entry is the actual created title for your site (e.g. "Count of Boatmurders"), while the entry from step 3 is essentially just the information for "A count". Here you can replace `histfig` and `histfig2` with ``desired_histfig_id`` from step 2. The game should immediately after this recognize the new noble and display them in the nobles screen, but the noble will '''not''' recognize this title in their ``groups`` tab until you follow the final steps.
+
 
# Run ``gui/gm-editor df.historical_figure.find(<desired_histfig_id>).entity_links``. This is essentially where civ-level information on the unit's ``groups`` tab is stored. Use Alt+i to insert a new value; enter the type name ``histfig_entity_link_positionst`` when prompted. Once the value is created, open it. Enter ``desired_civ_id`` from step 4 as ``entity_id``, enter ``100`` for ``link_strength``, enter ``desired_position_assignment_id`` for ``assignment_id``. ``start_year`` is up to you; this is what legends will use to determine the date this character was elevated to a noble. The current year is the simplest option, though any year after the site's founding and where the desired noble is an adult will work fine.
+
4. Run ``gui/gm-editor df.global.plotinfo``. (s)earch for both ``civ_id`` (write this down for later, we will call it ``desired_civ_id``) and ``site_id`` (write down as well, we will call it ``desired_site_id``).
 +
 
 +
5. Run ``gui/gm-editor df.world_site.find(df.global.plotinfo.site_id).entity_links``. Find the link here where ``entity_id`` is equal to ``desired_civ_id``. This is the game's information for connections between your site and your civ. Write down the value in ``position_profile_id``; we will refer this to ``desired_position_assignment_id`` in this guide.
 +
 
 +
6. Run ``gui/gm-editor df.historical_entity.find(df.global.plotinfo.civ_id).positions.assignments``. This is a list of **actual titles** given out by your civ. Find the entry where ``id`` is equal to ``desired_position_assignment_id`` (in these entries, confusingly, ``id`` is the position_assignment_id, and ``position_id`` is the id of the **type** of title in ``positions.own`` from step 3.) This entry is the actual created title for your site (e.g. "Count of Boatmurders"), while the entry from step 3 is essentially just the information for "A count". Here you can replace `histfig` and `histfig2` with ``desired_histfig_id`` from step 2. The game should immediately after this recognize the new noble and display them in the nobles screen, but the noble will **not** recognize this title in their ``groups`` tab until you follow the final steps.
 +
 
 +
7. Run ``gui/gm-editor df.historical_figure.find(<desired_histfig_id>).entity_links``. This is essentially where civ-level information on the unit's ``groups`` tab is stored. Use Alt+i to insert a new value; enter the type name ``histfig_entity_link_positionst`` when prompted. Once the value is created, open it. Enter ``desired_civ_id`` from step 4 as ``entity_id``, enter ``100`` for ``link_strength``, enter ``desired_position_assignment_id`` for ``assignment_id``. ``start_year`` is up to you; this is what legends will use to determine the date this character was elevated to a noble. The current year is the simplest option, though any year after the site's founding and where the desired noble is an adult will work fine.
  
 
Update '''as of v51.10-beta and DFHACK v51.10-beta2''', I was able to figure out a VERY EXPERIMENTAL way to do this when the fortress has never had a baron(ness) before:
 
Update '''as of v51.10-beta and DFHACK v51.10-beta2''', I was able to figure out a VERY EXPERIMENTAL way to do this when the fortress has never had a baron(ness) before:

Please note that all contributions to Dwarf Fortress Wiki are considered to be released under the GFDL & MIT (see Dwarf Fortress Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)

Templates used on this page:

This page is a member of 2 hidden categories: