Classes:CustomInventory

From ZDoom Wiki
(Redirected from CustomInventory)
Jump to: navigation, search
Note: Wait! Stop! Before you copy this actor's definition into your mod, remember the following things:
  1. You do not need to copy that actor, since it is already defined.
  2. In fact, it's not just useless, it's actually harmful as it can cause problems.
  3. If you want to modify it, or use a modified version, using inheritance is the way to go.
  4. The actor definitions here are put on the wiki for reference purpose only. Learn from them, don't copy them.
  5. There is only one exception: if what you want is changing Ammo capacity, you need to create a new type from Ammo.
Custom inventory
Actor type Internal Game MiniZDoomLogoIcon.png
DoomEd Number None Class Name CustomInventory


Classes: InventoryCustomInventory
 →ArtiBoostMana
 →ArtiEgg
 →ArtiPork
 →Berserk
 →Mana3
 →Megasphere

CustomInventory items are special items that allow some very primitive scripted functionality using its states. The base class CustomInventory is never used directly. It is always the base class for items defined in DECORATE.

DECORATE definition

ACTOR CustomInventory : Inventory native {}

Using in DECORATE

CustomInventory only uses the basic Inventory properties, but defines 3 new states:

  • Pickup.
  • Use.
  • Drop.
Ktip.png Tip: Players, Monsters and pretty much everything else can obtain a CustomInventory and be affected by its Pickup state. Inventory items can also receive CustomInventory items to execute behaviors, given by ACS or DECORATE (by DECORATE is (development version b4f05ee only)).

The behavior is as follows:

  • All code pointers in the Pickup state sequence are called when the item is being picked up. The sequence is successful when the last called function in the state doesn't return failure explicitly; you can also use ACS_ExecuteWithResult to set the result from ACS. Success can be overridden by terminating the state sequence with fail instead of stop.
Ktip.png Tip: Jumping functions always set success to false.
  • If the Pickup sequence returns successfully the behavior depends on the presence of the Use state:
    • If there is no Use state the item will be removed from the map and not be placed in the actor's inventory.
    • If there is a Use state the item will be placed in the actor's inventory.
  • If the item has a Use state and is being used by the player the Use state sequence is called. Failure or success are determined the same way as for the Pickup state. If the sequence returns successfully the item is removed from the inventory. Note that due to this special behavior, the Use and Pickup states will ignore all frame durations and shouldn't be looped, attempts to do to so may result in the sequence being interrupted by the engine; every frame will execute within the same tic.
  • If the item is being dropped by a monster the Drop state sequence will be executed and the item will never be spawned. This is mostly there for special actions that can be taken by Strife conversation scripts. For regular monster death actions there are better and more flexible way to achieve the same.

Notes:

  • State jumps should use an actual string instead of an offset number to perform the jump to guarantee it does what it's supposed to do for the Use state.
  • To make an item that's able to be picked up with conditions (excluding the Inventory.MaxAmount property), the inventory item will have to perform a function such as A_RailWait last in the state, especially after jump functions. The +INVENTORY.ALWAYSPICKUP flag should not be used in this case, because even if the sequence fails, the item will still disappear. Instead, after all conditions are met, you should perform a function akin to the described above to signify success.
  • CustomInventory items can modify the picking actor's user variables but some conditions apply:
    • Pickup or Use states both work.
    • If the item is solely developed for A_GiveInventory functionality and similar only, defining the user variable first is not needed. Only the receiver needs it defined.
    • If the receiver does not have the variable defined, it will log a console message notifying the player it does not exist.
    • User defined variables on inventory items will only affect the item itself until picked up; everything afterwards affects only the receiver. As such, if the actor is missing the variable used by CustomInventory, it will also log a message about missing user variables.
  • A jump to the Use state will NOT be treated the same as the actor actually activating it. For this, the +INVENTORY.AUTOACTIVATE flag must be present if it's for anything non-player related.
  • CustomInventory items cannot be used to "fetch" variables directly. They can perform jumps based upon the current actor's variables that are defined, and execute DECORATE action functions and ACS scripts accordingly, and they can modify that actor's variables in particular, but nothing else. Once used, the CustomInventory item loses access to its variables, gaining direct access to the owner's variables instead.

Examples

actor BigBoost : CustomInventory 10492
{
  Inventory.PickupMessage "Energy Boost!!!"
  Inventory.PickupSound "misc/p_pkup"
  +COUNTITEM
  states
  {
  Spawn:
    AWI3 A -1
    stop
  Pickup:
    TNT1 A 0 A_GiveInventory ("Soulsphere", 2)
    TNT1 A 0 A_GiveInventory ("BFG9000")
    stop
  }
}