btmux-0.6-rc4/doc/
btmux-0.6-rc4/event/
btmux-0.6-rc4/game/
btmux-0.6-rc4/game/maps/
btmux-0.6-rc4/game/mechs/
btmux-0.6-rc4/game/text/help/
btmux-0.6-rc4/game/text/help/cat_faction/
btmux-0.6-rc4/game/text/help/cat_inform/
btmux-0.6-rc4/game/text/help/cat_misc/
btmux-0.6-rc4/game/text/help/cat_mux/
btmux-0.6-rc4/game/text/help/cat_mux/cat_commands/
btmux-0.6-rc4/game/text/help/cat_mux/cat_functions/
btmux-0.6-rc4/game/text/help/cat_templates/
btmux-0.6-rc4/game/text/wizhelp/
btmux-0.6-rc4/include/
btmux-0.6-rc4/misc/
btmux-0.6-rc4/python/
btmux-0.6-rc4/src/hcode/btech/
btmux-0.6-rc4/tree/
& btcritstatus()
 
  Syntax: btcritstatus(<UnitDB>,<location>)
 
  This function returns a string displaying the status of the 
  criticals in <location> on <UnitDB>
 
  The string returned is formatted" 
  <critslot>|<?>|<partname>|<operational>|<crittype>
	
	Note: The element denoted <?> is used for the brand of partnames, 
	however brands are not implemented on this codebase, so will return 
	empty
 
  <operational> returns 0 if the <critslot> is functional, -1 if the 
  part at <critslot> is destroyed
 
  <crittype> returns a value indicating the type of item stored at 
  that <critslot>
 
  * 1 = Weapon
  * 2 = Ammo
  * 3 = Actuator
  * 4 = Cargo
  * 5 = Empty
  * 0 = Other (eg Cockpit, LifeSupport) 
 
	Note: if <critslot> refers to a location where missiles are stored, <crittype> 
	will return 4, indicating a cargo crittype
 
 Continued in btcritstatus()2