Case

My thoughts are with Striker.

MISSION START(Set Flag)//FLAG IS FALSE (1)//SET FLAG(1) && MESSAGE(Flag set,10) CONTINUOUS ACTION(Message)//TIME SINCE FLAG(1,15)//CLEAR FLAG(1) && MESSAGE(Message goes here,10) && SET FLAG(1) First trigger sets Flag 1. Second trigger continuously checks if it is true, waits 15 seconds, then resets it and prints out a message.

No, not by the looks of it.

If by host you mean the server, then yes, they can add any folder or file of which the integrity must be checked on each of the clients connecting to the server. The integrity check appears to do a checksum (MD5, SHA1).

I thought you were intelligent enough not to use a generalized and false statement like this. Since when did pilot skill and pilot error drop out of the equation predicting the outcome of a head to head engagement? Both are as important if not more important than what plane one flies or weapons one brings. Even you make mistakes, as you showed only a couple of days ago.

Happy Birthday! :holiday::drink::beer::cheer3nc::yay:

Don't worry, he's already making such a map.

Last time anyone checked, the laws of physics were the same for both missiles, so why couldn't the code that simulates them be?

It seems only the MP version writes to temp/error.txt, which contains: Failed to parse Error running \Scripts\server.lua: ./Scripts/Database/db_main.lua:12: module 'weapons_table' not found: no field package.preload['weapons_table'] no file './LuaSocket/weapons_table.lua' no file './Scripts/Database/../../Config/Weapons/weapons_table.lua' no file './Scripts/Database/../../weapons_table.lua' no file '.\lua-weapons_table.dll' no file '.\weapons_table.dll' no file 'C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\lua-weapons_table.dll' no file 'C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\bin\x86\stable\weapons_table.dll' I did not install any mods so I have no problems reinstalling FC2.0, but I'll wait till tomorrow evening so I can perhaps get some more info on what might be causing this and how it can be fixed/prevented.

My FC2.0 installation went corrupt. When running the single player I get the following error message: Error: ..\blackshark\modules\me_options.lua:329: assertion failed! Stack traceback: ->stack:..\blackshark\modules\me_options.lua in line 329 in func: ->stack:.\BlackShark\BlackShark.lua in line 266 in func: which allows me to press 'OK', to get: ..\blackshark\modules\me_logbook.lua:147: attempt to index field 'country_by_id' (a nil value) after which I can press 'OK' to kill the program. It started after a multiplayer session where I might have gotten the stuck chat bug though I was not aware of it. I restarted the MP and SP versions of FC but TrackIR, HOTAS and keyboard do not respond, except for the ESC key. After restarting the PC I get the error above. My game is not modded except for having manually changed snapviews. Any ideas what might cause this and how to fix it?

Because I only tested it for ground units and choppers, not for AC and ships.

No, they can capture enemy bases as well. They'd have to kill all enemy units and be close enough for the airbase to change coalition. Just make a test mission to try it out.

I tested this with ground units and choppers, not yet with aircraft or ships. What I found was that if ground units gets within a certain distance (I estimate about 1km) from a neutral airbase, the airbase gets that coalition. If those units get destroyed the airbase becomes neutral again. Choppers landing on an airbase had no effect on the airbase coalition.

This is very easy to do. Just set the second group on a 23 hour time hold and activate it once the first group is dead or damaged or has its radar taken out. EDIT: Check out this thread if you hadn't seen it already.

We all do :D

Thank you for looking in to this Alex! The Black Shark tacview.lua uses LoGetWorldObjects to get the name, unitname and groupname of each unit.

No, unfortunately there is no reactivate action. You will have to use active another group.

No, it is not, but you or GG mentioned something about it, so I was wondering what you might be doing on that. With LRM your scripts and locked ACMI was forced upon the clients, but right now it is a free for all. People writing scripts should take their responsibility and inform the community and server admins of how scripts may be misused.

Yoda, what work is done to prevent your software from being misused?

Are you talking about the vanilla or T?

Well, this is the downside of the way FC2.0 works, doing an integrity check instead of, say, uploading server enforced files to each client. However, I think the multiplayer community has to become accustomed to the concept of integrity checks. Without those, multiplayer servers will become chaotic and accusations of exploits and cheats will be the norm. The simplest example is tacview, which any client can run on a server that does not check the integrity of export.lua and has exports enabled. Tacview will simply give anyone a live view of the battle field.

It will depend if the server where you want to fly allows the ability. If it allows it then it will allow it for everyone. If they will not allow it then no one on that server will be able to use it.

Game servers can use the integrity check feature to check if files on the client match those on the server, and if that check fails, they will not be able to join. These integrity checks will become standard practice on game servers to prevent players from cheating. To run a stock server the admins would check the integrity of some crucial files, like export.lua, rearm.lua and modellod.txt. Any player that did not alter these files can join the server without problems. For players that did alter them, the server should provide the accepted files to their clients. If servers want to allow scripts like LEAVU and ERI they should check the integrity of export.lua and the LEAVU/ERI files to ensure that they are not tampered with. One of the problems with the LEAVU and ERI scripts is the fact that they are open source. Anyone can download the code and change it for good and for bad purposes. I cannot stress it more, server admins should start checking the integrity of certain files.

No, copy these files to the FC2.0 config/export folder.

Copy the Ka-50/Config/Export/TacviewExportBlackShark.lua file to Config/Export/ in the FC2.0 directory. Then edit Config/Export/Config.lua to set exports = true, then edit Config/Export/export.lua and add at the end dofile("./Config/Export/TacviewExportBlackShark.lua").