Making objects non-interactable

[chronicsilence 12]

I have an object that I would like to make non-interactable. It's a light source (specifically the construction cone with light), and I need to keep it so that the light still works (i.e. enableSimulation false is not an option) but it can't be moved or destroyed. If you put the allowDamage false on it, the light still stops blinking if you shoot it and it can still get knocked over.

I also need to make sure that it doesn't become a rigid structure that things can hit. What I really need is a way to just make everything, including bullets and grenade shockwaves, go through it. Is there any command to do such a thing, that won't have a horrendous performance impact?

[iceman77 18]

I'm sure there's some witty command / way out there. In the mean time, you could always store the position of the cone. If it's moved from the position or "hit" by a projectile such as a bullet, have it either delete the cone and create a new one at the correct position, or have it reposition the cone back into the correct spot. disableCollisionWith command may also come in handy. Though idk if it will work with a road cone.

[f2k sel 164]

this addEventHandler ["handledamage",{0}]

[iceman77 18]

The cone still gets knocked over though with the handleDamage EH. Unless I'm missing the point of the OP. I think he wants the cone to not be able to be knocked over.

---------- Post added at 14:30 ---------- Previous post was at 14:28 ----------

In any case, I may as well post my most shitty work around.

cone init:

_nul = [this] execVM "cone.sqf";

cone.sqf

_rc = _this select 0;
_rcPos = getPosATL _rc;

while {true} do {
   waitUntil {_rc distance _rcPos > 0};
   deleteVehicle _rc;
_rc = createVehicle ["RoadCone_F", _rcPos, [], 0, "CAN_COLLIDE"]; 
sleep 1;
};

---------- Post added at 14:42 ---------- Previous post was at 14:30 ----------

Or maybe you can make clever use of the HIT eventHandler. Whenever the object is hit by a projectile, move it back into position and set it's vector (incase it was knocked down). Though I don't believe getting runover counts as getting "hit"? Not sure. Or you could have a global cone cleanup loop. Which would automatically delete all cones and create new ones at their positions once every <insert time here>

Edited December 8, 2013 by Iceman77

[das attorney 857]

Try this:

Call your cone: cone1

cone1 enableSimulation false;

Then run this script:

_pos = getPosATL cone1;

while {true} do
{
_light = "#lightpoint" createVehicle _pos;
_light setLightBrightness 0.7;
_light setLightAmbient[0.001, 0.0007, 0];
_light setLightColor[1, 0.7, 0];
_light lightAttachObject [cone1, [0,0,0.24]];
_light setLightFlareMaxDistance 400;
_light setLightDayLight false;
_light setLightIntensity 1000;
_light setLightUseFlare true;
_light setLightAttenuation [0, 1, 1, 1];
sleep 1;
deleteVehicle _light;
sleep 1;
};

It's not exactly the same, but it's pretty close. You can play with the numbers to suit your taste.

Your cone should now be a ghost, but still emitting light!

[f2k sel 164]

I miss read that bit.

this addEventHandler ["handledamage",{(_this select 0)  setCenterOfMass [[0,0,-0.4],3],0}]; // self righting cone

or

gl being the name of a game logic placed somewhere on the map

this addEventHandler ["handledamage",{0}];
this attachto [gl];

[Tankbuster 1733]

Attachto the cone to an invisible helipad.

[das attorney 857]

Attachto the cone to an invisible helipad.

Nice and simple - like it :)

EDIT: It's funny seeing all the different ways of thinking coming up with 9 ways to skin a cat :)

[iceman77 18]

Attachto the cone to an invisible helipad.

brilliant lol

---------- Post added at 15:06 ---------- Previous post was at 14:57 ----------

this addEventHandler ["handledamage",{(_this select 0) setCenterOfMass [[0,0,-0.4],3],0}]; // self righting cone

Ahh that's really clever. Nice one.

@ the OP - Either one of these suggestions is better than what Das and I suggested IMO. Less loops = good.

Edited December 9, 2013 by Iceman77

[chronicsilence 12]

Attachto the cone to an invisible helipad.

That sounds interesting. How do I create an invisible helipad though, and attach something to it?

[toxicsludge 12]

That sounds interesting. How do I create an invisible helipad though, and attach something to it?

The helipad is an object, much like an ammobox. I have no idea on how to use 'attachTo', tho, try here: http://community.bistudio.com/wiki/attachTo

[fusion13 11]

AttachAttachti is cone attachTo [heli, pos]; I believe that is it anyway and invisible heli I don't know.

[f2k sel 164]

Use of attachto is in post six, the heli pad is in the editor under signs. I used a game logic myself but the result is the same.

You don't need the position for this sort of attach the object will remain in place. you can attach multiple objects to the same logic or heli pad.

multiple attach method c1 refers to the name you give each cone.

my_pad would be the name you give the pad

{_x addEventHandler ["handledamage",{0}];_x attachto [my_pad]} foreach [c1,c2,c3,c4,c5,c6];

If you still want then to remain working when shot I think you will still need the eventhandler.

If you have more than a few cones you would be better using nearest objects to find them

I don't have the actual road cone type at hand but when you place a cone you should see the name in the top right of the smaller editor.

Just repace xxxxx with the correct name.

{
_x addEventHandler ["handledamage",{0}];
 _x attachto [my_pad]
 } foreach (nearestobjects [my_pad,["xxxxxxxxxx"],100] );

that should find all cones within 100 meters of the pad or game logic.

Edited December 10, 2013 by F2k Sel