Weapon Pylon Mods in 1.1

[169th_DedCat]

This happened on one of our squad member's computer while he was hosting, see screenshot below.

 

The mission was not classified, however even then I thought the client was supposed to be force fed the servers weapon pylon config LUA in 1.1 so they couldn't use completely bogus payloads like this on anything but their own PC. Am I wrong, or has someone already found a way around the server pushed pylon configs?

[Quirkitized]

It will only force the loadouts if the server mission is classified. It's a shame really, I have to do that for all my missions because of the 3 or 4 assholes running around putting 50 IR mavericks on there a10s.

[Force_Feedback]

It will only force the loadouts if the server mission is classified. It's a shame really, I have to do that for all my missions because of the 3 or 4 assholes running around putting 50 IR mavericks on there a10s.

 

AFAIK, the maximum number of pylons lomac supports is 12, after 12 it does doo-doo-wa-ha (no hud etc).

 

So, 12*3=36 mavs, nowhere near 50.

 

lol, what's the use of putting 36 mavs on a a10, you'd get a flying brick, dum cheators

[britgliderpilot]

So, 12*3=36 mavs, nowhere near 50.

 

Close enough, given artistic licence ;)

[Quirkitized]

AFAIK, the maximum number of pylons lomac supports is 12, after 12 it does doo-doo-wa-ha (no hud etc).

 

So, 12*3=36 mavs, nowhere near 50.

 

lol, what's the use of putting 36 mavs on a a10, you'd get a flying brick, dum cheators

 

I was begin sarcastic ;). But yes, I know what your saying....

[LawnDart]

It will only force the loadouts if the server mission is classified.

 

What do you mean by making it classified?

 

Although we don't use weapons, there's nothing limiting anyone from joining and arming our Thunberbird jets with heat seakers whenever we host tryouts. It would be nice to "lock" our loadouts as empty for clients if at all possible...

 

LawnDart

[169th_DedCat]

It would be nice to "lock" our loadouts as empty for clients if at all possible...

 

When you classify a multiplayer mission in 1.1 (In the top menu bar in the mission editor: Edit -> Classify -> Set a password) changes cannot be made by clients to their skin, aircraft #, or payload. They may only use the default one you specified in your mission.

[169th_DedCat]

It will only force the loadouts if the server mission is classified.

 

That's really a shame. I knew classifying the mission locked the client into the default payload, but I had thought that ED had set 1.1 up so that when a client joins an unclassified mission, their payload selection is still limited to the weapons available in the server's own weapon pylon configuration, so that they may create their own payload but are limited to the weapons available on that aircraft in the server's pylon config file. I guess it's all still locally configured.

 

Looks like the only way to prevent LOPE cheaters is to lock the client into a single payload. :frown:

[Quirkitized]

Yeah, and another thing that bites about it.... whatever options you have for the *main menu*, it will stick to that mission.

 

Example: Lets say you go to play coop with a few buddies, externals on, map view, show enemies, have some fun, etc. But then you load up your classified mission and when you classified it, externals were off, map view, etc....now you have to exit out, un-classify it, turn those options on again, and then re-classify it.

 

It's a PITA....main menu options for the overall game should not have any effect on a single mission. There should be some option for that...

[169th_DedCat]

I don't mind that feature at all Quirk. It allows you to easily set different parameters for the different missions you create instead of always having to remember to adjust them before the game.

 

Should you want to change them while hosing you don't have to quit the server session. Before you launch them game (when clients are connecting and choosing teams), simply use the declassify password, go into options and set them as you wish. You do NOT need to re-classify it, save it, or disconnect clients. The mission will remain classified with the new options you set for your clients.

[Quirkitized]

I don't mind that feature at all Quirk. It allows you to easily set different parameters for the different missions you create instead of always having to remember to adjust them before the game.

 

Should you want to change them while hosing you don't have to quit the server session. Before you launch them game (when clients are connecting and choosing teams), simply use the declassify password, go into options and set them as you wish. You do NOT need to re-classify it, save it, or disconnect clients. The mission will remain classified with the new options you set for your clients.

 

rgr :D