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 23a:Cheating
Jump to navigation
Jump to search
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
You are editing a page for an older version of Dwarf Fortress ("Main" is the current version, not "23a"). Please make sure you intend to do this. If you are here by mistake, see the current page instead.
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 7: | Line 7: | ||
=File Edits= | =File Edits= | ||
− | The most common use of editing raw files is to get free items. | + | The most common use of editing raw files is to get free items, such as gems, adamantine, or flux. |
When changing the raw files, you may or may not need to create a new world in order for your changes to be reflected. | When changing the raw files, you may or may not need to create a new world in order for your changes to be reflected. | ||
Line 15: | Line 15: | ||
Worlds created before the modifications were made won't be playable unless the previous version of the raw file is restored. Save your custom raw files if you want to continue playing your game at some future point. | Worlds created before the modifications were made won't be playable unless the previous version of the raw file is restored. Save your custom raw files if you want to continue playing your game at some future point. | ||
− | + | Attempting to play worlds not generated with identical reaction additions will fail on load. | |
− | See also: [[Material token]] and [[ | + | Raw files are located in the raw/objects directory |
+ | |||
+ | See also: [[Material token]], [[Creature token]], and [[Matgloss token]] for making your own custom cheats. | ||
==Creature Token Modifications== | ==Creature Token Modifications== | ||
Line 31: | Line 33: | ||
Add something like this to their creature entries. | Add something like this to their creature entries. | ||
− | + | [ITEMCORPSE:ARMOR:ITEM_ARMOR_CHAINMAIL:ADAMANTINE] | |
− | + | [ITEMCORPSE_QUALITY:5] | |
+ | Note that you do ''not'' need to make a new world for this to work, and that you can even change this entry in-between saves on the same adventurer or fortress, which has immense and obvious cheating potential. You may want to take a look at the [[Item token]] page for a better general understanding of the ITEMCORPSE tag; ITEMCORPSE_QUALITY, on the other hand, simply ranges from 0 (no quality modifier) to 5 (masterpiece quality). | ||
− | Note that | + | Note that this technique can only be used to create items made of obsidian (with USE_SHARPSTONE), glass, metal (including ores), and various other hardcoded materials (e.g. ash, potash, or pearlash). |
− | + | It is also possible to create creature/plant items (such as meat, fish, seeds, bones, or shells) for the first 49 creatures/plants defined in the raws by specifying the [[material token]] with a matching index. For example, you could create "cow shells" by specifying [ITEMCORPSE:SHELL:NO_SUBTYPE:GEM_RARE]; very useful if you have no shelled animals in your fortress area and your mastercrafter gets an unlucky Strange Mood. | |
===Super-Fast Dwarves=== | ===Super-Fast Dwarves=== | ||
Line 58: | Line 61: | ||
Savescumming refers to the practice of regularly backing up your saves so you can revert to one if your fortress crumbles to the last. As the documentation suggests doing this anyways (in case of save corruption), some might not consider this to be cheating. | Savescumming refers to the practice of regularly backing up your saves so you can revert to one if your fortress crumbles to the last. As the documentation suggests doing this anyways (in case of save corruption), some might not consider this to be cheating. | ||
− | Unlike in newer versions, killing dwarfort.exe from Task Manager is '''not''' safe and can easily result in | + | Unlike in newer versions, killing dwarfort.exe from Task Manager is '''not''' safe and can easily result in Nemesis Unit Load Errors, as the data files for a given world are modified ''in-place'' during gameplay (rather than being staged to a temporary folder and then merged back in when saving, as later versions do). |
=Memory Editing= | =Memory Editing= |