Supply Drop script

[legio4777 12]

Hey Guys

I´m looking for a good supply drop...

Is there any good script?

Which one do you reccomend?

BR

[MulleDK19 21]

Depends on what you need. Actual plane/helicopter, or just an ammo crate spawning mid-air with a parachute.

[legio4777 12]

I would like ti be realistic a helo could be fine. Also if i can add any ammo box or VAS will be great

[[evo] dan 79]

Theres an editor module that can do this for you by the way.

[legio4777 12]

Dan;2630901']Theres an editor module that can do this for you by the way.

Yes I do know but I want it for MP. Does it work in MP and dedi server?

[[evo] dan 79]

Yes it does

[MILN4R 10]

No it doesn't. For every client connected to server it will drop a crate(not sure tho, not tested this theory), but here is a fact to back me up. On my server i call in supply drop, does it correctly and then drops 2 crates due to there being 2 clients? (me and the server). And the heli transport module wont work in MP correctly either. Artillery tho, works fine.

Well, iv been looking over. the code by BI and well simply put, it look like its not designed for MP. The more i think about it the more i think that its gonna not be a quick fix for me to do. I simply put am not good enough to do such a thing. I know you can do the whole class CfgCommunicationMenu thing to do supports and stuff, like they did in their showcase support mission. but the thing is it will still be linking to the A3\modules_f\supports\ stuff. which isn't made for MP. And i am almost certain that we can make it work. as copying the entire supports folder into mission directory, deleting the CfgCommunicationMenu.hpp, and patches thingy. then going through each file and making all the

_this execVM 'A3\modules_f\supports\<whatever its linking to>'

or basically anything that is

A3\modules_f\supports\

and changing it so its linking to your supports folder in mission directory, e.g in config.cpp

		class Eventhandlers
	{
		init = "_this execVM 'A3\modules_f\supports\init_requester.sqf'";
	};

to

		class Eventhandlers
	{
		init = "_this execVM 'supports\init_requester.sqf'";
	};

. And then adding #include "supports\Config.cpp" to your description.ext, obviously something goes wrong with it somewhere because the loading name of mission wont display, it shows as Unknown mission and in game the supports aren't displayed and under the comm menu they are listed as numbers, e.g. you've got 3 supports, they will display as 1,2,3 in order top to bottom. BUT that means it did over wright stuff SO. And the problems are probably in the code somewhere or in the deleted CfgCommunicationMenu.hpp, the reason that is deleted is that it causes game to crash due to

class CfgCommunicationMenu

being defined in config.cpp too.

But the fact that it over rights, means that the changes/ fixes to supports could be possible. I don't know how to make it so but i believe it is possible to do it. Im going to be playing around with it, to see if i can figure out how to make it work, but i have the distinct felling that this is way above my level of scripting, so this is why this is the first time im posting on the forum. And there is feedback trackers about these problems btw, which are very very old and were left unanswered, some where even closed so, yeah. And this isn't a very big priority to the DEV`s because the only real people who will report this stuff are actual mission makers, since they are the ones who encounter these problems.

Of course if it works for you then... i want to know everything you did. And i mean everything!

Another note is that the Config.cpp and cfgCommunicationMenu.hpp have alost the exact same parts, Config.cpp part for cfgCommunicationMenu

class CfgCommunicationMenu
{
class Default;
class ArtilleryBase;
class Support_Request_Artillery: ArtilleryBase
{
	expression = "player setVariable ['BIS_SUPP_request', ['Artillery', _pos]]";
};
class CASBase;
class Support_Request_CAS_Heli: CASBase
{
	text = "$STR_A3_mdl_supp_disp_cas_heli";
	expression = "player setVariable ['BIS_SUPP_request', ['CAS_Heli', _pos]]";
};
class Support_Request_CAS_Bombing: CASBase
{
	text = "$STR_A3_mdl_supp_disp_cas_bombing";
	expression = "player setVariable ['BIS_SUPP_request', ['CAS_Bombing', _pos]]";
};
class SupplyDropBase;
class Support_Request_Drop: SupplyDropBase
{
	expression = "player setVariable ['BIS_SUPP_request', ['Drop', _pos]]";
};
class TransportBase;
class Support_Request_Transport: TransportBase
{
	expression = "player setVariable ['BIS_SUPP_request', ['Transport', _pos]]";
};
class Support_Report_Done
{
	text = "$STR_A3_mdl_supp_comm_done";
	expression = "player setVariable ['BIS_SUPP_supporting', FALSE]; call BIS_SUPP_refreshMainWindow";
};
class Support_Report_Failed
{
	text = "STR_A3_mdl_supp_comm_failed";
	expression = "player setVariable ['BIS_SUPP_failed', TRUE]";
};
};

And cfgCommunicationMenu.hpp full file is.

class CfgCommunicationMenu
{
class Default;
class ArtilleryBase;
class Support_Request_Artillery: ArtilleryBase
{
	expression = "_this setVariable ['BIS_SUPP_request', ['Artillery', _pos]]";	
};

class CASBase;
class Support_Request_CAS_Heli: CASBase
{
	text = $STR_A3_mdl_supp_disp_cas_heli;
	expression = "_this setVariable ['BIS_SUPP_request', ['CAS_Heli', _pos]]";	
};

class Support_Request_CAS_Bombing: CASBase
{
	text = $STR_A3_mdl_supp_disp_cas_bombing;
	expression = "_this setVariable ['BIS_SUPP_request', ['CAS_Bombing', _pos]]";	
};

class SupplyDropBase;
class Support_Request_Drop: SupplyDropBase
{
	expression = "_this setVariable ['BIS_SUPP_request', ['Drop', _pos]]";	
};

class TransportBase;
class Support_Request_Transport: TransportBase
{
	expression = "_this setVariable ['BIS_SUPP_request', ['Transport', _pos]]";	
};

class Support_Report_Done
{
	text = $STR_A3_mdl_supp_comm_done;
	expression = "_this setVariable ['BIS_SUPP_supporting', FALSE]; call BIS_SUPP_refreshMainWindow";
};

class Support_Report_Failed
{
	text = STR_A3_mdl_supp_comm_failed;
	expression = "_this setVariable ['BIS_SUPP_failed', TRUE]";
};
};

As you can see the only difference is in the expressions, Config.cpp`s is "player" and the menu`s is "_this".

Note: Im on the DEV build, in the past supports were broken aon dev branch, and this may be the case here, but probably not. Also can`t be bothered to switch back to main as i like playing with Zues. And the difference between DEV and main is almost 1gig, also for quick reference for anyone who wants to quick switch between dev and main, when you want to go to dev make a backup of your game via steam backup feature, then switch to dev, download what it want then when your finished with dev make a backup of the Dev build, then load your main build backup, might still need a update if main received a update in the time that you were gone but yeah to be expected.

Wow quite the post... really need a show button for code up in this joint.

Edited February 25, 2014 by MILN4R
i felt more Information was required.

[legio4777 12]

Ok. Thanks...

So Im going up to my previous question..

There is any good script for the Supply Drop?

[MILN4R 10]

Lol, pretty much. Nope. I found a thread that looks promising but yet to hear a reply from the guy(i PM`d him since its quite old thread)

http://forums.bistudio.com/showthread.php?163949-Comms-menu-not-working-on-Dedi-Server

I dont have time to do what he is doing so, if you feel like trying it go ahead.

Edited February 27, 2014 by MILN4R