mirror of
https://github.com/acemod/ACE3.git
synced 2024-08-30 18:23:18 +00:00
1b12d37284
Hacking the BI respawn framework to support a spectator setting was intrusive and limiting. Instead of using a setting, I've opted to introduce a new respawn template that can be used within BI's respawn framework. The benefits of this approach are: - Compatibility isn't a concern, that responsibility is shifted onto mission designers. - Mission designers can use the functionality of the BI framework alongside the spectator system (combining templates, using different templates for different sides, etc.). - If a custom respawn framework is used, then this doesn't change anything. Custom frameworks are still fully supported via the public functions provided. - Remains simple to set up, just requires a description.ext edit
27 lines
887 B
C++
27 lines
887 B
C++
class ACE_Settings {
|
|
class GVAR(filterUnits) {
|
|
typeName = "SCALAR";
|
|
value = 1;
|
|
values[] = {CSTRING(units_none), CSTRING(units_players), CSTRING(units_all)};
|
|
};
|
|
class GVAR(filterSides) {
|
|
typeName = "SCALAR";
|
|
value = 0;
|
|
values[] = {CSTRING(sides_player), CSTRING(sides_friendly), CSTRING(sides_hostile), CSTRING(sides_all)};
|
|
};
|
|
class GVAR(restrictModes) {
|
|
typeName = "SCALAR";
|
|
value = 0;
|
|
values[] = {CSTRING(modes_all), CSTRING(modes_unit), CSTRING(modes_free), CSTRING(modes_internal), CSTRING(modes_external)};
|
|
};
|
|
class GVAR(restrictVisions) {
|
|
typeName = "SCALAR";
|
|
value = 0;
|
|
values[] = {CSTRING(modes_all), CSTRING(visions_nv), CSTRING(visions_ti), "$STR_Special_None"};
|
|
};
|
|
class GVAR(unitIcons) {
|
|
typeName = "BOOL";
|
|
value = 1;
|
|
};
|
|
};
|