Modding:being (0.9.9.7) - Revision history

Yaflhdztioxo: Replaced content with "Within the context of modding a 'being' can refer to: * The being blueprint, a structure used to define beings * The [[Modding:being_AP..."

2013-04-20T23:02:33Z

Replaced content with "Within the context of modding a 'being' can refer to: * The being blueprint, a structure used to define beings * The [[Modding:being_AP..."

Show changes

Yaflhdztioxo: moved Modding:Being to Modding:being (0.9.9.7)

2013-04-20T22:52:44Z

moved Modding:Being to Modding:being (0.9.9.7)

Game Hunter: quick format fix

2012-01-31T21:06:31Z

quick format fix

Game Hunter: also it's IF_BLADE not IF_BLADED

2012-01-31T21:04:25Z

also it's IF_BLADE not IF_BLADED

Game Hunter: BF_MODEXPERT now correct!

2012-01-31T21:03:35Z

BF_MODEXPERT now correct!

Game Hunter: added and updated being flags

2012-01-31T20:57:26Z

added and updated being flags

Game Hunter: whoops wrong table title

2011-10-24T23:38:27Z

whoops wrong table title

Game Hunter: more table stuff

2011-10-19T20:09:59Z

more table stuff

Show changes

Tehtmi: more detail about path_find

2011-08-15T21:56:31Z

more detail about path_find

Tehtmi: Added some missing stuff

2011-08-15T21:36:49Z

Added some missing stuff

@@ Line 109: / Line 109: @@
    |BF_NOEXP|Beings with this flag will not award experience to the player.
    |BF_BOSS|Killing this monster will cause the same message as killing the final boss as well as its death explosion and ending the game.
-   |BF_JC||When used with BF_BOSS, changes the explosion to blue and changes the message to indicate that JC was killed instead of the cyberdemon.
+   |BF_JC|When used with BF_BOSS, changes the explosion to blue and changes the message to indicate that JC was killed instead of the cyberdemon.
    |}}
 }}

