Difference between revisions of "Arma 3: Curator"

From Bohemia Interactive Community
Jump to navigation Jump to search
m
m
Line 27: Line 27:
 
* Input (3 classes): <code>["B_Soldier_f", "B_MRAP_01_F", "ModuleLightning_F"]</code>
 
* Input (3 classes): <code>["B_Soldier_f", "B_MRAP_01_F", "ModuleLightning_F"]</code>
 
* Output (3 arrays with settings): <code>[[true,0.1], [true,0.5,0.6], [false,0,0]]</code>
 
* Output (3 arrays with settings): <code>[[true,0.1], [true,0.5,0.6], [false,0,0]]</code>
 +
  
 
Every item in the array is in the following format:
 
Every item in the array is in the following format:

Revision as of 18:46, 17 February 2014

arma3 curator eye.png

Curator is a technical name for Arma 3 Zeus game master system. Every involved scripting command, event handler or class name contains the name. The reason for it is to have a generic name which can be passed from project to project without any associations.

Setup

The central piece of every curator is Game Master module, otherwise referred to as Curator Logic. It stores every setting, like editing areas, available objects or their costs.

You can find the module in Modules (F7) > Zeus > Game Master

In module arguments, can set the curator unit (either specific unit, player with given UID or server admin) and that's all you need to add game master to your mission. Without any further settings, all objects will be available for free and whole map will be editable.

In every examples on this page, we'll call the module myCurator.

Costs

Detailed Explanation

You can assign individual cost for every object in the game using CuratorObjectRegistered event handler.

myCurator addEventHandler ["CuratorObjectRegistered",{...code here, see below...}];

Arguments passed into the handler are:

Expected returned value is an Array of Arrays of the same size as the input array, with each item belonging to a class with the same array index. Missing or incorrect values will be replaced by default [true,0,0].

  • Input: [string1, string2, string3, ... classN]
  • Output: [array1, array2, array3, ... arrayN]

Example:

  • Input (3 classes): ["B_Soldier_f", "B_MRAP_01_F", "ModuleLightning_F"]
  • Output (3 arrays with settings): [[true,0.1], [true,0.5,0.6], [false,0,0]]


Every item in the array is in the following format:

[show, cost, (costWithCrew)]
  • show: Boolean - true to let the object appear in the CREATE list, false to hide it (costs will still be accepted if an object of the type is already present in the mission and made editable)
  • cost: Number - cost of the object
  • costWithCrew (Optional): Number - cost of the object with crew in it (affects only vehicles). When undefined, normal cost is used.

Example of the whole event handler:

myCurator addEventHandler [
	"CuratorObjectRegistered",
	{
		_classes = _this select 1;
		_costs = [];
		{
			_cost = if (_x isKindOf "Man") then {[true,0.1]} else {[false,0]}; // Show only objects of type "Man", hide everything else
			_costs = _costs + [_cost];
		} forEach _classes; // Go through all classes and assign cost for each of them
		_costs
	}
];

Functions

Alternatively, you can use scripting functions which will simplify cost settings:

Unlocking Objects

Editable Objects

Editing Areas

Camera Areas