User Tools

Site Tools


dm_commands

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dm_commands [2022/09/25 12:22]
leaf [wizhelp]
dm_commands [2024/06/05 14:22] (current)
leaf Format updates, added some forced line breaks and removed white spacing
Line 30: Line 30:
  
 ==== addexp ==== ==== addexp ====
 +
 The command addexp can either add or subtract a specified amount of experience to a player in the game, to any skill they have access to (i.e., praying because they have a holy symbol) or have learned (i.e., skill scroll of punching) or started with as part of their race (i.e., wraith feed for a wraith) or class (i.e., flame touch for a fireborn.) ​ The command addexp can either add or subtract a specified amount of experience to a player in the game, to any skill they have access to (i.e., praying because they have a holy symbol) or have learned (i.e., skill scroll of punching) or started with as part of their race (i.e., wraith feed for a wraith) or class (i.e., flame touch for a fireborn.) ​
  
Line 104: Line 105:
 Creating wands/​staves/​scrolls/​etc with specific spells is done in the same manner as an artifact. Creating wands/​staves/​scrolls/​etc with specific spells is done in the same manner as an artifact.
  
-See Also: [[#dump]]+See Also: [[#dump]]\\
 See Also: [[#​patch]] ​ See Also: [[#​patch]] ​
 +
 ==== debug ==== ==== debug ====
  
Line 125: Line 127:
  
 The default value is debug 1 The default value is debug 1
 +
 ==== dump ==== ==== dump ====
  
Line 176: Line 179:
 Usage: dumpabove Usage: dumpabove
  
-See Also: [[#​patch]] +See Also: [[#patch]]\\ 
-See Also: [[#​dumpallarchtypes]] +See Also: [[#​dumpallarchtypes]]\\ 
-See Also: [[#​dumpallmaps]] +See Also: [[#​dumpallmaps]]\\ 
-See Also: [[#​dumpallobjects]] +See Also: [[#​dumpallobjects]]\\ 
-See Also: [[#​dumpbelow]]+See Also: [[#​dumpbelow]]\\
 See Also: [[#​dumpfriendlyobjects]] See Also: [[#​dumpfriendlyobjects]]
  
Line 189: Line 192:
 Usage: dumpallarchtypes Usage: dumpallarchtypes
  
-See Also: [[#​patch]] +See Also: [[#patch]]\\ 
-See Also: [[#​dumpabove]] +See Also: [[#​dumpabove]]\\ 
-See Also: [[#​dumpallmaps]] +See Also: [[#​dumpallmaps]]\\ 
-See Also: [[#​dumpallobjects]] +See Also: [[#​dumpallobjects]]\\ 
-See Also: [[#​dumpbelow]]+See Also: [[#​dumpbelow]]\\
 See Also: [[#​dumpfriendlyobjects]] See Also: [[#​dumpfriendlyobjects]]
  
Line 202: Line 205:
 Usage: dumpbelow Usage: dumpbelow
  
-See Also: [[#​patch]] +See Also: [[#patch]]\\ 
-See Also: [[#​dumpabove]] +See Also: [[#​dumpabove]]\\ 
-See Also: [[#​dumpallarchtypes]] +See Also: [[#​dumpallarchtypes]]\\ 
-See Also: [[#​dumpallmaps]] +See Also: [[#​dumpallmaps]]\\ 
-See Also: [[#​dumpallobjects]]+See Also: [[#​dumpallobjects]]\\
 See Also: [[#​dumpfriendlyobjects]] See Also: [[#​dumpfriendlyobjects]]
  
Line 215: Line 218:
 Usage: dumpallmaps Usage: dumpallmaps
  
-See Also: [[#​patch]] +See Also: [[#patch]]\\ 
-See Also: [[#​dumpabove]] +See Also: [[#​dumpabove]]\\ 
-See Also: [[#​dumpallarchtypes]] +See Also: [[#​dumpallarchtypes]]\\ 
-See Also: [[#​dumpallobjects]] +See Also: [[#​dumpallobjects]]\\ 
-See Also: [[#​dumpbelow]]+See Also: [[#​dumpbelow]]\\
 See Also: [[#​dumpfriendlyobjects]] See Also: [[#​dumpfriendlyobjects]]
 +
 ==== dumpallobjects ==== ==== dumpallobjects ====
  
Line 227: Line 231:
 Usage: dumpallobjects Usage: dumpallobjects
  
-See Also: [[#​patch]] +See Also: [[#patch]]\\ 
-See Also: [[#​dumpabove]] +See Also: [[#​dumpabove]]\\ 
-See Also: [[#​dumpallarchtypes]] +See Also: [[#​dumpallarchtypes]]\\ 
-See Also: [[#​dumpallmaps]] +See Also: [[#​dumpallmaps]]\\ 
-See Also: [[#​dumpbelow]]+See Also: [[#​dumpbelow]]\\
 See Also: [[#​dumpfriendlyobjects]] See Also: [[#​dumpfriendlyobjects]]
 +
 ==== dumpfriendlyobjects ==== ==== dumpfriendlyobjects ====
  
Line 239: Line 244:
 Usage: dumpfriendlyobjects Usage: dumpfriendlyobjects
  
-See Also: [[#​patch]] +See Also: [[#patch]]\\ 
-See Also: [[#​dumpabove]] +See Also: [[#​dumpabove]]\\ 
-See Also: [[#​dumpallarchtypes]] +See Also: [[#​dumpallarchtypes]]\\ 
-See Also: [[#​dumpallmaps]] +See Also: [[#​dumpallmaps]]\\ 
-See Also: [[#​dumpallobjects]] +See Also: [[#​dumpallobjects]]\\ 
-See Also: [[#​dumpbelow]]+See Also: [[#​dumpbelow]]\\
  
 ==== follow ==== ==== follow ====
 +
 The follow command allows a DM to follow a specified player and keeps the DM at four (4) or fewer squares away from a player (works better when hidden). The follow command allows a DM to follow a specified player and keeps the DM at four (4) or fewer squares away from a player (works better when hidden).
  
Line 328: Line 334:
  
 This will insert the 2nd item in the first. 2nd can't be a player. This will insert the 2nd item in the first. 2nd can't be a player.
 +
 ==== invisible ==== ==== invisible ====
  
Line 336: Line 343:
  
 Once the timer on the command expires, the DM will return to visible mode again. Once the timer on the command expires, the DM will return to visible mode again.
 +
 ==== kick ==== ==== kick ====
  
Line 370: Line 378:
 The DM character still has access to the granted spell even when they are not in DM mode - but still must meet the minimum casting requirements for the spell (i.e., proper level in praying, enough grace to cast the prayer, etc.) The DM character still has access to the granted spell even when they are not in DM mode - but still must meet the minimum casting requirements for the spell (i.e., proper level in praying, enough grace to cast the prayer, etc.)
  
-See Also: [[player_commands#​learn_spell|learn_spell]] +See Also: [[player_commands#​learn_spell|learn_spell]]\\ 
-See Also: [[player_commands#​nodm|nodm]]+See Also: [[player_commands#​nodm|nodm]]\\ 
 ==== learn_spell ==== ==== learn_spell ====
  
Line 407: Line 416:
  
 See Also: nodm See Also: nodm
 +
 ==== overlay_save ==== ==== overlay_save ====
 +
 syntax: overlay_save syntax: overlay_save
  
Line 436: Line 447:
 This will load a new plugin into memory. Using this with no arguments, or invalid arguments will cause a server crash. The plugin name should be as it appears in your plugin directory. Double-check the names before using plugins. This will load a new plugin into memory. Using this with no arguments, or invalid arguments will cause a server crash. The plugin name should be as it appears in your plugin directory. Double-check the names before using plugins.
  
-See Also: pluglist+See Also: pluglist\\
 See Also: plugout See Also: plugout
  
 ==== pluglist ==== ==== pluglist ====
 +
 syntax: pluglist syntax: pluglist
  
Line 450: Line 462:
 This will remove a loaded plugin from memory. This will remove a loaded plugin from memory.
  
-See Also: plugin+See Also: plugin\\
 See Also: pluglist See Also: pluglist
 +
 ==== possess ==== ==== possess ====
  
Line 464: Line 477:
 It is not suggested you try to possess another player, as bad things will undoubtably happen. It is not suggested you try to possess another player, as bad things will undoubtably happen.
  
-See Also: dump+See Also: dump\\
 See Also: mon_aggr See Also: mon_aggr
  
 ==== printlos ==== ==== printlos ====
 +
 syntax: printlos syntax: printlos
  
Line 482: Line 496:
 It is useful to change, via .quest file editing, the status of a quest for a player. It is useful to change, via .quest file editing, the status of a quest for a player.
  
-See Also: purge_quests+See Also: purge_quests\\
 See Also: quest See Also: quest
  
Line 495: Line 509:
 This is used to avoid restarting the server when a quest definition changes. This is used to avoid restarting the server when a quest definition changes.
  
-See Also: purge_quest_state+See Also: purge_quest_state\\
 See Also: quest See Also: quest
  
Line 511: Line 525:
 Note: (player name) may be a partial name as long as it isn't ambiguous. The player must be online. Note: (player name) may be a partial name as long as it isn't ambiguous. The player must be online.
  
-See Also: purge_quest_state+See Also: purge_quest_state\\
 See Also: purge_quests See Also: purge_quests
 +
 +==== recollect ====
 +
 +syntax: recollect
 +
 +NOTE: Experimental command - use with caution
 +
 +FIXME: the command is currently not documented as a help file in the game
 +
 +The recollect command will cause the server to run the archetype collection process again. An example for using this command is for testing new faces by comparing old faces with new ones without rebooting the server.
 +
 +Check the server logs for output related to this command since there currently is no output to the DM or through the game client in regard to running this command.
 +
 +Example server log output:
 +  Starting to collect assets from /​usr/​games/​crossfire/​share/​crossfire
 +  Finishing collecting assets from /​usr/​games/​crossfire/​share/​crossfire
  
 ==== remove ==== ==== remove ====
 +
 syntax: remove <tag> syntax: remove <tag>
  
Line 522: Line 553:
  
 ==== reset ==== ==== reset ====
 +
 syntax: ''​reset <​mapname>''​ or ''​reset .''​ or ''​reset full-reset <​mapname>''​ or ''​reset full-reset .''​ syntax: ''​reset <​mapname>''​ or ''​reset .''​ or ''​reset full-reset <​mapname>''​ or ''​reset full-reset .''​
  
Line 528: Line 560:
  
 === How to reset a unique map === === How to reset a unique map ===
 +
 Since revision 13938 (trunk) and 13939 (branch), ''​reset full-reset <​mapname>''​ enables to remove unique items from a map. Since revision 13938 (trunk) and 13939 (branch), ''​reset full-reset <​mapname>''​ enables to remove unique items from a map.
  
Line 533: Line 566:
  
 === How to reset a unique map (before those revisions) === === How to reset a unique map (before those revisions) ===
 +
 To reset a unique map, access to the server file system is needed. ​ Make sure all items of value are retrieved from the map before implementing the reset, or they will be lost.  When the map owner says all is clear, consider the example of trying to reset a python guild map (/​pup_land/​guilds/​purple_butterfly/​hallofjoining). To reset a unique map, access to the server file system is needed. ​ Make sure all items of value are retrieved from the map before implementing the reset, or they will be lost.  When the map owner says all is clear, consider the example of trying to reset a python guild map (/​pup_land/​guilds/​purple_butterfly/​hallofjoining).
  
Line 576: Line 610:
  
 ==== spellreset ==== ==== spellreset ====
 +
 syntax: spellreset syntax: spellreset
  
Line 581: Line 616:
  
 ==== ssdumptable ==== ==== ssdumptable ====
 +
 syntax: ssdumptable syntax: ssdumptable
  
Line 595: Line 631:
  
 The command would display all stats for the player Darla. The command would display all stats for the player Darla.
- 
- 
  
  
Line 617: Line 651:
 There is no '​reverse'​ summoning, except to go to a map yourself and summon the player again. There is no '​reverse'​ summoning, except to go to a map yourself and summon the player again.
  
-See Also: goto+See Also: goto\\
 See Also: teleport See Also: teleport
 +
 ==== teleport ==== ==== teleport ====
  
Line 630: Line 665:
  
 See Also: summon See Also: summon
 +
 ==== time ==== ==== time ====
  
Line 732: Line 768:
  
 ==== wizpass ==== ==== wizpass ====
-syntax: wizpass 
  
-notesthis will toggle on and off your ability to walk thru walls as dm.+Usagewizpass 
 + 
 +This will toggle on and off your ability to walk through ​walls as DM.
  
    
dm_commands.1664126579.txt.gz · Last modified: 2022/09/25 12:22 by leaf