Search the Community

PLEASE I am searching how to respawn with a choice of classes, for example when the player die he can choose one of the multiple classes (Sniper, Rifleman ..) But the problem is that I can't make a choice I have just the sniper... Sorry for my English I am french :/ I hope that my screens are going to better explain my problem ^^

I want to have a box where players can come up, and select a class from scroll wheel options, and it'll give them the gear immediately. I've seen it done, I just want to do it myself. Please reply if you know how. LTJG Hummel SEAL Team 10

Hello everyone, I have compiled a little list of base classes for CfgVehicles. so that these can be used in combination with isKindOf CfgVehicles Base I had created a pastebin to preserve a little more forum space.

I am trying to make an addon that will make a small hud appear as soon as you enter particular vehicle. I have made the hud itself via script using rsctext. I only need the code for the init.sqf so that: 1) playable unit enters mortar as gunner (only mortar no other vehicle) - script starts 2) playable unit exits mortar - script stops I need this to work with all mortars placed on the map for all playable units, without any naming etc. (of course each player must see the hud individually). Please advise if it is possible to do and the code to do it if possible. Thank you,

SQF Classes for ArmA 3 Edited - release updated with a couple of bugfixes - if you downloaded prior to 6pm GMT on 29 October then please re-download to get the corrected files. "If . . . [the] fact [that brutes abstract not] be made the distinguishing property of that sort of animal, I fear a great many of those that pass for men must be reckoned into their number." -- George Berkeley Many times when scripting in SQF it may occur that implementing object-oriented techniques can simplify or enhance certain abstractions. The technique of using getVariable/setVariable on a unit or gamelogic to store function code or references specific to that unit's situation is a common pattern found in many missions and modules. Here, that idea is taken one step farther: instead of storing functions on game objects, we store an array of class names (representing a chain of inheritance or a mixture of interfaces). Meanwhile, a master Classes array holds a subarray for each defined class, containing a function definition for each class method. With this arrangement and just a handful of primitive functions, an unlimited variety of classes and methods can be declared on-the-fly while a mission is running. Release (.zip): https://github.com/dwringer/a3system/releases/tag/v1.0 Code: http://github.com/dwringer/a3system/tree/master/ClassDemo.Tanoa This is a selection of modules drawn from a larger repository I keep at http://www.github.com/dwringer/a3system/. There, more recent versions of these modules can often be found. I also placed other modules I created over the years, which are of variable quality and may or may not be worth a look. Class layout Lambda Macros Example overview This will demonstrate how to create abstract instances and send messages (method calls) to them. The included example is a mission with four men (crew_1..crew_4) and two vehicles (car_1, car_2). You may easily duplicate it in a different map if you don't have Tanoa available. There is a single Radio Alpha trigger, upon whose activation the following scripts are executed: CG = ["CrewUnitGroup"] call fnc_new; [CG, "assign", crew_1, "driver"] call fnc_tell; [CG, "assign", crew_2, "gunner"] call fnc_tell; [CG, "assign", crew_3, "driver"] call fnc_tell; [CG, "assign", crew_4, "gunner"] call fnc_tell; [CG, "assign", car_1, "vehicle"] call fnc_tell; [CG, "assign", car_2, "vehicle"] call fnc_tell; [CG, "board_instant"] call fnc_tell; Here, fnc_new is how we create a new instance. It accepts the class name and any init parameters appended to it (here there are none). We could also put a Game Logic in the editor instead of using fnc_new, and in its init use the following: _nil = this spawn { waitUntil {not isNil "ClassesInitialized"}; [_this, "CrewUnitGroup"] call fnc_instance; .. rest of code .. }; The method calls are actually made with fnc_tell, which takes as parameters the class instance, method name, and subsequently each method parameter. Thus, all methods to all classes are defined and called using a standardized syntax and set of functions which have been precompiled. Since fnc_instance makes an instance out of an existing object, we can also use it for creating class inheritance. Consider the following: DEFCLASS("MySubClass") ["_self"] DO { [_self, "SuperClass"] call fnc_instance; .. rest of code .. _self } ENDCLASS; Now, MySubClass inherits all the methods from SuperClass. Each game object keeps an ordered list of its class assignments, so if a method is not found on MySubClass it will be looked up on SuperClass. I have provided the macros SUPER and SUPER_ARGS in include\classes.hpp to facilitate subclassing from within classdef header files. If you want to create a subclass method that implements a superclass method under a different name, that can be done by looking up the class alist in the Classes global alist and using the function contained there as a new method. In classdef files, this has a macro called ALIAS(subclass, subclass_method, superclass, superclass_method). Another example Without further ado, the link to the repository containing the above example mission folder and all required modules is: Release (.zip): https://github.com/dwringer/a3system/releases/tag/v1.0 Code: http://github.com/dwringer/a3system/tree/master/ClassDemo.Tanoa Good luck, and if anyone creates some useful classes or a cool class tree, I'd love to hear about it. Even if this just serves as an example of what can be done to (ab)use SQF, I am satisfied. "No point in mentioning these bats, I thought. Poor bastard will see them soon enough." -- Raoul Duke Edited - release updated with a couple of bugfixes - if you downloaded prior to 6pm GMT on 29 October then please redownload to get the corrected files. There were changes made to fnc_tell and fnc_filter related to nil values being passed as parameters. Edited - added another example section

