40d:Cheating - Revision history

Quietust: upon closer investigation, 40d cleared data/save/current on startup - it was only the "cancel embark" workflow that could lead to corruption (primarily in version 0.31.xx)

2022-05-09T17:24:47Z

upon closer investigation, 40d cleared data/save/current on startup - it was only the "cancel embark" workflow that could lead to corruption (primarily in version 0.31.xx)

Quietust: /* Savescumming */ pretty sure you needed to nuke the "current" folder in this version, otherwise the next Save could pick up extra garbage and corrupt the world

2022-05-09T16:48:03Z

Savescumming: pretty sure you needed to nuke the "current" folder in this version, otherwise the next Save could pick up extra garbage and corrupt the world

207.237.241.211: /* Memory Editing */

2013-10-21T04:46:44Z

Memory Editing

Timrem: Undo revision 164356 by 192.168.255.3 (talk)

2012-02-19T23:28:22Z

Undo revision 164356 by 192.168.255.3 (talk)

192.168.255.3: /* Savescumming */

2012-02-19T21:49:20Z

Savescumming

QuietBot: Fixing links within namespace (0401/2470)

2011-12-08T14:38:19Z

Fixing links within namespace (0401/2470)

Quietust at 19:28, 12 August 2010

2010-08-12T19:28:53Z

209.237.95.175: fixed memory editing link at the end so that it goes to the 40d memory editing page

2010-07-04T22:52:35Z

fixed memory editing link at the end so that it goes to the 40d memory editing page

QuietBot: Fixing quality template tags (220/690)

2010-05-07T04:42:13Z

Fixing quality template tags (220/690)

67.168.32.242: /* Reaction Additions */

2010-05-03T15:48:26Z

Reaction Additions

@@ Line 212: / Line 212: @@
 Savescumming refers to the practice of regularly backing up your saves so you can revert to one if your fortress crumbles to the last. This can be toggled to be done automatically in the init file, so some might not consider this to be cheating.
-Another method to save scum is open up task manager (ctrl+alt+delete) and open the Processes tab, and then selecting dwarfort.exe and clicking on end task. This will cause Dwarf Fortress to close, reverting to the last saved game. Whenever you do this, be sure to delete the contents of the "data/save/current" folder, otherwise the next time you Save you could end up corrupting your world.
+Another method to save scum is open up task manager (ctrl+alt+delete) and open the Processes tab, and then selecting dwarfort.exe and clicking on end task. This will cause Dwarf Fortress to close, reverting to the last saved game.
 On Linux, since the game binary (named dwarfort.exe) is launched via a script wrapper (named df), simply closing the launched script does not work as the actual game will continue to run. However, closing dwarfort.exe is possible in a number of ways:

@@ Line 212: / Line 212: @@
 Savescumming refers to the practice of regularly backing up your saves so you can revert to one if your fortress crumbles to the last. This can be toggled to be done automatically in the init file, so some might not consider this to be cheating.
-Another method to save scum is open up task manager (ctrl+alt+delete) and open the Processes tab, and then selecting dwarfort.exe and clicking on end task. This will cause dwarf fortress to close, reverting to the last saved game. Back a long time ago, this could cause inflate errors and destroy the save-game, but Toady has solved the problem.
+Another method to save scum is open up task manager (ctrl+alt+delete) and open the Processes tab, and then selecting dwarfort.exe and clicking on end task. This will cause Dwarf Fortress to close, reverting to the last saved game. Whenever you do this, be sure to delete the contents of the "data/save/current" folder, otherwise the next time you Save you could end up corrupting your world.
 On Linux, since the game binary (named dwarfort.exe) is launched via a script wrapper (named df), simply closing the launched script does not work as the actual game will continue to run. However, closing dwarfort.exe is possible in a number of ways:
@@ Line 223: / Line 223: @@
       killall -9 dwarfort.exe
 =Memory Editing=

