DeployableToolbox
Related Docs:
object DeployableToolbox
| package avatar
Determine if the given deployable can be managed by this toolbox.
Determine if the given deployable can be managed by this toolbox.
the deployable
true, if it can be managed under the current conditions;
false, otherwise
Contains
Available
Valid
Manage the provided deployable.
Although proper testing should be performed prior to attempting to add the deployable to this toolbox,
three tests are administered to determine whether space is available prior to insertion.
Manage the provided deployable.
Although proper testing should be performed prior to attempting to add the deployable to this toolbox,
three tests are administered to determine whether space is available prior to insertion.
The first two tests check for available space in the category count and in the unit count
and the third test checks whether the deployable is already being managed by this toolbox.
No changes should occur if the deployable is not properly added.
the deployable
true, if the deployable is added;
false, otherwise
Change the count of deployable units that can be tracked by providing a new certification.
Change the count of deployable units that can be tracked by providing a new certification. If the given certification is already factored into the quantities, no changes will occur.
the new certification
the group of previous certifications being tracked; occasionally, important former certification values are required for additional configuration; the new certification should already have been added to this group
Determine if the given deployable can be managed by this toolbox by testing if the specific deployable list and the deployable category list have available slots.
Determine if the given deployable can be managed by this toolbox by testing if the specific deployable list and the deployable category list have available slots. In this case, a "slot" is merely the difference between the current count is less than the maximum count.
the deployable
true, if the deployable can be added to the support lists and counted;
false, otherwise
Reference all managed deployables in the same category.
Reference all managed deployables in the same category.
the type of deployable
a list of globally unique identifiers that should be valid for the current zone
Reference all managed deployables in the same category as an example deployable.
Reference all managed deployables in the same category as an example deployable.
the example deployable
a list of globally unique identifiers that should be valid for the current zone
Remove all managed deployables.
Remove all managed deployables.
a list of globally unique identifiers that should be valid for the current zone
Remove all managed deployables that belong to the same category.
Remove all managed deployables that belong to the same category.
the deployable type belonging to a category
a list of globally unique identifiers that should be valid for the current zone
Remove all managed deployables that are the same type.
Remove all managed deployables that are the same type.
the deployable type
a list of globally unique identifiers that should be valid for the current zone
Check if this deployable is already being managed by the toolbox by determining whether or not it is already being managed by this toolbox.
Check if this deployable is already being managed by the toolbox by determining whether or not it is already being managed by this toolbox.
the deployable
true, if the deployable can be found in one of the lists;
false, otherwise
Check the current capacity for the same category of deployable as the example.
Check the current capacity for the same category of deployable as the example.
the example deployable
the current quantity of deployables and the maximum number
Check the current capacity for the same type of deployable as the example.
Check the current capacity for the same type of deployable as the example.
the example deployable
the current quantity of deployables and the maximum number
Reference all managed deployables of the same type.
Reference all managed deployables of the same type.
the type of deployable
a list of globally unique identifiers that should be valid for the current zone
Reference all managed deployables of the same type as an example deployable.
Reference all managed deployables of the same type as an example deployable.
the example deployable
a list of globally unique identifiers that should be valid for the current zone
Remove the first managed deployable from a category.
Remove the first managed deployable from a category. The only test performed is whether there is any valid deployable managed for the category.
the target category
any deployable that is found
Remove the first managed deployable that satisfies a test and belongs to the same category as the example.
Remove the first managed deployable that satisfies a test and belongs to the same category as the example. The test in question is used to pinpoint the first qualifying deployable; but, if the test fails to find any valid targets, the first deployable in the list of managed deployables for that category is selected to be removed. The only test performed is whether there is any valid deployable managed for the category.
the example deployable
the testing rule for determining a valid deployable
any deployable that is found
Remove the first managed deployable that matches the same type of deployable as the example.
Remove the first managed deployable that matches the same type of deployable as the example. The explicit tests is defined to find the first deployable whose type matches.
the example deployable
any deployable that is found
Set up the initial deployable counts by providing certification values to be used in category and unit selection.
Set up the initial deployable counts by providing certification values to be used in category and unit selection.
a group of certifications for the initial values
true, if this is the first time and actual "initialization" is performed;
false, otherwise
Stop managing the provided deployable.
Although proper testing should be performed prior to attempting to remove the deployable to this toolbox,
a single test is administered to determine whether the removal can take place.
Stop managing the provided deployable.
Although proper testing should be performed prior to attempting to remove the deployable to this toolbox,
a single test is administered to determine whether the removal can take place.
If the deployable is found to currently being managed by this toolbox, then it is properly removed.
No changes should occur if the deployable is not properly removed.
the deployable
true, if the deployable is added;
false, otherwise
Change the count of deployable units that can be tracked by designating a certification whose deployables will be removed.
Change the count of deployable units that can be tracked by designating a certification whose deployables will be removed. If the given certification is already factored out of the quantities, no changes will occur.
the old certification
the group of previous certifications being tracked; occasionally, important former certification values are required for additional configuration; the new certification should already have been excluded from this group
Determine if the given deployable can be managed by this toolbox by testing if the specific deployable maximum and the deployable category maximum is non-zero
Determine if the given deployable can be managed by this toolbox by testing if the specific deployable maximum and the deployable category maximum is non-zero
the deployable
true, if both category maximum and deployable type maximum are positive non-zero integers;
false, otherwise
A class that keeps track - "manages" - deployables that are owned by the avatar.
Deployables belong to the Engineering certification line of certifications.
CombatEngineeringand above certifications include permissions for different types of deployables, and one unique type of deployable is available through theGroundSupportand one that also requiresAdvancedHacking. (They are collectively called "ce" for that reason.) Not only does the level of certification change the maximum number of deployables that can be managed by type but it also influences the maximum number of deployables that can be managed by category. Individual deployables are counted by type and category individually in special data structures to avoid having to probe the primary list of deployable references whenever a question of quantity is asked. As deployables are added and removed, and tracked certifications are added and removed, these structures are updated to reflect proper count.