Pylon loadout extension/restriction server side?

[Mirknir]

Hello fellow mission builders,

 

In my mission I am trying to change the weapon restrictions for some planes like adding SAB100 to su33 or AIM9X to F15.

 

So, I know how to do this on my client using the typical pylon editing in the corresponding luas

BUT I would like those changes to be carried in the mission and thus on the server I am hosting so people don't have to do this locally.

 

For this, I tried to include the corresponding luas in the mission and it didn't work :(

Su‐33.lua .lua 2.1 ... ... ..... 2B0... Scripts\Database\Planes\Su‐33.lua

Su‐27.lua .lua 2.2 ... ... ..... FD6... Scripts\Database\Planes\Su‐27.lua

F‐15C.lua .lua 1.6 ... ... ..... 7385... Scripts\Database\Planes\F‐15C.lua

I think I've played on a server allowing more weapons on the F15 at some point so it must be possible.

 

Is there actually a way to do that?

Anyone has an idea?

 

Thanks

[FSFIan]

I think I've played on a server allowing more weapons on the F15 at some point so it must be possible.

 

Is there actually a way to do that?

 

Have you tried doing the same thing to the server (i.e. editing the files in the server's DCS installation)?

[Mirknir]

I tried but it's not working either or it's not enough :(

[ThePutzer]

Simple work around

 

You can open up the Air Port, and uncheck the unlimited box. Then set the air 2 air weapon from, 100 to 0. You can export your new settings to other air ports also. Noodle around on that page..These old timers can give you more specifics if you need.. Just a thought. Hope it helps..

ThePutzer

[xcom]

AFAIK, you will always need to change this locally.

This means that you should do the following -

1. Create the same changes on the server side.

2. Create a mod pack for all users that are joining the server.

3. add the relevant folders in the integrity check with the server, this will ensure that anyone who joins, actually has the change in effect.

[Frostie]

Have you tried making the changes to the scripts/planes/[plane type] to suit which weapon you need then adding the weapons to the planes in the mission editor.

 

 

eg.

 

add AIM-54 to A-10A

Added at the bottom of the pylon list

 

 

 
pylon(1, 0, -0.615000, -0.016000, -6.365000,
{
FiZ = -4.0,
},
{
{ CLSID = "{DB434044-F5D0-4F1F-9BA9-B73027E18DD3}" }, -- AIM-9Mx2
{ CLSID = "{LAU-105_1*AIM-9M_L}" }, -- AIM-9Mx1
{ CLSID = "{LAU-105_1*CATM-9M_L}" }, -- CATM-9M
{ CLSID = "{3C0745ED-8B0B-42eb-B907-5BD5C1717447}" }, -- AIM-9Px2
{ CLSID = "{6D21ECEA-F85B-4E8D-9D51-31DC9B8AA4EF}" }, -- ALQ-131
{ CLSID = "ALQ_184" }, -- ALQ-184 
{ CLSID = "{A4BCC903-06C8-47bb-9937-A30FEDB4E741}" }, -- Red-Smoke
{ CLSID = "{A4BCC903-06C8-47bb-9937-A30FEDB4E742}" }, -- Green-Smoke
{ CLSID = "{A4BCC903-06C8-47bb-9937-A30FEDB4E743}" }, -- Blue-Smoke
{ CLSID = "{A4BCC903-06C8-47bb-9937-A30FEDB4E744}" }, -- White-Smoke
{ CLSID = "{A4BCC903-06C8-47bb-9937-A30FEDB4E745}" }, -- Yellow-Smoke
{ CLSID = "{A4BCC903-06C8-47bb-9937-A30FEDB4E746}" }, -- Orange-Smoke
{ CLSID = "{Mk82AIR}" },
{ CLSID = "{CBU-87}" },
{ CLSID = "{BDU-50LD}" }, -- BDU-50LD
{ CLSID = "{BDU-50HD}" }, -- BDU-50HD
{ CLSID = "{5335D97A-35A5-4643-9D9B-026C75961E52}" }, -- CBU-97
{ CLSID = "{BCE4E030-38E9-423E-98ED-24BE3DA87C32}" }, -- Mk-82
{ CLSID = "{7575BA0B-7294-4844-857B-031A144B2595}" }, -- AIM-54
}

you'd need to do this to the relevant pylons then add them on to the planes in your mission.