@@ Line 83: / Line 83: @@
    |BF_SHOTTYHEAD|Gives the benefits of the [[Traits#Shottyhead|Shottyhead]] trait.
    |BF_NORUNPENALTY|Gives the benefits of the [[Traits#Running Man|Running Man]] trait.
-   |BF_DUALBLADE|If both weapons in the being's equipment slots have IF_BLADED, this flag allows both weapons to attack in the same turn, each at half the attack time (part of the [[Traits#Malicious Blades|Malicious Blades]] trait).
+   |BF_DUALBLADE|If both weapons in the being's equipment slots have IF_BLADE, this flag allows both weapons to attack in the same turn, each at half the attack time (part of the [[Traits#Malicious Blades|Malicious Blades]] trait).
-   |BF_BLADEDEFEND|If the weapon in the being's prepared slot has IF_BLADED, this flag grants the being with resistances as [[Traits#Malicious Blades|Malicious Blades]].
+   |BF_BLADEDEFEND|If the weapon in the being's prepared slot has IF_BLADE, this flag grants the being with resistances as [[Traits#Malicious Blades|Malicious Blades]].
    |BF_PISTOLMAX|Gives the benefits of the [[Sharpshooter]] trait.
    |BF_FIREANGEL|Gives the benefits of the [[Traits#Fireangel|Fireangel]] trait.

@@ Line 63: / Line 63: @@
    |BF_INSTAUSE|Allows consumable items to be used in 0.1s instead of the usual 1.0s, as the [[Technician]] class bonus.
    |BF_MAPEXPERT|Makes computer maps work like tracking maps, as the [[Technician]] class bonus.
    |BF_QUICKSWAP|Gives the benefits of the Juggler trait.
    |BF_BERSERKER|Gives the benefits of the [[Traits#Berserker|Berserker]] trait.
@@ Line 98: / Line 99: @@
    |BF_KNOCKIMMUNE|Makes the being immune to [[knockback]].
    |BF_UNIQUENAME|This flag makes the game treat the being's name as a proper noun.
    |BF_ENTERBOSS1|This is a flag for the player that helps determine which victory message to use in the mortem.
    |BF_KILLBOSS1|This is a flag for the player that helps determine which victory message to use in the mortem.

@@ Line 49: / Line 49: @@
    |}}
 |}
+=== Flags ===
 == Engine Hooks ==
 Specifying one or more of these hooks in the prototype will allow for greater customization.

@@ Line 5: / Line 5: @@
 New beings are created from being prototypes. Think of a being prototype as a recipe for creating new beings. There can be multiple former humans, but they all came from the same prototype. Prototypes are declared by passing a table with the desired properties to the Beings function. [[#Engine Hooks|Engine hooks]] may also be included in the prototype. Mostly, the prototype's properties just describe beings' initial properties (occasionally with different names). Beings' properties can also mostly be changed after they are instantiated. Required fields are underlined. Sometimes required fields can safely be omitted, but this will generate a message in the log file. All being prototypes are stored in a global table called beings. This table can be indexed by id or nid.
 {|class="wikitable" style="border: 2px solid darkred; border-spacing: 0; font-size: 90%; margin: 0.25em 0.5em;"
-  ! colspan="3" style="background: darkred; color: yellow; font-size: 120%; text-align: center"|'''Thing Properties'''
+  ! colspan="3" style="background: darkred; color: yellow; font-size: 120%; text-align: center"|'''Being Prototype'''
   {{Table3Col
    |es=background: #333;
@@ Line 81: / Line 81: @@
 {|class="wikitable" style="border: 2px solid darkred; border-spacing: 0; font-size: 90%; margin: 0.25em 0.5em;"
-  ! colspan="3" style="background: darkred; color: yellow; font-size: 120%; text-align: center"|Thing
+  ! colspan="3" style="background: darkred; color: yellow; font-size: 120%; text-align: center"|Being
   {{Table3Col
    |es=background: #333;

@@ Line 472: / Line 472: @@
 {{Anchor|being_path_find}}
 ;[[Modding:Being|Being]]&#058;path_find([[Modding:Coord|Coord]] target, '''integer''' cutoff, '''integer''' maximum) &rarr; '''boolean'''
-:This attempts to calculate a path between the being and ''target''. The ''cutoff'' and ''maximum'' parameters are somewhat technical, but basically they indicate how much time should be spend searching for a path. DoomRL uses 40, 200 for bosses and 10, 40 for normal enemies. The path will be remembered by the being, and can be followed using path_next. Modders should keep in mind that path-finding is a somewhat expensive operation, especially for large ''cutoff'' and ''maximum''. The return value indicates whether a path was found.
+:This attempts to calculate a path between the being and ''target''. The ''cutoff'' and ''maximum'' parameters are somewhat technical, but basically they indicate how much time should be spend searching for a path. DoomRL uses 40, 200 for bosses and 10, 40 for normal enemies. The path will be remembered by the being, and can be followed using path_next. Modders should keep in mind that path-finding is a somewhat expensive operation, especially for large ''cutoff'' and ''maximum''. The return value indicates whether a path was found. Even if no path was found, a path will be loaded that will try to take the being closer to the target (although this path may be empty). This uses the AStar searching algorithm using Euclidean distance as a heuristic. The search is aborted if ''maximum'' nodes are expanded without finding the target or it ''cutoff'' nodes are expanded without getting closer to the target. When aborted, a path is created to the closest expanded node to the target in terms of the heuristic.
 ----
 {{Anchor|being_path_next}}

@@ Line 1: / Line 1: @@
 If it bleeds, it leads. Beings inherit from the [[Modding:Thing|Thing]] base class which handles some basic properties in common with items. In addition the [[Modding:Player|Player]] inherits this class, so anything you can do to creatures can be done to the player as well.
 == Prototype ==
-New beings are created from being prototypes. Think of a being prototype as a recipe for creating new beings. There can be multiple former humans, but they all came from the same prototype. Prototypes are declared by passing a table with the desired properties to the Beings function. [[#Engine Hooks|Engine hooks]] may also be included in the prototype. Mostly, the prototype's properties just describe beings' initial properties (occasionally with different names). Beings' properties can also mostly be changed after they are instantiated. Required fields are underlined. Sometimes required fields can safely be omitted, but this will generate a message in the log file.
+New beings are created from being prototypes. Think of a being prototype as a recipe for creating new beings. There can be multiple former humans, but they all came from the same prototype. Prototypes are declared by passing a table with the desired properties to the Beings function. [[#Engine Hooks|Engine hooks]] may also be included in the prototype. Mostly, the prototype's properties just describe beings' initial properties (occasionally with different names). Beings' properties can also mostly be changed after they are instantiated. Required fields are underlined. Sometimes required fields can safely be omitted, but this will generate a message in the log file. All being prototypes are stored in a global table called beings. This table can be indexed by id or nid.
 {|style="border: 2px solid darkred; border-spacing: 0; font-size: 90%; margin: 0.25em 0.5em;"
 |colspan=3 style="background: darkred; color: yellow; font-size: 120%; text-align: center"|'''Being Prototype'''
@@ Line 23: / Line 21: @@
 |style="text-align: right; vertical-align:top; padding-right: 2ex;"|'''string'''
 |style="vertical-align:top; padding-right: 2ex;"|id
-|This is the being's sid. It must be distinct from other string ids. (The numeric id is automatically assigned.) Only the first 20 characters will be used. The default is the first word of the name in all lowercase.
+|This is the being's sid. It must be distinct from other string ids. (The numeric id is automatically assigned to a field called nid.) Only the first 20 characters will be used. The default is the first word of the name in all lowercase.
 |-
 |style="text-align: right; vertical-align:top; padding-right: 2ex;"|'''integer''' '''list'''
@@ Line 285: / Line 283: @@
 |style="vertical-align:top; padding-right: 2ex;"|soundhoof
 |This is the being's .hoof sound.
 |}
 == API ==