LUA Request for Devs

[GGTharos]

Just realized that with the ability to export all objects positions via LUA someone could use it to cheat by circumventing the difficulty settings for showing objects on the map.

 

Would it be possible to apply server-enforced settings on LUA exports and -perhaps- some sort of authorization protocol which would allow a client with the correct password export all objects?

 

Oh and for the future..separate red/blue side briefings and maps? Pretty please? :D

 

As well as red/blue pass so that teams can't see each other's maps.

[Dmut]

Hello GGTharos

Valery have told us, that all LUA import\export thing can be optionally restricted on server, so if everyone want to fly in the same conditions - server will limit import\export usage on clients. But, of course, limitations like these will affect pilots who flying in cockpit with instruments, based on LUA import\export.

[GGTharos]

If imports/exports can be -selectively- allowed/denied then pilots flying with instruments will be ok. The main thing is to avoid export of all objects on the map.

 

Thank you for the answer though, this is good news.

[Dmut]

since I don't know how flexible those limitations could be, we can wait for v1.1 release or rather ask a betas to post a quotes from config-files (not sure if they allowed to)

[GGTharos]

Undertood. I'm patient :)

[Valery Blazhnov]

If imports/exports can be -selectively- allowed/denied then pilots flying with instruments will be ok. The main thing is to avoid export of all objects on the map.

 

Thank you for the answer though, this is good news.

The server administrator can edit Export.lua and so he can allow/deny some export features.

[GGTharos]

Cool!

[nightowl]

Hello eveybody,

 

Just two remarks concerning the control of the exposed lua functions through the server edit:

 

- While I think that this is a good solution, it is however a bit technical and error prone for a number of users. This effect could, however, be minimised by proposing default configurations. Good.

 

- In the case of the Awacs project, you may have heard of and seen some screens here, I think that there is a difficulty due to the granularity of the control on the functions. Valery, tell me if I am wrong, but what I understood is that the server user can edit the export.lua file to disable functions. If he does this on a global level, then we can say good bye to the AWACS mod, as the AWACS needs the data given by the functions.....which allow cheating !!!

 

I hope that I am wrong and that function usage can be disabled from the server but on client basis.

[GGTharos]

If it can't be, I'm sure they'll work something out - for example, it would make sense to allow by default, the server to export anything it wants, but force files to the client to shut off unwanted capabilities.

[nightowl]

Hi,

 

Yes exactly. However in that case only the server could "serve" data to the AWACS, which removes the capability for a client to be AWACS unless there is a net connection from the server to the AWACS software.

 

Anyway, it does not matter. We just need to have fun...with the guys we trust !

[GGTharos]

Yep, that's the idea. And while I trust a lot of people, sadly I catch folks on the 44th server with edited payloads every day.

[Phil_C6]

Hi men

Yep, that's the idea. And while I trust a lot of people, sadly I catch folks on the 44th server with edited payloads every day.

 

It could be really fine to have the possibility to blocked playload in the mission editor.

 

And to decide at the start of the mission how many times each pilots could recover. (create a reserve of planes, missiles, fuel....)

 

I have many others suggestions for the editor, maybe could you export other parameters for these ideas

 

 

Sorry for my bad english

 

Good night @+

[GGTharos]

You cna block payloads for MP missions but it must be done through LUA on the server.

[nightowl]

Hi,

 

You cna block payloads for MP missions but it must be done through LUA on the server.

 

Can you elaborate on this, as I haven't seen such things in the lua exposed functions list posted on the web site !!!

 

For what I understood, I should say guessed, most of the functions are geared toward local client usage like for a cockpit with data replication screens (all the LoGetxxxx functions) and switch for input (see Input section of export.lua on web site). Note that only two can accept arguments in input:

 

LoGetObjectById() -- (args - 1 (number), results - 1 (table))

LoGetNameByType () -- args 4 (number : level1,level2,level3,level4), result string

 

Few of these functions are more global and can be used in the case of the AWACS project:

LoGetObjectById()

LoGetWorldObjects()

 

Other functions do not take arguments in input to specify the Object on which we would need to apply the function. Example, how could an external application, like the AWACS one, get the routes of all flights ?

It cannot with the current function set.

 

So how could the server check the payload of a plane through currently exposed Lua functions ? Moreover, restrict it through Lua exposed functions ? May be I missed something here as unless the server and the clients exchange signatures of the meinit.xml file, I do not see how we could have restrictions on payload editing.

 

So unless there is a network connection, in parallel of the lockon built-in client/server one, between the Lo clients, the Lo server and an external application, there not much one can do.

Unfortunately an external application will not benefit from the fact that there is already a Lo builtin connection between the clients and the server ! The ideal situation would be where all the clients could use the Lua exposed function locally, to take an example for a cockpit or instrument replication, and external global applications, like the AWACS project, would use only the server output capabilities...because the server knows anyway everything about the clients...

[GGTharos]

The devs implemented a numebr of server-side files which are *pushed* to the client and override the client's own MEinit etc files (AFAIK)

 

These files have interesting names like WeaponPylon.lua and so on and so on ;) Essentially you can use those files to force the desired configurationon part of the client when it connects to your server.

 

Unfortunately, since I'm not on the beta team, I can't offer more details.