https://wiki.thedarkmod.com/api.php?action=feedcontributions&feedformat=atom&user=145.253.32.51 2026-04-18T11:05:33Z User contributions MediaWiki 1.45.3 https://wiki.thedarkmod.com/index.php?title=Inventory&diff=2240 2007-02-12T14:40:21Z

<p>145.253.32.51: /* Definitions */</p> <hr /> <div>= Overview =<br /> This article describes how to set up inventory items and how they can be given to an entity. The purpose of the inventory is, to keep track of all items that are in an entities possessions. I delibaretly use &quot;entity&quot; here because, in principle, all entities can have an inventory, even though it may only make sense for AI and the player to actuall have one. For future improvements it might be usefull for other purposes as well though.<br /> Also included is a script interface, so that a mapper can interact with the inventory in a more sophisticated way, if the default implementation is not sufficient.<br /> <br /> == Definitions ==<br /> <br /> The spawnargs can be either set in the def file as a default, or in the map file to override settings for specific entities. Naturaly this also means that they can be manipulated by scripts as well, since they are the standard way of configuring objects in Doom 3.<br /> <br /> '''IMPORTANT!!!''' Normally items will vanish from the map as soon as the item is successfully put into the inventory. If this doesn't work, then the item will stay visible. This is a intentionally so, to make the mapper aware of the problem. Currently there is only one error condition that can really trigger this, which is that an item is configured to not be anonymous, but has an empty inv_icon entry. Additionally to not becoming invisible, you can also look into the logfile, because there you can find an errr message with the name of the entity that was causing the problem.<br /> <br /> There are several terms and types of items that can be used in the inventory:<br /> <br /> * '''anonymous items''' An anonymous object means that it will not show up as a seperate item in the inventory. An example would be normal loot like coins or golden dishes. Since they should not be stored in the inventory as seperate items, they don't need to be displayed either. In this case they only count for the total of loot and are discarded afterwards. Anonymous items also can not be dropped after they went into the inventory because they essentially no longer exist. For the loot count it obviously doesn't matter wether an item is anonymous or not, as all are added up into the loot categories. Examples are gold coins and all the other (mostly loot) items that are collected but not being used individually. <br /> <br /> * '''stackable items''' These are items that can be stacked in the inventory. This means that the player can acquire multiple instances of such items, but only one entry is shown in the inventory with a counter of how many currently are available. An example would be a health potion. The player can posses more than one health potion at a time and this would be indicated by the counter. Stackable items are identified by setting the stackable property. They also must always use the same name and category. If this doesn't match, they are considered to be of different types. This also allows for dealing out i.e. fake health potions which have no effect or deal damage instead (as an example).<br /> <br /> * '''Category''' is a classification of items, to visually group them together. This allows the player to faster scroll through the inventory because he doesn't have to cycle through all the individual items. For example a category would be 'Readables' where books and scrolls are stored, and another Category would be 'Tools' where lockpicks and other items can be stored. Note that this category is entirely up to the mapper to decide and also is option. it doesn't has any consequence as to the playabillity and is only a convenience for the player. Categories can switched of on the HUD, so that the player can use the inventory also in the Thief style (which is the default).<br /> <br /> == Spawnargs ==<br /> <br /> inv_category : string<br /> Specifies the cagtegory that the object should be filed under. This <br /> allows for player convenience and also is needed for stackable items.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_name : string<br /> Specifies the name the object should display when it is activated in the inventory.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_icon : D3 path to icon<br /> Points to an icon that is to be displayed when the object is selected in the inventory.<br /> This entry also determines wether an object is to be considered anonymous or not. <br /> <br /> inv_stackable : [0/1]<br /> Determines wether an item is an individual or can be a stack of similar objects. An<br /> Example would be the various potions. The player can pick up more than one health <br /> potion, but in the inventory he will only get one item with a counter. Keep in mind<br /> though that a stack of gold coins is not per se stackable, because usually it will be<br /> only one model of a stack of coin with a value of i.E. 10 Gold, so this means that it<br /> is not to be confused with a a single gold coin having 10 items with a value of 1 each.<br /> <br /> inv_count : &lt;N&gt;<br /> Determines the number of items this represents. This is only needed for items where<br /> stackable is 1, otherwise it is set to 0. Als the option for stackable must always <br /> precede the count, otherwise the count is set to 0.<br /> <br /> inv_droppable : [0/1]<br /> If set to 1 the item can be dropped into the map by the player. This will not<br /> work for anonymous items, since they will have no representation after they<br /> were put into the inventory.<br /> <br /> inv_delete : [0/1]<br /> Determines if an anonymous object can be deleted, after it was put into the inventory.<br /> This is advisable, because the entity will stay in memory and a mapper could still<br /> access it via scripting. If the mapper decides that an item will no longer be accessed<br /> after it has been acquired, this key should be set to 1. This can affect loading time<br /> of saved games, as entities, that are no longer needed, don't need to be saved and<br /> restored.<br /> If the mapper also creates entities on the fly, with the help of scripts, it might<br /> better to set this flag on appropriate objects to free up the limited number of<br /> entities a map can hold. The usuals candidates for this flag are all the regular loot<br /> items, because they wont be used anymore after they have been found (lik coins, purses,<br /> etc.). Also note that, if dropappable is set to 1, then this key will be ignored, since<br /> droppabale items must be turned into entities again to be placed in the map.<br /> <br /> inv_loot_type : [ 0 | 1 | 2 | 3 ]<br /> * 0 = No lootitem (default)<br /> * 1 = Jewelry/Gems<br /> * 2 = Gold<br /> * 3 = Goods<br /> This has to be set in order to define what kind of item it is and if it is a loot item,<br /> which category of loot it should account for.<br /> <br /> inv_loot_value : &lt;N&gt;<br /> Determines the amount of loot this item accounts for. This value is ignore if it is<br /> set on an item, which is of loot_type = 0.<br /> <br /> inv_map_start : [0|1]<br /> Determines wether this object should be assigned to an inventory at map start.<br /> <br /> inv_target : &lt;entityname&gt;<br /> If the item should be assigned to an entity at map start, this should get the name<br /> of the entity who shold recive it. To give an item to the player, you would use<br /> &quot;player1&quot; as the name, because this is the name that the player entity gets by<br /> default. If inv_map_start is not set or set to 0, then this key doesn't need to be<br /> set and is ignored. Since the name can be arbitrary, this means of course, that you<br /> can also give it to an AI, which the player later on meets. This should not be confused<br /> with loot, that is to be attached to an AI though. If you attach a purse or a key to<br /> an AI, which the player can frob later on, then it doesn't need to get this set, because<br /> such things will not be stored in the inventory. You could assign such things to an<br /> chest though, to give the objects to the player when he opens it. This is not directly<br /> support though, because it is assumed that chests will be filled with real objects, like<br /> TDS did it. However the T1/T2 style chests are still possible to do with some scripting.<br /> <br /> == Default equipment for map start ==<br /> <br /> This describes how to give items to the player at the mapstart, but the same mechanism can be applied to any other AI (or entity for that matter) as well.<br /> <br /> * First create your object in the editor, just like you would if you wanted to put it in the map. Create brush, select the item and/or models and place it anywhere you like in the map<br /> <br /> * Set the key inv_map_start on the object entity to the value 1.<br /> <br /> * Set the key inv_target on the object entity to the value player1. If you want to assign this object to, as an example, a guard with the name Benny, then set it to benny, assuming the entity key &quot;name&quot; is also set to &quot;benny&quot;.<br /> <br /> The objects can really be placed anyhwere you like and it doesn't really matter. As soon as the map starts, the objects will be put in the inventory, and will vanish from the map. So you could put them right in front of the players eyes, and he still wouldn't see them, as this happens at the intialization time, before the map actually becomes visible.<br /> <br /> That's it. Quite simple I would say. :)<br /> <br /> [[Category:Editing]]<br /> [[Category:Tutorial]]</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Inventory&diff=2239 2007-02-12T14:39:58Z

<p>145.253.32.51: /* Definitions */</p> <hr /> <div>= Overview =<br /> This article describes how to set up inventory items and how they can be given to an entity. The purpose of the inventory is, to keep track of all items that are in an entities possessions. I delibaretly use &quot;entity&quot; here because, in principle, all entities can have an inventory, even though it may only make sense for AI and the player to actuall have one. For future improvements it might be usefull for other purposes as well though.<br /> Also included is a script interface, so that a mapper can interact with the inventory in a more sophisticated way, if the default implementation is not sufficient.<br /> <br /> == Definitions ==<br /> <br /> The spawnargs can be either set in the def file as a default, or in the map file to override settings for specific entities. Naturaly this also means that they can be manipulated by scripts as well, since they are the standard way of configuring objects in Doom 3.<br /> <br /> '''IMPORTANT!!!''' Normally items will vanish from the map as soon as the item is successfully put into the inventory. If this doesn't work, then the item will stay visible. This is a intentionally so, to make the mapper aware of the problem. Currently there is only one error condition that can really trigger this, which is that an item is configured to not be anonymous, but has an empty inv_icon entry. Additionally to not becoming invisible, you can also look into the logfile, because there you can find the name of the entity that was causing the problem.<br /> <br /> There are several terms and types of items that can be used in the inventory:<br /> <br /> * '''anonymous items''' An anonymous object means that it will not show up as a seperate item in the inventory. An example would be normal loot like coins or golden dishes. Since they should not be stored in the inventory as seperate items, they don't need to be displayed either. In this case they only count for the total of loot and are discarded afterwards. Anonymous items also can not be dropped after they went into the inventory because they essentially no longer exist. For the loot count it obviously doesn't matter wether an item is anonymous or not, as all are added up into the loot categories. Examples are gold coins and all the other (mostly loot) items that are collected but not being used individually. <br /> <br /> * '''stackable items''' These are items that can be stacked in the inventory. This means that the player can acquire multiple instances of such items, but only one entry is shown in the inventory with a counter of how many currently are available. An example would be a health potion. The player can posses more than one health potion at a time and this would be indicated by the counter. Stackable items are identified by setting the stackable property. They also must always use the same name and category. If this doesn't match, they are considered to be of different types. This also allows for dealing out i.e. fake health potions which have no effect or deal damage instead (as an example).<br /> <br /> * '''Category''' is a classification of items, to visually group them together. This allows the player to faster scroll through the inventory because he doesn't have to cycle through all the individual items. For example a category would be 'Readables' where books and scrolls are stored, and another Category would be 'Tools' where lockpicks and other items can be stored. Note that this category is entirely up to the mapper to decide and also is option. it doesn't has any consequence as to the playabillity and is only a convenience for the player. Categories can switched of on the HUD, so that the player can use the inventory also in the Thief style (which is the default).<br /> <br /> == Spawnargs ==<br /> <br /> inv_category : string<br /> Specifies the cagtegory that the object should be filed under. This <br /> allows for player convenience and also is needed for stackable items.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_name : string<br /> Specifies the name the object should display when it is activated in the inventory.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_icon : D3 path to icon<br /> Points to an icon that is to be displayed when the object is selected in the inventory.<br /> This entry also determines wether an object is to be considered anonymous or not. <br /> <br /> inv_stackable : [0/1]<br /> Determines wether an item is an individual or can be a stack of similar objects. An<br /> Example would be the various potions. The player can pick up more than one health <br /> potion, but in the inventory he will only get one item with a counter. Keep in mind<br /> though that a stack of gold coins is not per se stackable, because usually it will be<br /> only one model of a stack of coin with a value of i.E. 10 Gold, so this means that it<br /> is not to be confused with a a single gold coin having 10 items with a value of 1 each.<br /> <br /> inv_count : &lt;N&gt;<br /> Determines the number of items this represents. This is only needed for items where<br /> stackable is 1, otherwise it is set to 0. Als the option for stackable must always <br /> precede the count, otherwise the count is set to 0.<br /> <br /> inv_droppable : [0/1]<br /> If set to 1 the item can be dropped into the map by the player. This will not<br /> work for anonymous items, since they will have no representation after they<br /> were put into the inventory.<br /> <br /> inv_delete : [0/1]<br /> Determines if an anonymous object can be deleted, after it was put into the inventory.<br /> This is advisable, because the entity will stay in memory and a mapper could still<br /> access it via scripting. If the mapper decides that an item will no longer be accessed<br /> after it has been acquired, this key should be set to 1. This can affect loading time<br /> of saved games, as entities, that are no longer needed, don't need to be saved and<br /> restored.<br /> If the mapper also creates entities on the fly, with the help of scripts, it might<br /> better to set this flag on appropriate objects to free up the limited number of<br /> entities a map can hold. The usuals candidates for this flag are all the regular loot<br /> items, because they wont be used anymore after they have been found (lik coins, purses,<br /> etc.). Also note that, if dropappable is set to 1, then this key will be ignored, since<br /> droppabale items must be turned into entities again to be placed in the map.<br /> <br /> inv_loot_type : [ 0 | 1 | 2 | 3 ]<br /> * 0 = No lootitem (default)<br /> * 1 = Jewelry/Gems<br /> * 2 = Gold<br /> * 3 = Goods<br /> This has to be set in order to define what kind of item it is and if it is a loot item,<br /> which category of loot it should account for.<br /> <br /> inv_loot_value : &lt;N&gt;<br /> Determines the amount of loot this item accounts for. This value is ignore if it is<br /> set on an item, which is of loot_type = 0.<br /> <br /> inv_map_start : [0|1]<br /> Determines wether this object should be assigned to an inventory at map start.<br /> <br /> inv_target : &lt;entityname&gt;<br /> If the item should be assigned to an entity at map start, this should get the name<br /> of the entity who shold recive it. To give an item to the player, you would use<br /> &quot;player1&quot; as the name, because this is the name that the player entity gets by<br /> default. If inv_map_start is not set or set to 0, then this key doesn't need to be<br /> set and is ignored. Since the name can be arbitrary, this means of course, that you<br /> can also give it to an AI, which the player later on meets. This should not be confused<br /> with loot, that is to be attached to an AI though. If you attach a purse or a key to<br /> an AI, which the player can frob later on, then it doesn't need to get this set, because<br /> such things will not be stored in the inventory. You could assign such things to an<br /> chest though, to give the objects to the player when he opens it. This is not directly<br /> support though, because it is assumed that chests will be filled with real objects, like<br /> TDS did it. However the T1/T2 style chests are still possible to do with some scripting.<br /> <br /> == Default equipment for map start ==<br /> <br /> This describes how to give items to the player at the mapstart, but the same mechanism can be applied to any other AI (or entity for that matter) as well.<br /> <br /> * First create your object in the editor, just like you would if you wanted to put it in the map. Create brush, select the item and/or models and place it anywhere you like in the map<br /> <br /> * Set the key inv_map_start on the object entity to the value 1.<br /> <br /> * Set the key inv_target on the object entity to the value player1. If you want to assign this object to, as an example, a guard with the name Benny, then set it to benny, assuming the entity key &quot;name&quot; is also set to &quot;benny&quot;.<br /> <br /> The objects can really be placed anyhwere you like and it doesn't really matter. As soon as the map starts, the objects will be put in the inventory, and will vanish from the map. So you could put them right in front of the players eyes, and he still wouldn't see them, as this happens at the intialization time, before the map actually becomes visible.<br /> <br /> That's it. Quite simple I would say. :)<br /> <br /> [[Category:Editing]]<br /> [[Category:Tutorial]]</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Inventory&diff=2238 2007-02-12T14:39:16Z

<p>145.253.32.51: /* Definitions */</p> <hr /> <div>= Overview =<br /> This article describes how to set up inventory items and how they can be given to an entity. The purpose of the inventory is, to keep track of all items that are in an entities possessions. I delibaretly use &quot;entity&quot; here because, in principle, all entities can have an inventory, even though it may only make sense for AI and the player to actuall have one. For future improvements it might be usefull for other purposes as well though.<br /> Also included is a script interface, so that a mapper can interact with the inventory in a more sophisticated way, if the default implementation is not sufficient.<br /> <br /> == Definitions ==<br /> <br /> The spawnargs can be either set in the def file as a default, or in the map file to override settings for specific entities. Naturaly this also means that they can be manipulated by scripts as well, since they are the standard way of configuring objects in Doom 3.<br /> <br /> '''IMPORTANT!!!''' Normally items will vanish from the map as soon as the item is successfully put into the inventory. If this doesn't work, then the item will stay visible. This is a intentionally so, to make the mapper aware of the problem. Currently there is only one error condition that can really trigger this, which is that an item is configured to not be anonymous, but has an empty inv_icon entry.<br /> <br /> There are several terms and types of items that can be used in the inventory:<br /> <br /> * '''anonymous items''' An anonymous object means that it will not show up as a seperate item in the inventory. An example would be normal loot like coins or golden dishes. Since they should not be stored in the inventory as seperate items, they don't need to be displayed either. In this case they only count for the total of loot and are discarded afterwards. Anonymous items also can not be dropped after they went into the inventory because they essentially no longer exist. For the loot count it obviously doesn't matter wether an item is anonymous or not, as all are added up into the loot categories. Examples are gold coins and all the other (mostly loot) items that are collected but not being used individually. <br /> <br /> * '''stackable items''' These are items that can be stacked in the inventory. This means that the player can acquire multiple instances of such items, but only one entry is shown in the inventory with a counter of how many currently are available. An example would be a health potion. The player can posses more than one health potion at a time and this would be indicated by the counter. Stackable items are identified by setting the stackable property. They also must always use the same name and category. If this doesn't match, they are considered to be of different types. This also allows for dealing out i.e. fake health potions which have no effect or deal damage instead (as an example).<br /> <br /> * '''Category''' is a classification of items, to visually group them together. This allows the player to faster scroll through the inventory because he doesn't have to cycle through all the individual items. For example a category would be 'Readables' where books and scrolls are stored, and another Category would be 'Tools' where lockpicks and other items can be stored. Note that this category is entirely up to the mapper to decide and also is option. it doesn't has any consequence as to the playabillity and is only a convenience for the player. Categories can switched of on the HUD, so that the player can use the inventory also in the Thief style (which is the default).<br /> <br /> == Spawnargs ==<br /> <br /> inv_category : string<br /> Specifies the cagtegory that the object should be filed under. This <br /> allows for player convenience and also is needed for stackable items.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_name : string<br /> Specifies the name the object should display when it is activated in the inventory.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_icon : D3 path to icon<br /> Points to an icon that is to be displayed when the object is selected in the inventory.<br /> This entry also determines wether an object is to be considered anonymous or not. <br /> <br /> inv_stackable : [0/1]<br /> Determines wether an item is an individual or can be a stack of similar objects. An<br /> Example would be the various potions. The player can pick up more than one health <br /> potion, but in the inventory he will only get one item with a counter. Keep in mind<br /> though that a stack of gold coins is not per se stackable, because usually it will be<br /> only one model of a stack of coin with a value of i.E. 10 Gold, so this means that it<br /> is not to be confused with a a single gold coin having 10 items with a value of 1 each.<br /> <br /> inv_count : &lt;N&gt;<br /> Determines the number of items this represents. This is only needed for items where<br /> stackable is 1, otherwise it is set to 0. Als the option for stackable must always <br /> precede the count, otherwise the count is set to 0.<br /> <br /> inv_droppable : [0/1]<br /> If set to 1 the item can be dropped into the map by the player. This will not<br /> work for anonymous items, since they will have no representation after they<br /> were put into the inventory.<br /> <br /> inv_delete : [0/1]<br /> Determines if an anonymous object can be deleted, after it was put into the inventory.<br /> This is advisable, because the entity will stay in memory and a mapper could still<br /> access it via scripting. If the mapper decides that an item will no longer be accessed<br /> after it has been acquired, this key should be set to 1. This can affect loading time<br /> of saved games, as entities, that are no longer needed, don't need to be saved and<br /> restored.<br /> If the mapper also creates entities on the fly, with the help of scripts, it might<br /> better to set this flag on appropriate objects to free up the limited number of<br /> entities a map can hold. The usuals candidates for this flag are all the regular loot<br /> items, because they wont be used anymore after they have been found (lik coins, purses,<br /> etc.). Also note that, if dropappable is set to 1, then this key will be ignored, since<br /> droppabale items must be turned into entities again to be placed in the map.<br /> <br /> inv_loot_type : [ 0 | 1 | 2 | 3 ]<br /> * 0 = No lootitem (default)<br /> * 1 = Jewelry/Gems<br /> * 2 = Gold<br /> * 3 = Goods<br /> This has to be set in order to define what kind of item it is and if it is a loot item,<br /> which category of loot it should account for.<br /> <br /> inv_loot_value : &lt;N&gt;<br /> Determines the amount of loot this item accounts for. This value is ignore if it is<br /> set on an item, which is of loot_type = 0.<br /> <br /> inv_map_start : [0|1]<br /> Determines wether this object should be assigned to an inventory at map start.<br /> <br /> inv_target : &lt;entityname&gt;<br /> If the item should be assigned to an entity at map start, this should get the name<br /> of the entity who shold recive it. To give an item to the player, you would use<br /> &quot;player1&quot; as the name, because this is the name that the player entity gets by<br /> default. If inv_map_start is not set or set to 0, then this key doesn't need to be<br /> set and is ignored. Since the name can be arbitrary, this means of course, that you<br /> can also give it to an AI, which the player later on meets. This should not be confused<br /> with loot, that is to be attached to an AI though. If you attach a purse or a key to<br /> an AI, which the player can frob later on, then it doesn't need to get this set, because<br /> such things will not be stored in the inventory. You could assign such things to an<br /> chest though, to give the objects to the player when he opens it. This is not directly<br /> support though, because it is assumed that chests will be filled with real objects, like<br /> TDS did it. However the T1/T2 style chests are still possible to do with some scripting.<br /> <br /> == Default equipment for map start ==<br /> <br /> This describes how to give items to the player at the mapstart, but the same mechanism can be applied to any other AI (or entity for that matter) as well.<br /> <br /> * First create your object in the editor, just like you would if you wanted to put it in the map. Create brush, select the item and/or models and place it anywhere you like in the map<br /> <br /> * Set the key inv_map_start on the object entity to the value 1.<br /> <br /> * Set the key inv_target on the object entity to the value player1. If you want to assign this object to, as an example, a guard with the name Benny, then set it to benny, assuming the entity key &quot;name&quot; is also set to &quot;benny&quot;.<br /> <br /> The objects can really be placed anyhwere you like and it doesn't really matter. As soon as the map starts, the objects will be put in the inventory, and will vanish from the map. So you could put them right in front of the players eyes, and he still wouldn't see them, as this happens at the intialization time, before the map actually becomes visible.<br /> <br /> That's it. Quite simple I would say. :)<br /> <br /> [[Category:Editing]]<br /> [[Category:Tutorial]]</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Inventory&diff=2237 2007-02-12T14:38:57Z

<p>145.253.32.51: /* Definitions */</p> <hr /> <div>= Overview =<br /> This article describes how to set up inventory items and how they can be given to an entity. The purpose of the inventory is, to keep track of all items that are in an entities possessions. I delibaretly use &quot;entity&quot; here because, in principle, all entities can have an inventory, even though it may only make sense for AI and the player to actuall have one. For future improvements it might be usefull for other purposes as well though.<br /> Also included is a script interface, so that a mapper can interact with the inventory in a more sophisticated way, if the default implementation is not sufficient.<br /> <br /> == Definitions ==<br /> <br /> The spawnargs can be either set in the def file as a default, or in the map file to override settings for specific entities. Naturaly this also means that they can be manipulated by scripts as well, since they are the standard way of configuring objects in Doom 3.<br /> <br /> '''IMPORTANT!!!''' Normally items will vanish from the map as soon as the item is successfully put into teh inventory. If this doesn't work, then the item will stay visible. This is a intentionally so, to make the mapper aware of the problem. Currently there is only one error condition that can really trigger this, which is that an item is configured to not be anonymous, but has an empty inv_icon entry.<br /> <br /> There are several terms and types of items that can be used in the inventory:<br /> <br /> * '''anonymous items''' An anonymous object means that it will not show up as a seperate item in the inventory. An example would be normal loot like coins or golden dishes. Since they should not be stored in the inventory as seperate items, they don't need to be displayed either. In this case they only count for the total of loot and are discarded afterwards. Anonymous items also can not be dropped after they went into the inventory because they essentially no longer exist. For the loot count it obviously doesn't matter wether an item is anonymous or not, as all are added up into the loot categories. Examples are gold coins and all the other (mostly loot) items that are collected but not being used individually. <br /> <br /> * '''stackable items''' These are items that can be stacked in the inventory. This means that the player can acquire multiple instances of such items, but only one entry is shown in the inventory with a counter of how many currently are available. An example would be a health potion. The player can posses more than one health potion at a time and this would be indicated by the counter. Stackable items are identified by setting the stackable property. They also must always use the same name and category. If this doesn't match, they are considered to be of different types. This also allows for dealing out i.e. fake health potions which have no effect or deal damage instead (as an example).<br /> <br /> * '''Category''' is a classification of items, to visually group them together. This allows the player to faster scroll through the inventory because he doesn't have to cycle through all the individual items. For example a category would be 'Readables' where books and scrolls are stored, and another Category would be 'Tools' where lockpicks and other items can be stored. Note that this category is entirely up to the mapper to decide and also is option. it doesn't has any consequence as to the playabillity and is only a convenience for the player. Categories can switched of on the HUD, so that the player can use the inventory also in the Thief style (which is the default).<br /> <br /> == Spawnargs ==<br /> <br /> inv_category : string<br /> Specifies the cagtegory that the object should be filed under. This <br /> allows for player convenience and also is needed for stackable items.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_name : string<br /> Specifies the name the object should display when it is activated in the inventory.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_icon : D3 path to icon<br /> Points to an icon that is to be displayed when the object is selected in the inventory.<br /> This entry also determines wether an object is to be considered anonymous or not. <br /> <br /> inv_stackable : [0/1]<br /> Determines wether an item is an individual or can be a stack of similar objects. An<br /> Example would be the various potions. The player can pick up more than one health <br /> potion, but in the inventory he will only get one item with a counter. Keep in mind<br /> though that a stack of gold coins is not per se stackable, because usually it will be<br /> only one model of a stack of coin with a value of i.E. 10 Gold, so this means that it<br /> is not to be confused with a a single gold coin having 10 items with a value of 1 each.<br /> <br /> inv_count : &lt;N&gt;<br /> Determines the number of items this represents. This is only needed for items where<br /> stackable is 1, otherwise it is set to 0. Als the option for stackable must always <br /> precede the count, otherwise the count is set to 0.<br /> <br /> inv_droppable : [0/1]<br /> If set to 1 the item can be dropped into the map by the player. This will not<br /> work for anonymous items, since they will have no representation after they<br /> were put into the inventory.<br /> <br /> inv_delete : [0/1]<br /> Determines if an anonymous object can be deleted, after it was put into the inventory.<br /> This is advisable, because the entity will stay in memory and a mapper could still<br /> access it via scripting. If the mapper decides that an item will no longer be accessed<br /> after it has been acquired, this key should be set to 1. This can affect loading time<br /> of saved games, as entities, that are no longer needed, don't need to be saved and<br /> restored.<br /> If the mapper also creates entities on the fly, with the help of scripts, it might<br /> better to set this flag on appropriate objects to free up the limited number of<br /> entities a map can hold. The usuals candidates for this flag are all the regular loot<br /> items, because they wont be used anymore after they have been found (lik coins, purses,<br /> etc.). Also note that, if dropappable is set to 1, then this key will be ignored, since<br /> droppabale items must be turned into entities again to be placed in the map.<br /> <br /> inv_loot_type : [ 0 | 1 | 2 | 3 ]<br /> * 0 = No lootitem (default)<br /> * 1 = Jewelry/Gems<br /> * 2 = Gold<br /> * 3 = Goods<br /> This has to be set in order to define what kind of item it is and if it is a loot item,<br /> which category of loot it should account for.<br /> <br /> inv_loot_value : &lt;N&gt;<br /> Determines the amount of loot this item accounts for. This value is ignore if it is<br /> set on an item, which is of loot_type = 0.<br /> <br /> inv_map_start : [0|1]<br /> Determines wether this object should be assigned to an inventory at map start.<br /> <br /> inv_target : &lt;entityname&gt;<br /> If the item should be assigned to an entity at map start, this should get the name<br /> of the entity who shold recive it. To give an item to the player, you would use<br /> &quot;player1&quot; as the name, because this is the name that the player entity gets by<br /> default. If inv_map_start is not set or set to 0, then this key doesn't need to be<br /> set and is ignored. Since the name can be arbitrary, this means of course, that you<br /> can also give it to an AI, which the player later on meets. This should not be confused<br /> with loot, that is to be attached to an AI though. If you attach a purse or a key to<br /> an AI, which the player can frob later on, then it doesn't need to get this set, because<br /> such things will not be stored in the inventory. You could assign such things to an<br /> chest though, to give the objects to the player when he opens it. This is not directly<br /> support though, because it is assumed that chests will be filled with real objects, like<br /> TDS did it. However the T1/T2 style chests are still possible to do with some scripting.<br /> <br /> == Default equipment for map start ==<br /> <br /> This describes how to give items to the player at the mapstart, but the same mechanism can be applied to any other AI (or entity for that matter) as well.<br /> <br /> * First create your object in the editor, just like you would if you wanted to put it in the map. Create brush, select the item and/or models and place it anywhere you like in the map<br /> <br /> * Set the key inv_map_start on the object entity to the value 1.<br /> <br /> * Set the key inv_target on the object entity to the value player1. If you want to assign this object to, as an example, a guard with the name Benny, then set it to benny, assuming the entity key &quot;name&quot; is also set to &quot;benny&quot;.<br /> <br /> The objects can really be placed anyhwere you like and it doesn't really matter. As soon as the map starts, the objects will be put in the inventory, and will vanish from the map. So you could put them right in front of the players eyes, and he still wouldn't see them, as this happens at the intialization time, before the map actually becomes visible.<br /> <br /> That's it. Quite simple I would say. :)<br /> <br /> [[Category:Editing]]<br /> [[Category:Tutorial]]</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Inventory&diff=2236 2007-02-12T14:38:37Z

<p>145.253.32.51: /* Overview */</p> <hr /> <div>= Overview =<br /> This article describes how to set up inventory items and how they can be given to an entity. The purpose of the inventory is, to keep track of all items that are in an entities possessions. I delibaretly use &quot;entity&quot; here because, in principle, all entities can have an inventory, even though it may only make sense for AI and the player to actuall have one. For future improvements it might be usefull for other purposes as well though.<br /> Also included is a script interface, so that a mapper can interact with the inventory in a more sophisticated way, if the default implementation is not sufficient.<br /> <br /> == Definitions ==<br /> <br /> The spawnargs can be either set in the def file as a default, or in the map file to override settings for specific entities. Naturaly this also means that they can be manipulated by scripts as well, since they are the standard way of configuring objects in Doom 3.<br /> <br /> Normally items will vanish from the map as soon as the item is successfully put into teh inventory. If this doesn't work, then the item will stay visible. This is a intentionally so, to make the mapper aware of the problem. Currently there is only one error condition that can really trigger this, which is that an item is configured to not be anonymous, but has an empty inv_icon entry.<br /> <br /> There are several terms and types of items that can be used in the inventory:<br /> <br /> * '''anonymous items''' An anonymous object means that it will not show up as a seperate item in the inventory. An example would be normal loot like coins or golden dishes. Since they should not be stored in the inventory as seperate items, they don't need to be displayed either. In this case they only count for the total of loot and are discarded afterwards. Anonymous items also can not be dropped after they went into the inventory because they essentially no longer exist. For the loot count it obviously doesn't matter wether an item is anonymous or not, as all are added up into the loot categories. Examples are gold coins and all the other (mostly loot) items that are collected but not being used individually. <br /> <br /> * '''stackable items''' These are items that can be stacked in the inventory. This means that the player can acquire multiple instances of such items, but only one entry is shown in the inventory with a counter of how many currently are available. An example would be a health potion. The player can posses more than one health potion at a time and this would be indicated by the counter. Stackable items are identified by setting the stackable property. They also must always use the same name and category. If this doesn't match, they are considered to be of different types. This also allows for dealing out i.e. fake health potions which have no effect or deal damage instead (as an example).<br /> <br /> * '''Category''' is a classification of items, to visually group them together. This allows the player to faster scroll through the inventory because he doesn't have to cycle through all the individual items. For example a category would be 'Readables' where books and scrolls are stored, and another Category would be 'Tools' where lockpicks and other items can be stored. Note that this category is entirely up to the mapper to decide and also is option. it doesn't has any consequence as to the playabillity and is only a convenience for the player. Categories can switched of on the HUD, so that the player can use the inventory also in the Thief style (which is the default).<br /> <br /> == Spawnargs ==<br /> <br /> inv_category : string<br /> Specifies the cagtegory that the object should be filed under. This <br /> allows for player convenience and also is needed for stackable items.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_name : string<br /> Specifies the name the object should display when it is activated in the inventory.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_icon : D3 path to icon<br /> Points to an icon that is to be displayed when the object is selected in the inventory.<br /> This entry also determines wether an object is to be considered anonymous or not. <br /> <br /> inv_stackable : [0/1]<br /> Determines wether an item is an individual or can be a stack of similar objects. An<br /> Example would be the various potions. The player can pick up more than one health <br /> potion, but in the inventory he will only get one item with a counter. Keep in mind<br /> though that a stack of gold coins is not per se stackable, because usually it will be<br /> only one model of a stack of coin with a value of i.E. 10 Gold, so this means that it<br /> is not to be confused with a a single gold coin having 10 items with a value of 1 each.<br /> <br /> inv_count : &lt;N&gt;<br /> Determines the number of items this represents. This is only needed for items where<br /> stackable is 1, otherwise it is set to 0. Als the option for stackable must always <br /> precede the count, otherwise the count is set to 0.<br /> <br /> inv_droppable : [0/1]<br /> If set to 1 the item can be dropped into the map by the player. This will not<br /> work for anonymous items, since they will have no representation after they<br /> were put into the inventory.<br /> <br /> inv_delete : [0/1]<br /> Determines if an anonymous object can be deleted, after it was put into the inventory.<br /> This is advisable, because the entity will stay in memory and a mapper could still<br /> access it via scripting. If the mapper decides that an item will no longer be accessed<br /> after it has been acquired, this key should be set to 1. This can affect loading time<br /> of saved games, as entities, that are no longer needed, don't need to be saved and<br /> restored.<br /> If the mapper also creates entities on the fly, with the help of scripts, it might<br /> better to set this flag on appropriate objects to free up the limited number of<br /> entities a map can hold. The usuals candidates for this flag are all the regular loot<br /> items, because they wont be used anymore after they have been found (lik coins, purses,<br /> etc.). Also note that, if dropappable is set to 1, then this key will be ignored, since<br /> droppabale items must be turned into entities again to be placed in the map.<br /> <br /> inv_loot_type : [ 0 | 1 | 2 | 3 ]<br /> * 0 = No lootitem (default)<br /> * 1 = Jewelry/Gems<br /> * 2 = Gold<br /> * 3 = Goods<br /> This has to be set in order to define what kind of item it is and if it is a loot item,<br /> which category of loot it should account for.<br /> <br /> inv_loot_value : &lt;N&gt;<br /> Determines the amount of loot this item accounts for. This value is ignore if it is<br /> set on an item, which is of loot_type = 0.<br /> <br /> inv_map_start : [0|1]<br /> Determines wether this object should be assigned to an inventory at map start.<br /> <br /> inv_target : &lt;entityname&gt;<br /> If the item should be assigned to an entity at map start, this should get the name<br /> of the entity who shold recive it. To give an item to the player, you would use<br /> &quot;player1&quot; as the name, because this is the name that the player entity gets by<br /> default. If inv_map_start is not set or set to 0, then this key doesn't need to be<br /> set and is ignored. Since the name can be arbitrary, this means of course, that you<br /> can also give it to an AI, which the player later on meets. This should not be confused<br /> with loot, that is to be attached to an AI though. If you attach a purse or a key to<br /> an AI, which the player can frob later on, then it doesn't need to get this set, because<br /> such things will not be stored in the inventory. You could assign such things to an<br /> chest though, to give the objects to the player when he opens it. This is not directly<br /> support though, because it is assumed that chests will be filled with real objects, like<br /> TDS did it. However the T1/T2 style chests are still possible to do with some scripting.<br /> <br /> == Default equipment for map start ==<br /> <br /> This describes how to give items to the player at the mapstart, but the same mechanism can be applied to any other AI (or entity for that matter) as well.<br /> <br /> * First create your object in the editor, just like you would if you wanted to put it in the map. Create brush, select the item and/or models and place it anywhere you like in the map<br /> <br /> * Set the key inv_map_start on the object entity to the value 1.<br /> <br /> * Set the key inv_target on the object entity to the value player1. If you want to assign this object to, as an example, a guard with the name Benny, then set it to benny, assuming the entity key &quot;name&quot; is also set to &quot;benny&quot;.<br /> <br /> The objects can really be placed anyhwere you like and it doesn't really matter. As soon as the map starts, the objects will be put in the inventory, and will vanish from the map. So you could put them right in front of the players eyes, and he still wouldn't see them, as this happens at the intialization time, before the map actually becomes visible.<br /> <br /> That's it. Quite simple I would say. :)<br /> <br /> [[Category:Editing]]<br /> [[Category:Tutorial]]</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Inventory&diff=2235 2007-02-12T14:35:48Z

<p>145.253.32.51: /* Spawnargs */</p> <hr /> <div>= Overview =<br /> This article describes how to set up inventory items and how they can be given to an entity. The purpose of the inventory is, to keep track of all items that are in an entities possessions. I delibaretly use &quot;entity&quot; here because, in principle, all entities can have an inventory, even though it may only make sense for AI and the player to actuall have one. For future improvements it might be usefull for other purposes as well though.<br /> Also included is a script interface, so that a mapper can interact with the inventory in a more sophisticated way, if the default implementation is not sufficient.<br /> <br /> == Definitions ==<br /> <br /> The spawnargs can be either set in the def file as a default, or in the map file to override settings for specific entities. Naturaly this also means that they can be manipulated by scripts as well, since they are the standard way of configuring objects in Doom 3.<br /> <br /> There are several terms and types of items that can be used in the inventory:<br /> <br /> * '''anonymous items''' An anonymous object means that it will not show up as a seperate item in the inventory. An example would be normal loot like coins or golden dishes. Since they should not be stored in the inventory as seperate items, they don't need to be displayed either. In this case they only count for the total of loot and are discarded afterwards. Anonymous items also can not be dropped after they went into the inventory because they essentially no longer exist. For the loot count it obviously doesn't matter wether an item is anonymous or not, as all are added up into the loot categories. Examples are gold coins and all the other (mostly loot) items that are collected but not being used individually. <br /> <br /> * '''stackable items''' These are items that can be stacked in the inventory. This means that the player can acquire multiple instances of such items, but only one entry is shown in the inventory with a counter of how many currently are available. An example would be a health potion. The player can posses more than one health potion at a time and this would be indicated by the counter. Stackable items are identified by setting the stackable property. They also must always use the same name and category. If this doesn't match, they are considered to be of different types. This also allows for dealing out i.e. fake health potions which have no effect or deal damage instead (as an example).<br /> <br /> * '''Category''' is a classification of items, to visually group them together. This allows the player to faster scroll through the inventory because he doesn't have to cycle through all the individual items. For example a category would be 'Readables' where books and scrolls are stored, and another Category would be 'Tools' where lockpicks and other items can be stored. Note that this category is entirely up to the mapper to decide and also is option. it doesn't has any consequence as to the playabillity and is only a convenience for the player. Categories can switched of on the HUD, so that the player can use the inventory also in the Thief style (which is the default).<br /> <br /> == Spawnargs ==<br /> <br /> inv_category : string<br /> Specifies the cagtegory that the object should be filed under. This <br /> allows for player convenience and also is needed for stackable items.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_name : string<br /> Specifies the name the object should display when it is activated in the inventory.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_icon : D3 path to icon<br /> Points to an icon that is to be displayed when the object is selected in the inventory.<br /> This entry also determines wether an object is to be considered anonymous or not. <br /> <br /> inv_stackable : [0/1]<br /> Determines wether an item is an individual or can be a stack of similar objects. An<br /> Example would be the various potions. The player can pick up more than one health <br /> potion, but in the inventory he will only get one item with a counter. Keep in mind<br /> though that a stack of gold coins is not per se stackable, because usually it will be<br /> only one model of a stack of coin with a value of i.E. 10 Gold, so this means that it<br /> is not to be confused with a a single gold coin having 10 items with a value of 1 each.<br /> <br /> inv_count : &lt;N&gt;<br /> Determines the number of items this represents. This is only needed for items where<br /> stackable is 1, otherwise it is set to 0. Als the option for stackable must always <br /> precede the count, otherwise the count is set to 0.<br /> <br /> inv_droppable : [0/1]<br /> If set to 1 the item can be dropped into the map by the player. This will not<br /> work for anonymous items, since they will have no representation after they<br /> were put into the inventory.<br /> <br /> inv_delete : [0/1]<br /> Determines if an anonymous object can be deleted, after it was put into the inventory.<br /> This is advisable, because the entity will stay in memory and a mapper could still<br /> access it via scripting. If the mapper decides that an item will no longer be accessed<br /> after it has been acquired, this key should be set to 1. This can affect loading time<br /> of saved games, as entities, that are no longer needed, don't need to be saved and<br /> restored.<br /> If the mapper also creates entities on the fly, with the help of scripts, it might<br /> better to set this flag on appropriate objects to free up the limited number of<br /> entities a map can hold. The usuals candidates for this flag are all the regular loot<br /> items, because they wont be used anymore after they have been found (lik coins, purses,<br /> etc.). Also note that, if dropappable is set to 1, then this key will be ignored, since<br /> droppabale items must be turned into entities again to be placed in the map.<br /> <br /> inv_loot_type : [ 0 | 1 | 2 | 3 ]<br /> * 0 = No lootitem (default)<br /> * 1 = Jewelry/Gems<br /> * 2 = Gold<br /> * 3 = Goods<br /> This has to be set in order to define what kind of item it is and if it is a loot item,<br /> which category of loot it should account for.<br /> <br /> inv_loot_value : &lt;N&gt;<br /> Determines the amount of loot this item accounts for. This value is ignore if it is<br /> set on an item, which is of loot_type = 0.<br /> <br /> inv_map_start : [0|1]<br /> Determines wether this object should be assigned to an inventory at map start.<br /> <br /> inv_target : &lt;entityname&gt;<br /> If the item should be assigned to an entity at map start, this should get the name<br /> of the entity who shold recive it. To give an item to the player, you would use<br /> &quot;player1&quot; as the name, because this is the name that the player entity gets by<br /> default. If inv_map_start is not set or set to 0, then this key doesn't need to be<br /> set and is ignored. Since the name can be arbitrary, this means of course, that you<br /> can also give it to an AI, which the player later on meets. This should not be confused<br /> with loot, that is to be attached to an AI though. If you attach a purse or a key to<br /> an AI, which the player can frob later on, then it doesn't need to get this set, because<br /> such things will not be stored in the inventory. You could assign such things to an<br /> chest though, to give the objects to the player when he opens it. This is not directly<br /> support though, because it is assumed that chests will be filled with real objects, like<br /> TDS did it. However the T1/T2 style chests are still possible to do with some scripting.<br /> <br /> == Default equipment for map start ==<br /> <br /> This describes how to give items to the player at the mapstart, but the same mechanism can be applied to any other AI (or entity for that matter) as well.<br /> <br /> * First create your object in the editor, just like you would if you wanted to put it in the map. Create brush, select the item and/or models and place it anywhere you like in the map<br /> <br /> * Set the key inv_map_start on the object entity to the value 1.<br /> <br /> * Set the key inv_target on the object entity to the value player1. If you want to assign this object to, as an example, a guard with the name Benny, then set it to benny, assuming the entity key &quot;name&quot; is also set to &quot;benny&quot;.<br /> <br /> The objects can really be placed anyhwere you like and it doesn't really matter. As soon as the map starts, the objects will be put in the inventory, and will vanish from the map. So you could put them right in front of the players eyes, and he still wouldn't see them, as this happens at the intialization time, before the map actually becomes visible.<br /> <br /> That's it. Quite simple I would say. :)<br /> <br /> [[Category:Editing]]<br /> [[Category:Tutorial]]</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Inventory&diff=2234 2007-02-12T14:25:12Z

<p>145.253.32.51: /* Spawnargs */</p> <hr /> <div>= Overview =<br /> This article describes how to set up inventory items and how they can be given to an entity. The purpose of the inventory is, to keep track of all items that are in an entities possessions. I delibaretly use &quot;entity&quot; here because, in principle, all entities can have an inventory, even though it may only make sense for AI and the player to actuall have one. For future improvements it might be usefull for other purposes as well though.<br /> Also included is a script interface, so that a mapper can interact with the inventory in a more sophisticated way, if the default implementation is not sufficient.<br /> <br /> == Definitions ==<br /> <br /> The spawnargs can be either set in the def file as a default, or in the map file to override settings for specific entities. Naturaly this also means that they can be manipulated by scripts as well, since they are the standard way of configuring objects in Doom 3.<br /> <br /> There are several terms and types of items that can be used in the inventory:<br /> <br /> * '''anonymous items''' An anonymous object means that it will not show up as a seperate item in the inventory. An example would be normal loot like coins or golden dishes. Since they should not be stored in the inventory as seperate items, they don't need to be displayed either. In this case they only count for the total of loot and are discarded afterwards. Anonymous items also can not be dropped after they went into the inventory because they essentially no longer exist. For the loot count it obviously doesn't matter wether an item is anonymous or not, as all are added up into the loot categories. Examples are gold coins and all the other (mostly loot) items that are collected but not being used individually. <br /> <br /> * '''stackable items''' These are items that can be stacked in the inventory. This means that the player can acquire multiple instances of such items, but only one entry is shown in the inventory with a counter of how many currently are available. An example would be a health potion. The player can posses more than one health potion at a time and this would be indicated by the counter. Stackable items are identified by setting the stackable property. They also must always use the same name and category. If this doesn't match, they are considered to be of different types. This also allows for dealing out i.e. fake health potions which have no effect or deal damage instead (as an example).<br /> <br /> * '''Category''' is a classification of items, to visually group them together. This allows the player to faster scroll through the inventory because he doesn't have to cycle through all the individual items. For example a category would be 'Readables' where books and scrolls are stored, and another Category would be 'Tools' where lockpicks and other items can be stored. Note that this category is entirely up to the mapper to decide and also is option. it doesn't has any consequence as to the playabillity and is only a convenience for the player. Categories can switched of on the HUD, so that the player can use the inventory also in the Thief style (which is the default).<br /> <br /> == Spawnargs ==<br /> <br /> inv_category : string<br /> Specifies the cagtegory that the object should be filed under. This <br /> allows for player convenience and also is needed for stackable items.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_name : string<br /> Specifies the name the object should display when it is activated in the inventory.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_icon : D3 path to icon<br /> Points to an icon that is to be displayed when the object is selected in the inventory.<br /> This entry also determines wether an object is to be considered anonymous or not. <br /> <br /> inv_stackable : [0/1]<br /> Determines wether an item is an individual or can be a stack of similar objects. An<br /> Example would be the various potions. The player can pick up more than one health <br /> potion, but in the inventory he will only get one item with a counter. Keep in mind<br /> though that a stack of gold coins is not per se stackable, because usually it will be<br /> only one model of a stack of coin with a value of i.E. 10 Gold, so this means that it<br /> is not to be confused with a a single gold coin having 10 items with a value of 1 each.<br /> <br /> inv_count : &lt;N&gt;<br /> Determines the number of items this represents. This is only needed for items where<br /> stackable is 1, otherwise it is set to 0. Als the option for stackable must always <br /> precede the count, otherwise the count is set to 0.<br /> <br /> inv_droppable : [0/1]<br /> If set to 1 the item can be dropped into the map by the player. This will not<br /> work for anonymous items, since they will have no representation after they<br /> were put into the inventory.<br /> <br /> inv_delete : [0/1]<br /> Determines if an anonymous object can be deleted, after it was put into the inventory.<br /> This is advisable, because the entity will stay in memory and a mapper could still<br /> access it via scripting. If the mapper decides that an item will no longer be accessed<br /> after it has been acquired, this key should be set to 1. This can affect loading time<br /> of saved games, as entities, that are no longer needed, don't need to be saved and<br /> restored.<br /> If the mapper also creates entities on the fly, with the help of scripts, it might<br /> better to set this flag on appropriate objects to free up the limited number of<br /> entities a map can hold. The usuals candidates for this flag are all the regular loot<br /> items, because they wont be used anymore after they have been found (lik coins, purses,<br /> etc.). Also note that, if dropappable is set to 1, then this key will be ignored, since<br /> droppabale items must be turned into entities again to be placed in the map.<br /> <br /> inv_loot_type : [ 0 | 1 | 2 | 3 ]<br /> * 0 = No lootitem (default)<br /> * 1 = Jewelry/Gems<br /> * 2 = Gold<br /> * 3 = Goods<br /> This has to be set in order to define what kind of item it is and if it is a loot item,<br /> which category of loot it should account for.<br /> <br /> inv_loot_value : &lt;N&gt;<br /> Determines the amount of loot this item accounts for. This value is ignore if it is<br /> set on an item, which is of loot_type = 0.<br /> <br /> inv_map_start : [0|1]<br /> Determines wether this object should be assigned to an inventory at map start.<br /> <br /> inv_target : &lt;entityname&gt;<br /> If the item should be assigned to an entity at map start, this should get the name<br /> of the entity who shold recive it. To give an item to the player, you would use<br /> &quot;player1&quot; as the name, because this is the name that the player entity gets by<br /> default. If inv_map_start is not set or set to 0, then this key doesn't need to be<br /> set and is ignored. Since the name can be arbitrary, this means of course, that you<br /> can also give it to an AI, which the player later on meets. This should not be confused<br /> with loot, that is to be attached to an AI though. If you attach a purse or a key to<br /> an AI, which the player can frob later on, then it doesn't need to get this set, because<br /> such things will not be stored in the inventory. You could assign such things to an<br /> chest though, to give the objects to the player when he opens it. This is not directly<br /> support though, because it is assumed that chests will be filled with real objects, like<br /> TDS did it. However the T1/T2 style chests are still possible to do with some scripting.<br /> <br /> [[Category:Editing]]<br /> [[Category:Tutorial]]</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Inventory&diff=2233 2007-02-12T14:07:43Z

<p>145.253.32.51: /* Spawnargs */</p> <hr /> <div>= Overview =<br /> This article describes how to set up inventory items and how they can be given to an entity. The purpose of the inventory is, to keep track of all items that are in an entities possessions. I delibaretly use &quot;entity&quot; here because, in principle, all entities can have an inventory, even though it may only make sense for AI and the player to actuall have one. For future improvements it might be usefull for other purposes as well though.<br /> Also included is a script interface, so that a mapper can interact with the inventory in a more sophisticated way, if the default implementation is not sufficient.<br /> <br /> == Definitions ==<br /> <br /> The spawnargs can be either set in the def file as a default, or in the map file to override settings for specific entities. Naturaly this also means that they can be manipulated by scripts as well, since they are the standard way of configuring objects in Doom 3.<br /> <br /> There are several terms and types of items that can be used in the inventory:<br /> <br /> * '''anonymous items''' An anonymous object means that it will not show up as a seperate item in the inventory. An example would be normal loot like coins or golden dishes. Since they should not be stored in the inventory as seperate items, they don't need to be displayed either. In this case they only count for the total of loot and are discarded afterwards. Anonymous items also can not be dropped after they went into the inventory because they essentially no longer exist. For the loot count it obviously doesn't matter wether an item is anonymous or not, as all are added up into the loot categories. Examples are gold coins and all the other (mostly loot) items that are collected but not being used individually. <br /> <br /> * '''stackable items''' These are items that can be stacked in the inventory. This means that the player can acquire multiple instances of such items, but only one entry is shown in the inventory with a counter of how many currently are available. An example would be a health potion. The player can posses more than one health potion at a time and this would be indicated by the counter. Stackable items are identified by setting the stackable property. They also must always use the same name and category. If this doesn't match, they are considered to be of different types. This also allows for dealing out i.e. fake health potions which have no effect or deal damage instead (as an example).<br /> <br /> * '''Category''' is a classification of items, to visually group them together. This allows the player to faster scroll through the inventory because he doesn't have to cycle through all the individual items. For example a category would be 'Readables' where books and scrolls are stored, and another Category would be 'Tools' where lockpicks and other items can be stored. Note that this category is entirely up to the mapper to decide and also is option. it doesn't has any consequence as to the playabillity and is only a convenience for the player. Categories can switched of on the HUD, so that the player can use the inventory also in the Thief style (which is the default).<br /> <br /> == Spawnargs ==<br /> <br /> inv_category : string<br /> Specifies the cagtegory that the object should be filed under. This <br /> allows for player convenience and also is needed for stackable items.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_name : string<br /> Specifies the name the object should display when it is activated in the inventory.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_icon : D3 path to icon<br /> Points to an icon that is to be displayed when the object is selected in the inventory.<br /> This entry also determines wether an object is to be considered anonymous or not. <br /> <br /> inv_droppable : [0/1]<br /> If set to 1 the item can be dropped into the map by the player. This will not<br /> work for anonymous items, since they will have no representation after they<br /> were put into the inventory.<br /> <br /> inv_delete : [0/1]<br /> Determines if an anonymous object can be deleted, after it was put into the inventory.<br /> This is advisable, because the entity will stay in memory and a mapper could still<br /> access it via scripting. If the mapper decides that an item will no longer be accessed<br /> after it has been acquired, this key should be set to 1. This can affect loading time<br /> of saved games, as entities, that are no longer needed, don't need to be saved and<br /> restored.<br /> If the mapper also creates entities on the fly, with the help of scripts, it might<br /> better to set this flag on appropriate objects to free up the limited number of<br /> entities a map can hold. The usuals candidates for this flag are all the regular loot<br /> items, because they wont be used anymore after they have been found (lik coins, purses,<br /> etc.). Also note that, if dropappable is set to 1, then this key will be ignored, since<br /> droppabale items must be turned into entities again to be placed in the map.<br /> <br /> [[Category:Editing]]<br /> [[Category:Tutorial]]</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Inventory&diff=2232 2007-02-12T14:07:01Z

<p>145.253.32.51: /* Spawnargs */</p> <hr /> <div>= Overview =<br /> This article describes how to set up inventory items and how they can be given to an entity. The purpose of the inventory is, to keep track of all items that are in an entities possessions. I delibaretly use &quot;entity&quot; here because, in principle, all entities can have an inventory, even though it may only make sense for AI and the player to actuall have one. For future improvements it might be usefull for other purposes as well though.<br /> Also included is a script interface, so that a mapper can interact with the inventory in a more sophisticated way, if the default implementation is not sufficient.<br /> <br /> == Definitions ==<br /> <br /> The spawnargs can be either set in the def file as a default, or in the map file to override settings for specific entities. Naturaly this also means that they can be manipulated by scripts as well, since they are the standard way of configuring objects in Doom 3.<br /> <br /> There are several terms and types of items that can be used in the inventory:<br /> <br /> * '''anonymous items''' An anonymous object means that it will not show up as a seperate item in the inventory. An example would be normal loot like coins or golden dishes. Since they should not be stored in the inventory as seperate items, they don't need to be displayed either. In this case they only count for the total of loot and are discarded afterwards. Anonymous items also can not be dropped after they went into the inventory because they essentially no longer exist. For the loot count it obviously doesn't matter wether an item is anonymous or not, as all are added up into the loot categories. Examples are gold coins and all the other (mostly loot) items that are collected but not being used individually. <br /> <br /> * '''stackable items''' These are items that can be stacked in the inventory. This means that the player can acquire multiple instances of such items, but only one entry is shown in the inventory with a counter of how many currently are available. An example would be a health potion. The player can posses more than one health potion at a time and this would be indicated by the counter. Stackable items are identified by setting the stackable property. They also must always use the same name and category. If this doesn't match, they are considered to be of different types. This also allows for dealing out i.e. fake health potions which have no effect or deal damage instead (as an example).<br /> <br /> * '''Category''' is a classification of items, to visually group them together. This allows the player to faster scroll through the inventory because he doesn't have to cycle through all the individual items. For example a category would be 'Readables' where books and scrolls are stored, and another Category would be 'Tools' where lockpicks and other items can be stored. Note that this category is entirely up to the mapper to decide and also is option. it doesn't has any consequence as to the playabillity and is only a convenience for the player. Categories can switched of on the HUD, so that the player can use the inventory also in the Thief style (which is the default).<br /> <br /> == Spawnargs ==<br /> <br /> inv_category : string<br /> Specifies the cagtegory that the object should be filed under. This <br /> allows for player convenience and also is needed for stackable items.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_name : string<br /> Specifies the name the object should display when it is activated in the inventory.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_icon : D3 path to icon<br /> Points to an icon that is to be displayed when the object is selected in the inventory.<br /> This entry also determines wether an object is to be considered anonymous or not. <br /> <br /> inv_droppable : [0/1]<br /> If set to 1 the item can be dropped into the map by the player. This will not<br /> work for anonymous items, since they will have no representation after they<br /> were put into the inventory.<br /> <br /> inv_delete : [0/1]<br /> Determines if an anonymous object can be deleted, after it was put into the inventory.<br /> This is advisable, because the entity will stay in memory and a mapper could still<br /> access it via scripting. If the mapper decides that an item will no longer be accessed<br /> after it has been acquired, this key should be set to 1. This can affect loading time<br /> of saved games, as entities, that are no longer needed, don't need to be saved and<br /> restored.<br /> If the mapper also creates entities on the fly, with the help of scripts, it might<br /> better to set this flag on appropriate objects tofree up the limited number of entities<br /> a map can hold. The usuals candidates for this flag are all the regular loot items,<br /> because they wont be used anymore after they have been found (lik coins, purses, etc.). <br /> Also note that, if dropappable is set to 1, then this key will be ignored, since<br /> droppabale items must be turned into entities again to be placed in the map.<br /> <br /> [[Category:Editing]]<br /> [[Category:Tutorial]]</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Inventory&diff=2231 2007-02-12T14:05:36Z

<p>145.253.32.51: /* Spawnargs */</p> <hr /> <div>= Overview =<br /> This article describes how to set up inventory items and how they can be given to an entity. The purpose of the inventory is, to keep track of all items that are in an entities possessions. I delibaretly use &quot;entity&quot; here because, in principle, all entities can have an inventory, even though it may only make sense for AI and the player to actuall have one. For future improvements it might be usefull for other purposes as well though.<br /> Also included is a script interface, so that a mapper can interact with the inventory in a more sophisticated way, if the default implementation is not sufficient.<br /> <br /> == Definitions ==<br /> <br /> The spawnargs can be either set in the def file as a default, or in the map file to override settings for specific entities. Naturaly this also means that they can be manipulated by scripts as well, since they are the standard way of configuring objects in Doom 3.<br /> <br /> There are several terms and types of items that can be used in the inventory:<br /> <br /> * '''anonymous items''' An anonymous object means that it will not show up as a seperate item in the inventory. An example would be normal loot like coins or golden dishes. Since they should not be stored in the inventory as seperate items, they don't need to be displayed either. In this case they only count for the total of loot and are discarded afterwards. Anonymous items also can not be dropped after they went into the inventory because they essentially no longer exist. For the loot count it obviously doesn't matter wether an item is anonymous or not, as all are added up into the loot categories. Examples are gold coins and all the other (mostly loot) items that are collected but not being used individually. <br /> <br /> * '''stackable items''' These are items that can be stacked in the inventory. This means that the player can acquire multiple instances of such items, but only one entry is shown in the inventory with a counter of how many currently are available. An example would be a health potion. The player can posses more than one health potion at a time and this would be indicated by the counter. Stackable items are identified by setting the stackable property. They also must always use the same name and category. If this doesn't match, they are considered to be of different types. This also allows for dealing out i.e. fake health potions which have no effect or deal damage instead (as an example).<br /> <br /> * '''Category''' is a classification of items, to visually group them together. This allows the player to faster scroll through the inventory because he doesn't have to cycle through all the individual items. For example a category would be 'Readables' where books and scrolls are stored, and another Category would be 'Tools' where lockpicks and other items can be stored. Note that this category is entirely up to the mapper to decide and also is option. it doesn't has any consequence as to the playabillity and is only a convenience for the player. Categories can switched of on the HUD, so that the player can use the inventory also in the Thief style (which is the default).<br /> <br /> == Spawnargs ==<br /> <br /> inv_category : string<br /> Specifies the cagtegory that the object should be filed under. This <br /> allows for player convenience and also is needed for stackable items.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_name : string<br /> Specifies the name the object should display when it is activated in the inventory.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_icon : D3 path to icon<br /> Points to an icon that is to be displayed when the object is selected in the inventory.<br /> This entry also determines wether an object is to be considered anonymous or not. <br /> <br /> inv_droppable : [0/1]<br /> If set to 1 the item can be dropped into the map by the player. This will not<br /> work for anonymous items, since they will have no representation after they<br /> were put into the inventory.<br /> <br /> inv_delete : [0/1]<br /> Determines if an anonymous object can be deleted, after it was put into the inventory.<br /> This is advisable, because the entity will stay in memory and a mapper could still<br /> access it via scripting. If the mapper decides that an item will no longer be accessed<br /> after it<br /> has been acquired, this key should be set to 1. This can affect loading time of saved<br /> games, as entities, that are no longer needed, don't need to be saved and restored. If<br /> the mapper also creates entities on the fly, with the help of scripts, it might better<br /> to set this flag on appropriate objects tofree up the limited number of entities a map<br /> can hold. The usuals candidates for this flag are all the regular loot items, because<br /> they wont be used anymore after they have been found (lik coins, purses, etc.). Also<br /> note that, if dropappable is set to 1, then this key will be ignored, since dropabale<br /> items must be turned into entities again to be placed in the map.<br /> <br /> [[Category:Editing]]<br /> [[Category:Tutorial]]</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Inventory&diff=2230 2007-02-12T14:01:35Z

<p>145.253.32.51: /* Definitions */</p> <hr /> <div>= Overview =<br /> This article describes how to set up inventory items and how they can be given to an entity. The purpose of the inventory is, to keep track of all items that are in an entities possessions. I delibaretly use &quot;entity&quot; here because, in principle, all entities can have an inventory, even though it may only make sense for AI and the player to actuall have one. For future improvements it might be usefull for other purposes as well though.<br /> Also included is a script interface, so that a mapper can interact with the inventory in a more sophisticated way, if the default implementation is not sufficient.<br /> <br /> == Definitions ==<br /> <br /> The spawnargs can be either set in the def file as a default, or in the map file to override settings for specific entities. Naturaly this also means that they can be manipulated by scripts as well, since they are the standard way of configuring objects in Doom 3.<br /> <br /> There are several terms and types of items that can be used in the inventory:<br /> <br /> * '''anonymous items''' An anonymous object means that it will not show up as a seperate item in the inventory. An example would be normal loot like coins or golden dishes. Since they should not be stored in the inventory as seperate items, they don't need to be displayed either. In this case they only count for the total of loot and are discarded afterwards. Anonymous items also can not be dropped after they went into the inventory because they essentially no longer exist. For the loot count it obviously doesn't matter wether an item is anonymous or not, as all are added up into the loot categories. Examples are gold coins and all the other (mostly loot) items that are collected but not being used individually. <br /> <br /> * '''stackable items''' These are items that can be stacked in the inventory. This means that the player can acquire multiple instances of such items, but only one entry is shown in the inventory with a counter of how many currently are available. An example would be a health potion. The player can posses more than one health potion at a time and this would be indicated by the counter. Stackable items are identified by setting the stackable property. They also must always use the same name and category. If this doesn't match, they are considered to be of different types. This also allows for dealing out i.e. fake health potions which have no effect or deal damage instead (as an example).<br /> <br /> * '''Category''' is a classification of items, to visually group them together. This allows the player to faster scroll through the inventory because he doesn't have to cycle through all the individual items. For example a category would be 'Readables' where books and scrolls are stored, and another Category would be 'Tools' where lockpicks and other items can be stored. Note that this category is entirely up to the mapper to decide and also is option. it doesn't has any consequence as to the playabillity and is only a convenience for the player. Categories can switched of on the HUD, so that the player can use the inventory also in the Thief style (which is the default).<br /> <br /> == Spawnargs ==<br /> <br /> inv_category : string<br /> Specifies the cagtegory that the object should be filed under. This <br /> allows for player convenience and also is needed for stackable items.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_name : string<br /> Specifies the name the object should display when it is activated in the inventory.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_icon : D3 path to icon<br /> Points to an icon that is to be displayed when the object is selected in the inventory.<br /> This entry also determines wether an object is to be considered anonymous or not. <br /> <br /> inv_droppable : [0/1]<br /> If set to 1 the item can be dropped into the map by the player. This will not<br /> work for anonymous items, since they will have no representation after they<br /> were put into the inventory.<br /> <br /> inv_delete : [0/1]<br /> Determines if an anonymous object can be deleted, after it was put into the inventory.<br /> this is neccessary, because the entity will stay in memory and a mapper can access it<br /> via scripting. If the mapper decides that an item will no longer be accessed after it<br /> has been acquired, this key should be set to 1. This can affect loading time of saved<br /> games, as entities, that are no longer needed, don't need to be saved and restored. If<br /> the mapper also creates entities on the fly, with the help of scripts, it might better<br /> to set this flag on appropriate objects tofree up the limited number of entities a map<br /> can hold. The usuals candidates for this flag are all the regular loot items, because<br /> they wont be used anymore after they have been found (lik coins, purses, etc.). Also<br /> note that, if dropappable is set to 1, then this key will be ignored, since dropabale<br /> items must be turned into entities again to be placed in the map.<br /> <br /> [[Category:Editing]]<br /> [[Category:Tutorial]]</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Inventory&diff=2229 2007-02-12T14:00:53Z

<p>145.253.32.51: /* Definitions */</p> <hr /> <div>= Overview =<br /> This article describes how to set up inventory items and how they can be given to an entity. The purpose of the inventory is, to keep track of all items that are in an entities possessions. I delibaretly use &quot;entity&quot; here because, in principle, all entities can have an inventory, even though it may only make sense for AI and the player to actuall have one. For future improvements it might be usefull for other purposes as well though.<br /> Also included is a script interface, so that a mapper can interact with the inventory in a more sophisticated way, if the default implementation is not sufficient.<br /> <br /> == Definitions ==<br /> <br /> The spawnargs can be either set in the def file as a default, or in the map file to override settings for specific entities. Naturaly this also means that they can be manipulated by scripts as well, since they are the standard way of configuring objects in Doom 3.<br /> <br /> There are several terms and types of items that can be used in the inventory:<br /> <br /> * '''anonymous items''' Gold coins and all the other (mostly loot) items that are collected but not being used individually.<br /> <br /> An anonymous object means that it will not show up as a seperate item in the inventory. An example would be normal loot like coins or golden dishes. Since they should not be stored in the inventory as seperate items, they don't need to be displayed either. In this case they only count for the total of loot and are discarded afterwards. Anonymous items also can not be dropped after they went into the inventory because they essentially no longer exist. For the loot count it obviously doesn't matter wether an item is anonymous or not, as all are added up into the loot categories.<br /> <br /> * '''stackable items''' These are items that can be stacked in the inventory. This means that the player can acquire multiple instances of such items, but only one entry is shown in the inventory with a counter of how many currently are available. An example would be a health potion. The player can posses more than one health potion at a time and this would be indicated by the counter. Stackable items are identified by setting the stackable property. They also must always use the same name and category. If this doesn't match, they are considered to be of different types. This also allows for dealing out i.e. fake health potions which have no effect or deal damage instead (as an example).<br /> <br /> * '''Category''' is a classification of items, to visually group them together. This allows the player to faster scroll through the inventory because he doesn't have to cycle through all the individual items. For example a category would be 'Readables' where books and scrolls are stored, and another Category would be 'Tools' where lockpicks and other items can be stored. Note that this category is entirely up to the mapper to decide and also is option. it doesn't has any consequence as to the playabillity and is only a convenience for the player. Categories can switched of on the HUD, so that the player can use the inventory also in the Thief style (which is the default).<br /> <br /> == Spawnargs ==<br /> <br /> inv_category : string<br /> Specifies the cagtegory that the object should be filed under. This <br /> allows for player convenience and also is needed for stackable items.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_name : string<br /> Specifies the name the object should display when it is activated in the inventory.<br /> example: &quot;inv_name&quot; &quot;Health Potion&quot;<br /> <br /> inv_icon : D3 path to icon<br /> Points to an icon that is to be displayed when the object is selected in the inventory.<br /> This entry also determines wether an object is to be considered anonymous or not. <br /> <br /> inv_droppable : [0/1]<br /> If set to 1 the item can be dropped into the map by the player. This will not<br /> work for anonymous items, since they will have no representation after they<br /> were put into the inventory.<br /> <br /> inv_delete : [0/1]<br /> Determines if an anonymous object can be deleted, after it was put into the inventory.<br /> this is neccessary, because the entity will stay in memory and a mapper can access it<br /> via scripting. If the mapper decides that an item will no longer be accessed after it<br /> has been acquired, this key should be set to 1. This can affect loading time of saved<br /> games, as entities, that are no longer needed, don't need to be saved and restored. If<br /> the mapper also creates entities on the fly, with the help of scripts, it might better<br /> to set this flag on appropriate objects tofree up the limited number of entities a map<br /> can hold. The usuals candidates for this flag are all the regular loot items, because<br /> they wont be used anymore after they have been found (lik coins, purses, etc.). Also<br /> note that, if dropappable is set to 1, then this key will be ignored, since dropabale<br /> items must be turned into entities again to be placed in the map.<br /> <br /> [[Category:Editing]]<br /> [[Category:Tutorial]]</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=How_to_pack_your_Mission&diff=1452 2005-12-05T17:46:08Z

<p>145.253.32.51: </p> <hr /> <div>You should pack all your assets into a seperate directory following the same structure as can be seen in the various origina PK4 files. Then you can use any application to pack it into a zip file (Winzip, WinRAR, etc.). After it is packed you just rename the zip extension to pk4.<br /> <br /> The result can be dropped either in the darkmod directory or in the base folder of your Doom 3 installation.</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=How_to_pack_your_Mission&diff=1451 2005-12-05T17:45:57Z

<p>145.253.32.51: </p> <hr /> <div>You should pack all your assets into a seperate directory following the same structure as can be seen in the various origina PK4 files. Then you can use any application to pack it into a zip file (Winzip, WinRAR, etc.). After it is packed you just rename the zip extension to pk4.<br /> <br /> The result can be dropped either in the darkdod directory or in the base folder of your Doom 3 installation.</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=How_to_pack_your_Mission&diff=1450 2005-12-05T17:45:49Z

<p>145.253.32.51: </p> <hr /> <div>You should pack al your assets into a seperate directory following the same structure as can be seen in the various origina PK4 files. Then you can use any application to pack it into a zip file (Winzip, WinRAR, etc.). After it is packed you just rename the zip extension to pk4.<br /> <br /> The result can be dropped either in the darkdod directory or in the base folder of your Doom 3 installation.</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Coding&diff=1449 2005-12-05T17:43:38Z

<p>145.253.32.51: </p> <hr /> <div>&lt;dl&gt;<br /> &lt;dt&gt;[[Scripting]]&lt;/dt&gt;<br /> &lt;dd&gt;Info relevant to scripting for The Dark Mod&lt;/dd&gt;<br /> <br /> &lt;dt&gt;[[SDK]]&lt;/dt&gt;<br /> &lt;dd&gt;Info relevant to coding in the SDK for The Dark Mod&lt;/dd&gt;<br /> <br /> &lt;/dl&gt;</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Coding&diff=1448 2005-12-05T17:42:57Z

<p>145.253.32.51: </p> <hr /> <div>&lt;dl&gt;<br /> &lt;dt&gt;[[Scripting]]&lt;/dt&gt;<br /> &lt;dd&gt;Information how to get The Dark Mod running&lt;/dd&gt;<br /> <br /> &lt;dt&gt;[[SDK]]&lt;/dt&gt;<br /> &lt;dd&gt;Information about level design and the tools&lt;/dd&gt;<br /> <br /> &lt;/dl&gt;</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Coding&diff=1447 2005-12-05T17:42:36Z

<p>145.253.32.51: </p> <hr /> <div>&lt;h2&gt;Coding sections&lt;/h2&gt;<br /> <br /> &lt;dl&gt;<br /> &lt;dt&gt;[[Scripting]]&lt;/dt&gt;<br /> &lt;dd&gt;Information how to get The Dark Mod running&lt;/dd&gt;<br /> <br /> &lt;dt&gt;[[SDK]]&lt;/dt&gt;<br /> &lt;dd&gt;Information about level design and the tools&lt;/dd&gt;<br /> <br /> &lt;/dl&gt;</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Coding&diff=1446 2005-12-05T17:42:16Z

<p>145.253.32.51: </p> <hr /> <div>&lt;h2&gt;Editing Categories:&lt;/h2&gt;<br /> <br /> &lt;dl&gt;<br /> &lt;dt&gt;[[Scripting]]&lt;/dt&gt;<br /> &lt;dd&gt;Information how to get The Dark Mod running&lt;/dd&gt;<br /> <br /> &lt;dt&gt;[[SDK]]&lt;/dt&gt;<br /> &lt;dd&gt;Information about level design and the tools&lt;/dd&gt;<br /> <br /> &lt;/dl&gt;</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Coding&diff=1445 2005-12-05T17:41:52Z

<p>145.253.32.51: </p> <hr /> <div>&lt;h2&gt;Editing Categories:&lt;/h2&gt;<br /> <br /> &lt;dl&gt;<br /> &lt;dt&gt;[[Scripting]]&lt;/dt&gt;<br /> &lt;dd&gt;Information how to get The Dark Mod running&lt;/dd&gt;<br /> <br /> &lt;dt&gt;[[SDK]]&lt;/dt&gt;<br /> &lt;dd&gt;Information about level design and the tools&lt;/dd&gt;<br /> <br /> &lt;/dl&gt;<br /> <br /> &lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;<br /> &lt;p style=&quot;margin:2em 0 2em 0; text-align:center; font-size:94%&quot;&gt;(Create a new page by making a link to it, then click it. Or you can just go to www.evilarmyfilms.com/darkwiki/yourpagename)&lt;/p&gt;</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Coding&diff=1444 2005-12-05T17:41:20Z

<p>145.253.32.51: </p> <hr /> <div>&lt;h2&gt;Editing Categories:&lt;/h2&gt;<br /> <br /> &lt;dl&gt;<br /> &lt;dt&gt;[[Installation]]&lt;/dt&gt;<br /> &lt;dd&gt;Information how to get The Dark Mod running&lt;/dd&gt;<br /> <br /> &lt;dt&gt;[[Editing]]&lt;/dt&gt;<br /> &lt;dd&gt;Information about level design and the tools&lt;/dd&gt;<br /> <br /> &lt;dt&gt;[[Textures]]&lt;/dt&gt;<br /> &lt;dd&gt;Explanation of material shaders and image files&lt;/dd&gt;<br /> <br /> &lt;dt&gt;[[Modeling]]&lt;/dt&gt;<br /> &lt;dd&gt;Modeling and file format information&lt;/dd&gt;<br /> <br /> &lt;dt&gt;[[Sound]]&lt;/dt&gt;<br /> &lt;dd&gt;Soundeffects, ambients and how to get them ingame&lt;/dd&gt;<br /> <br /> &lt;dt&gt;[[Coding]]&lt;/dt&gt;<br /> &lt;dd&gt;Source code modification, level and GUI scripting&lt;/dd&gt;<br /> <br /> &lt;dt&gt;[[Release]]&lt;/dt&gt;<br /> &lt;dd&gt;How to pack a mission, and get it tested and released!&lt;/dd&gt;<br /> &lt;/dl&gt;<br /> <br /> &lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;<br /> &lt;p style=&quot;margin:2em 0 2em 0; text-align:center; font-size:94%&quot;&gt;(Create a new page by making a link to it, then click it. Or you can just go to www.evilarmyfilms.com/darkwiki/yourpagename)&lt;/p&gt;</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Editing&diff=1443 2005-12-05T17:39:32Z

<p>145.253.32.51: </p> <hr /> <div>The general hub for DarkMod specific editing - links to articles about:<br /> <br /> [[AI]]<br /> <br /> [[Sound Prop]]<br /> <br /> [[Creating doors]]<br /> <br /> [[Visportals]]<br /> <br /> <br /> <br /> and other specifics that are relevant to the mod.</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Installation&diff=1442 2005-12-05T17:37:53Z

<p>145.253.32.51: /* Installing The Dark Mod on Windows */</p> <hr /> <div>== Requirements ==<br /> <br /> <br /> In order to install The Dark Mod D3 has to have at least patch for 1.3 installed. You can download the patch here http://download.activision.com/doom3/D3_1_3.exe. It is recommended that the installation path for Doom 3 contains no blanks as it might cause problems with some of the tools. Additionally it is recommended to keep all the paths lower case. This is especially important as Doom 3 can also run on other platforms like Linux where pathnames are different depending on their case (i.e. /home/sparhawk/Doom3 is a different path than /home/sparhawk/doom3). Windows does not have such restrictions but it happened on some systems that there were still issues with paths, as Doom 3 has it's own internal library of handling paths in a system independent way and therefore this might cause maps to break on some systems while they can work on others.<br /> <br /> Depending on the operating system additional requirements may apply. Doom 3 currently supports Windows, Linux and Mac platforms. Requirements for the various platforms will be added at a later point, when development has progressed to a state where it makes sense to ensure platform compatibillity.<br /> <br /> == Installing The Dark Mod on Windows ==<br /> <br /> <br /> In order to install The Dark Mod, once the requirements have been satsified, you should download the package which is provided (insert link here). In the distribution is a DLL contained named DevIL.dll which is required for image handling. Since as the time of writing there is no installer, so the user must install this library himself. To do this the DLL must be copied in the windows/system32 directory. The DLL can also be put in any other directory where a path is pointing to (meaning that the directory is included in the PATH environment variable when Doom 3 is run). If the library is not found when the mod is loaded, Doom 3 will show it's blue window and can not be started. The downloaded archive must be extracted directly into the Doom 3 folder which will create a darkmod folder in there with all files neccessary to run the mod.<br /> <br /> == Installing The Dark Mod on Linux ==<br /> <br /> <br /> Instructions on how to install The Dark Mod on linux will be added at a later point, as currently there is no development done to ensure linux compatibillity.<br /> <br /> <br /> <br /> It is assumed that running a mod is consistent throughout the supported platforms. In case this turns out not to be true, we will add specific instructions for certain platforms later.<br /> In order to run The Dark Mod, Doom 3 can be started normally. In the lower right corner you can see a button saying &quot;MOD&quot;. Clicking on this button will cause a dialog to appear listing all the mods currently installed. You can select Darkmod by choosing the appropriate entry from the dialog and load it. This will cause Doom 3 to load the mod data and initialze the mod. For later releases it is planned to create a total conversion, which means that we will provide menu screens for all the various settings to be done in a consistant style fitting to the The Dark Mod universe. Since this is still under development, TDM maps have to be loaded via console commands using &quot;map &lt;mapname&gt;&quot;. For instructions on how to use the console please refer to the game manual or tutorials which can be found (insert link to general tutorial site).<br /> <br /> == Running the Mod ==<br /> <br /> Alterantively The Dark Mod can be initialized directly from the command line (or via an icon from the desktop) by using the commandline <br /> '''Windows:'''<br /> &quot;&lt;path to Doom 3&gt;/doom3.exe +set fs_game darkmod&quot;<br /> <br /> '''Linux:'''<br /> &quot;&lt;path to Doom 3&gt;/doom3 +set fs_game darkmod&quot;<br /> <br /> It is recommended to use this way of running The Dark Mod, as it appears that Doom 3 will handle paths more consistently then loading the mod manually.</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Installation&diff=1441 2005-12-05T17:37:10Z

<p>145.253.32.51: /* Requirements */</p> <hr /> <div>== Requirements ==<br /> <br /> <br /> In order to install The Dark Mod D3 has to have at least patch for 1.3 installed. You can download the patch here http://download.activision.com/doom3/D3_1_3.exe. It is recommended that the installation path for Doom 3 contains no blanks as it might cause problems with some of the tools. Additionally it is recommended to keep all the paths lower case. This is especially important as Doom 3 can also run on other platforms like Linux where pathnames are different depending on their case (i.e. /home/sparhawk/Doom3 is a different path than /home/sparhawk/doom3). Windows does not have such restrictions but it happened on some systems that there were still issues with paths, as Doom 3 has it's own internal library of handling paths in a system independent way and therefore this might cause maps to break on some systems while they can work on others.<br /> <br /> Depending on the operating system additional requirements may apply. Doom 3 currently supports Windows, Linux and Mac platforms. Requirements for the various platforms will be added at a later point, when development has progressed to a state where it makes sense to ensure platform compatibillity.<br /> <br /> == Installing The Dark Mod on Windows ==<br /> <br /> <br /> In order to install The Dark Mod, once the requirements have been satsified, you should download the package which is provided (inert link here). In the distribution is a DLL contained named DevIL.dll which is required for image handling. Since as the time of writing there is no installer, so the user must install this library himself. To do this the DLL must be copied in the windows/system32 directory. The DLL can also be put in any other directory where a path is pointing to (meaning that the directory is included in the PATH environment variable when Doom 3 is run). If the library is not found when the mod is loaded, Doom 3 will show it's blue window and can not be started. The downloaded archive must be extracted directly into the Doom 3 folder which will create a darkmod folder in there with all files neccessary to run the mod.<br /> <br /> <br /> <br /> == Installing The Dark Mod on Linux ==<br /> <br /> <br /> Instructions on how to install The Dark Mod on linux will be added at a later point, as currently there is no development done to ensure linux compatibillity.<br /> <br /> <br /> <br /> It is assumed that running a mod is consistent throughout the supported platforms. In case this turns out not to be true, we will add specific instructions for certain platforms later.<br /> In order to run The Dark Mod, Doom 3 can be started normally. In the lower right corner you can see a button saying &quot;MOD&quot;. Clicking on this button will cause a dialog to appear listing all the mods currently installed. You can select Darkmod by choosing the appropriate entry from the dialog and load it. This will cause Doom 3 to load the mod data and initialze the mod. For later releases it is planned to create a total conversion, which means that we will provide menu screens for all the various settings to be done in a consistant style fitting to the The Dark Mod universe. Since this is still under development, TDM maps have to be loaded via console commands using &quot;map &lt;mapname&gt;&quot;. For instructions on how to use the console please refer to the game manual or tutorials which can be found (insert link to general tutorial site).<br /> <br /> == Running the Mod ==<br /> <br /> Alterantively The Dark Mod can be initialized directly from the command line (or via an icon from the desktop) by using the commandline <br /> '''Windows:'''<br /> &quot;&lt;path to Doom 3&gt;/doom3.exe +set fs_game darkmod&quot;<br /> <br /> '''Linux:'''<br /> &quot;&lt;path to Doom 3&gt;/doom3 +set fs_game darkmod&quot;<br /> <br /> It is recommended to use this way of running The Dark Mod, as it appears that Doom 3 will handle paths more consistently then loading the mod manually.</div>

145.253.32.51 https://wiki.thedarkmod.com/index.php?title=Installation&diff=1440 2005-12-05T17:36:51Z

<p>145.253.32.51: /* Requirements */</p> <hr /> <div>== Requirements ==<br /> <br /> <br /> In order to install The Dark Mod D3 has to have at least patch for 1.3 installed. You can download the patch http://download.activision.com/doom3/D3_1_3.exe. It is recommended that the installation path for Doom 3 contains no blanks as it might cause problems with some of the tools. Additionally it is recommended to keep all the paths lower case. This is especially important as Doom 3 can also run on other platforms like Linux where pathnames are different depending on their case (i.e. /home/sparhawk/Doom3 is a different path than /home/sparhawk/doom3). Windows does not have such restrictions but it happened on some systems that there were still issues with paths, as Doom 3 has it's own internal library of handling paths in a system independent way and therefore this might cause maps to break on some systems while they can work on others.<br /> <br /> Depending on the operating system additional requirements may apply. Doom 3 currently supports Windows, Linux and Mac platforms. Requirements for the various platforms will be added at a later point, when development has progressed to a state where it makes sense to ensure platform compatibillity.<br /> <br /> == Installing The Dark Mod on Windows ==<br /> <br /> <br /> In order to install The Dark Mod, once the requirements have been satsified, you should download the package which is provided (inert link here). In the distribution is a DLL contained named DevIL.dll which is required for image handling. Since as the time of writing there is no installer, so the user must install this library himself. To do this the DLL must be copied in the windows/system32 directory. The DLL can also be put in any other directory where a path is pointing to (meaning that the directory is included in the PATH environment variable when Doom 3 is run). If the library is not found when the mod is loaded, Doom 3 will show it's blue window and can not be started. The downloaded archive must be extracted directly into the Doom 3 folder which will create a darkmod folder in there with all files neccessary to run the mod.<br /> <br /> <br /> <br /> == Installing The Dark Mod on Linux ==<br /> <br /> <br /> Instructions on how to install The Dark Mod on linux will be added at a later point, as currently there is no development done to ensure linux compatibillity.<br /> <br /> <br /> <br /> It is assumed that running a mod is consistent throughout the supported platforms. In case this turns out not to be true, we will add specific instructions for certain platforms later.<br /> In order to run The Dark Mod, Doom 3 can be started normally. In the lower right corner you can see a button saying &quot;MOD&quot;. Clicking on this button will cause a dialog to appear listing all the mods currently installed. You can select Darkmod by choosing the appropriate entry from the dialog and load it. This will cause Doom 3 to load the mod data and initialze the mod. For later releases it is planned to create a total conversion, which means that we will provide menu screens for all the various settings to be done in a consistant style fitting to the The Dark Mod universe. Since this is still under development, TDM maps have to be loaded via console commands using &quot;map &lt;mapname&gt;&quot;. For instructions on how to use the console please refer to the game manual or tutorials which can be found (insert link to general tutorial site).<br /> <br /> == Running the Mod ==<br /> <br /> Alterantively The Dark Mod can be initialized directly from the command line (or via an icon from the desktop) by using the commandline <br /> '''Windows:'''<br /> &quot;&lt;path to Doom 3&gt;/doom3.exe +set fs_game darkmod&quot;<br /> <br /> '''Linux:'''<br /> &quot;&lt;path to Doom 3&gt;/doom3 +set fs_game darkmod&quot;<br /> <br /> It is recommended to use this way of running The Dark Mod, as it appears that Doom 3 will handle paths more consistently then loading the mod manually.</div>

145.253.32.51