@@ Line 229: / Line 229: @@
 :''[[40d:Memory editing|Main article: Memory editing]]''
-Memory editing refers to using an external program to modify numbers within the game. This is at its most useful when choosing what to take with you, as you can give yourself an unlimited number of points. What doesn't work in the new version is giving your starting dwarves tons of prof skills, since there now is a limit in how many skills they can start with. You can still start your dwarves with all proficient skills, but you need to change the skill limit value first on every dwarf you want to do this with, also when editing the memory values with such programs as CheatEngine in adventure mode your point value is 4bytes but in fortress you have to change the search to 2bytes only for hex editors though
+Memory editing refers to using an external program to modify numbers within the game. This is at its most useful when choosing what to take with you, as you can give yourself an unlimited number of points. What doesn't work in the new version is giving your starting dwarves tons of prof skills, since there now is a limit in how many skills they can start with. You can still start your dwarves with all proficient skills, but you need to change the [skill limit value] (What?) first on every dwarf you want to do this with, also when editing the memory values with such programs as CheatEngine in adventure mode your point value is 4bytes but in fortress you have to change the search to 2bytes only for hex editors though
 The [[utilities]] page has several tools that do specific memory hacks, such as to teleport a creature.

@@ Line 212: / Line 212: @@
 Savescumming refers to the practice of regularly backing up your saves so you can revert to one if your fortress crumbles to the last. This can be toggled to be done automatically in the init file, so some might not consider this to be cheating.
-Another method to save scum is open up task manager (ctrl+shift+esc) and open the Processes tab, and then selecting dwarfort.exe and clicking on end task. This will cause dwarf fortress to close, reverting to the last saved game. Back a long time ago, this could cause inflate errors and destroy the save-game, but Toady has solved the problem.
+Another method to save scum is open up task manager (ctrl+alt+delete) and open the Processes tab, and then selecting dwarfort.exe and clicking on end task. This will cause dwarf fortress to close, reverting to the last saved game. Back a long time ago, this could cause inflate errors and destroy the save-game, but Toady has solved the problem.
 On Linux, since the game binary (named dwarfort.exe) is launched via a script wrapper (named df), simply closing the launched script does not work as the actual game will continue to run. However, closing dwarfort.exe is possible in a number of ways:
@@ Line 223: / Line 223: @@
       killall -9 dwarfort.exe
 =Memory Editing=

@@ Line 212: / Line 212: @@
 Savescumming refers to the practice of regularly backing up your saves so you can revert to one if your fortress crumbles to the last. This can be toggled to be done automatically in the init file, so some might not consider this to be cheating.
-Another method to save scum is open up task manager (ctrl+alt+delete) and open the Processes tab, and then selecting dwarfort.exe and clicking on end task. This will cause dwarf fortress to close, reverting to the last saved game. Back a long time ago, this could cause inflate errors and destroy the save-game, but Toady has solved the problem.
+Another method to save scum is open up task manager (ctrl+shift+esc) and open the Processes tab, and then selecting dwarfort.exe and clicking on end task. This will cause dwarf fortress to close, reverting to the last saved game. Back a long time ago, this could cause inflate errors and destroy the save-game, but Toady has solved the problem.
 On Linux, since the game binary (named dwarfort.exe) is launched via a script wrapper (named df), simply closing the launched script does not work as the actual game will continue to run. However, closing dwarfort.exe is possible in a number of ways:
@@ Line 223: / Line 223: @@
       killall -9 dwarfort.exe
 =Memory Editing=

@@ Line 3: / Line 3: @@
 {{mod}}
-'''Cheating''' is altering the game to make dwarf fortress easier. This is distinctly different from [[exploits]]. There are two main ways to alter the game: changing the game's raw source files (which are really just text files), and directly altering the game's memory (which requires special tools).
+'''Cheating''' is altering the game to make dwarf fortress easier. This is distinctly different from [[Main:exploits|exploits]]. There are two main ways to alter the game: changing the game's raw source files (which are really just text files), and directly altering the game's memory (which requires special tools).
 =File Edits=
