evennia/game/docs/help_files.json

2 lines
518 KiB
JSON
Raw Normal View History

[{"pk": 2, "model": "helpsys.helpentry", "fields": {"entrytext": "\"\n\n COMMAND: \"<message>\n\n Says <message> out loud to everyone in your current location (usually a\n room).\n\n Example:\n > \"Where is the movie theater?\n You say, \"Where is the movie theater?\"\n\n Note that the closing double quote is automatically added.\n\n Related Topics: page, pose, say, :, \".\n\n", "topicname": "\"", "staff_only": false}}, {"pk": 3, "model": "helpsys.helpentry", "fields": {"entrytext": "#\n\n COMMAND: #<number> <command>\n\n Forces the object whose database number is <number> to perform <command>.\n Example: '#1033 move north' forces object #1033 to go north (assuming that\n you control it). The same restrictions that apply to @force also apply to\n this command.\n\n Related Topics: @force.\n\n", "topicname": "#", "staff_only": false}}, {"pk": 4, "model": "helpsys.helpentry", "fields": {"entrytext": "$-COMMANDS\n\n These commands are called arbitrary commands, user-defined commands, or\n $-commands (for how they are defined). See 'arbitrary commands' for the\n full description.\n\n Related Topics: arbitrary commands\n\n", "topicname": "$-COMMANDS", "staff_only": false}}, {"pk": 5, "model": "helpsys.helpentry", "fields": {"entrytext": "\n COMMAND: &<attribute> <object>[=<value>]\n SYNONYM: @set <object> = <attribute>:[<value>]\n\n Sets the attribute named <attribute> on <object> to <value>. If\n <attribute> is not a predefined attribute (like ofail or va), then it is\n created. Attributes so created are called user-named attributes.\n Attribute names may only contain letters, numbers, and the characters\n < -_.@#$^&*~?=+| >, and must start with a letter. The names of user-named\n attributes may not be abbreviated (an attempt to get the value of the\n attribute will fail, and an attempt to set will create a new attribute).\n The & command may be used to set predefined attributes (in this instance,\n '&<attr> <object>=<value>' is equivalent to '@<attr> <object>=<value>').\n\n Related Topics: @set.\n\n", "topicname": "&", "staff_only": false}}, {"pk": 6, "model": "helpsys.helpentry", "fields": {"entrytext": ":\n\n COMMAND: :<message>\n\n Displays <message> to everyone in your current room, preceded by your name\n and a space. However, if <message> starts with a space, no space is\n inserted between your name and the pose -- like the ';' command.\n\n Example:\n >:jumps for joy.\n Player jumps for joy.\n >: 's cat meows.\n Player's cat meows.\n\n Related Topics: page, pose, say, whisper, ;, \".\n\n", "topicname": ":", "staff_only": false}}, {"pk": 7, "model": "helpsys.helpentry", "fields": {"entrytext": ";\n\n COMMAND: ;<message>\n\n This command is much like the ':' command, except that no space is inserted\n between your name and the pose. However, <message> can start with its own\n space -- a result similar to using the ':' command.\n\n Example:\n > ;'s watch beeps.\n Player's watch beeps.\n > ; meows.\n Player meows.\n\n Warning: This command does not work in command lists run from an attribute\n because the ';' is treated as the command separator. Use pose/nospace\n instead.\n\n Related Topics: page, pose, say, whisper, :, \".\n\n", "topicname": ";", "staff_only": false}}, {"pk": 8, "model": "helpsys.helpentry", "fields": {"entrytext": "@@\n\n COMMAND: @@ <args>\n\n This command and everything after it (excluding the command-separator\n ';') is not evaluated by the parser. This is useful for adding comments\n in softcode or, more commonly, writing comment headers for softcode\n installers (such as /quotable text files). Note that @@ must be\n followed by a space or it will return an error message.\n\n Always be doubly sure that ()'s and {}'s in the (otherwise ignored)\n arguments are nested correctly, so that any semicolons used to separate it\n from subsequent code in the line are recognized by the parser.\n\n Example:\n > @va me=$foobar *:@fo #1234=%0;@@ This controls my foobar puppet.\n > foobar say Hello World!\n foob