The challenge: I decided to try and find a purpose for the Virtual Reality terrain! :lol: This is the first TvT scenario I've ever created and was looking to see what others thought. Steam Workshop download: http://steamcommunity.com/sharedfiles/filedetails/?id=719318132 and a direct .pbo download http://www.filedropper.com/sectorcontrolv4vr

Without going to much off topic I'll give a bit of background on why such question... I'm working on a clothes mod that creates new uniforms, helmets,etc. The scripts weren't much optimized and were pretty much copy+paste based. Worked but if I wanted to change a value of a type of vest then I had to change them all. So I started adapting the scripts to be based on inheritance so that all I had to change for the childs were textures. However I started to face some issues of many values not being inherited, particularly stats of uniforms which could be perhaps answered with the fact that some stats are present in subclasses which weren't declared in the children. However my vests children don't have subclasses declared and have the correct stats so I'm not sure. As I was doing some research looking for answers I've stumbled upon Macros which seems to be a replacement for my inheritance based system since it just copycats the parent and all I have to do is input the values into the parameters. Thus my question, which should have I used in the first place? May have I miswritten the inheritances? Or perhaps a mix of both? I haven't fixed the problem yet as I was looking for an answer on the best aproach towards the problem. It seems that backpacks, vests and helmets are working correctly but I'm not entirely sure since uniforms stats and some subclasses variables are missing/generating errors. This also brings me doubts wether or not Units are correcly setup despite at first glance they seem to have inherited correctly. Below I'll leave an example of my classes. (For the sake of simplicity for now I'll just take a segment from my vests. If it's due necessary later on I could post segments from the Units/Uniforms files.) //Also authors don't seem to inherit properly. (...) class cfgWeapons { class VestItem; class Vest_Camo_Base: ItemCore { class ItemInfo; }; #include "cfgVest.hpp" }; (...) class VEST_TAC_Desert: Vest_Camo_Base { author = "Example"; //vehicleClass = myVest; side = TWest; scope = 2; displayName = "TacticalVest Desert"; picture = "\A3\characters_f\Data\UI\icon_v_tacvest_blk_ca.paa"; model = "A3\Characters_F\Common\equip_tacticalvest.p3d"; hiddenSelections[] = {"Camo"}; hiddenSelectionsMaterials[] = {"A3\Characters_F\Common\Data\tacticalvest.rvmat"}; hiddenSelectionsTextures[] = {"forces\tex\vest\deserttactical.paa"}; class ItemInfo: VestItem { class HitpointsProtectionInfo { class Chest { HitpointName = "HitChest"; armor = 8; PassThrough = 0.3; }; class Diaphragm { HitpointName = "HitDiaphragm"; armor = 8; PassThrough = 0.3; }; class Abdomen { hitpointName = "HitAbdomen"; armor = 8; passThrough = 0.3; }; class Body { hitpointName = "HitBody"; passThrough = 0.3; }; }; uniformModel = "A3\Characters_F\Common\equip_tacticalvest.p3d"; containerClass = "Supply120"; mass = 80; hiddenSelections[] = {"camo"}; }; }; class VEST_TAC_WoodlandA: VEST_TAC_Desert { author = "Example"; displayName = "TacticalVest Woodland-A"; hiddenSelectionsTextures[] = {"forces\tex\vest\woodlandtactical.paa"}; };

Hi, Actually i'm working on a campaign. Everthing works pretty well so far, but was thinking to change current structure as I want to move some functions out of the mission folder in order that these can be used by other missions as well without copying them to every mission again. ... that's were the problem started... I tried several ways to achieve that but none of the methods i used seem to work... I am using the standard 'ShowOSD' function. For this, i have created a configfile: cfgFunktion.hpp in 'Campaigns\DM_BST\config' which contains the classes: (cfgFunktion.hpp is included in the description.ext of the current mission: #include "\Campaigns\DM_BST\config\cfgFunktion.hpp" class CfgFunctions { class DM{ class intel { class showOSD { file = "intel\fn_showOSD.sqf"; }; }; }; }; the function fn_showOSD.sqf (which is the standard function of Jiri Wainar) i have it in a subfolder within the the mission folder -> xHub01.Stratis\intel from a customer script (within the missionfolder), the function then gets called using [] spawn DM_fnc_showOSD; So far everthing works as it should! :D but.... when I try to put the function (fn_showOSD.sqf) outside of the missionfolder eg into: Campaigns\DM_BST\functions\intel\ and adopt the path in the cfgFunktion.hpp for the function showOSD to the new location, eg: class showOSD { file = "Campaigns\DM_BST\functions\intel\fn_showOSD.sqf"; }; when I launch the mission the showOSD function dosen't work. Also, what need to be considered when putting something outside of the current missionfolder within a campaign? would really appreciate to get some help here.... Boosterchen