@@ Line 19: / Line 19: @@
 Raw files are located in the raw/objects directory
-See also: {{L|Material token}}, {{L|Creature token}}, {{L|Matgloss token}}, and {{L|Reactions}} for making your own custom cheats.
+See also: [[Material token]], [[Creature token]], [[Matgloss token]], and [[Reactions]] for making your own custom cheats.
 ==Reaction Additions==
@@ Line 179: / Line 179: @@
       [ITEMCORPSE:ARMOR:ITEM_ARMOR_CHAINMAIL:METAL: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 (and by highly likely extension, fortress), which has immense and obvious cheating potential.  You may want to take a look at the {{L|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 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 (and by highly likely extension, 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).
 Another example:
@@ Line 188: / Line 188: @@
 ===Super-Fast Dwarves===
-If you believe your dwarves are a bit too slow, try opening the following {{L|creature token}} file...
+If you believe your dwarves are a bit too slow, try opening the following [[creature token]] file...
 <pre>\raw\objects\creature_standard.txt</pre> ...and adding '''[SPEED:1]''' (or SPEED:0 if you're up to some psychedelic light speed traveling)  somewhere after '''[CREATURE:DWARF]''' but before the next '''[CREATURE]''' entry. *NEW RELEASE EDIT*  Find [HOMEOTHERM:#####] and add [SPEED:###] edit the "#" and replace with desired value ((found by looking at creature fairy) edit if needed)
 This will make your dwarves do the majority of their actions '''''super''''' fast, including moving, digging and workshop actions.
@@ Line 231: / Line 231: @@
 Memory editing refers to using an external program to modify numbers within the game. This is at its most useful when choosing what to take with you, as you can give yourself an unlimited number of points. What doesn't work in the new version is giving your starting dwarves tons of prof skills, since there now is a limit in how many skills they can start with. You can still start your dwarves with all proficient skills, but you need to change the skill limit value first on every dwarf you want to do this with, also when editing the memory values with such programs as CheatEngine in adventure mode your point value is 4bytes but in fortress you have to change the search to 2bytes only for hex editors though
-The {{L|utilities}} page has several tools that do specific memory hacks, such as to teleport a creature.
+The [[utilities]] page has several tools that do specific memory hacks, such as to teleport a creature.
 Editing the memory of a game has a possibility to cause the game to crash or misbehave, including corrupting of saves.

@@ Line 1: / Line 1: @@
 {{av}}
-{{human}}
+{{Quality|Exceptional}}
 {{mod}}

← Older revision		Revision as of 15:48, 3 May 2010
Line 155:		Line 155:

	These cheats do not require a new world (because they only modify existing reactions), and allow my smelters to create steel and adamantine from nothing. It's probably easier, though, to mod some bulk stone into the ore you need and go from there.		These cheats do not require a new world (because they only modify existing reactions), and allow my smelters to create steel and adamantine from nothing. It's probably easier, though, to mod some bulk stone into the ore you need and go from there.
		+
		+	===Ultimate Smelter Cheat===
		+	Since it's easy enough to alter smelter reactions, one can build a single multi-purpose reaction as follows:
		+	[REACTION:CHEAT_HORRIBLY]
		+	[NAME:prospect bulk stone]
		+	[SMELTER][FUEL]
		+	[REAGENT:1:REACTION_CLASS:JUNK]
		+	[PRODUCT:100:1:BAR:NO_SUBTYPE:METAL:COPPER]
		+	where any bulk stone you want to destroy is labeled REACTION_CLASS:JUNK, and PRODUCT is whatever you want; turtle shells, rough rock crystals, platinum, whatever you need. No need to make lots of reactions just for gems, no need to modify existing reactions.

	==Creature Token Modifications==		==Creature Token Modifications==