Hardcard

Btw, I've just noticed that you are using invalid country enumerators for the MiG-21s (which might be related to the repeated spawning issue) The correct country enumerator for Russia is this: country.id.[color="Green"]RUSSIA[/color]

I'm doing this for me as much as for you and others, don't worry about it. Learning new stuff as I go, increasing my understanding of lua and perfecting the script, two birds with one stone, as they say. :thumbup: The good news is that I think I've finally found a way of keeping things automatic while having statics spawn from mission start (without being tied to parking spots). This new script I'm working on is the best version so far (I think)... but the required setup process requires some explaining (probably will post a tutorial video for this in the near future) @Rudel I'll send you the new files + a link to a video tutorial that I've made for you (in Spanish) I hope this new version will satisfy all your fundamental requirements ;) As for the issue you're having with those MiG21s, you're using one of the previous versions of the script (the "improved" one?), I've changed things around in the latest versions.

How about another version of the automatic script that does the following? : - Spawn statics right from the start - Spawn statics at the same coordinates as the clients they're replacing, regardless of their location on the map. I still need to figure out a way to get the liveries directly from the clients, though...

Yes, you can check whether the shooting units belong to specific groups. But keep in mind that these events are triggered by individual units, not groups. This script can be loaded with a MISSION START trigger, if you want.

The battle is not lost, I might figure out a way to spawn a first round of statics, regardless of client activation. In order to achieve this high level of automation, I had to ditch the static spawning method I used in the previous versions of the script (which allowed a bit more freedom in this regard) This new method is way better, since it doesn't require static templates or reference tables (except for the freaking liveries :badmood:), but things can get messy if "unregistered" statics are present on the map when clients start spawning. I'm pretty sure I can find a way to spawn and "register" a first set of statics, before any clients join :thumbup:

Well, well, I ended up making the script (almost) completely automatic :lol: With this new version, there's no need to place any static templates on the map, statics are created and spawned from "thin air", so to speak. The script does everything for you, but there are a couple of catches: - If you want the replacement static liveries to be consistent with the client's, you'll need to fill the Livery_Table, which looks like this: - Replacement statics will only spawn after clients switch slots (they will only replace client aircraft that have been active at least once). - Remember to provide the common client prefix/suffix (it's in line 147): ClientSET = SET_CLIENT:New():FilterActive(Active):FilterPrefixes("[color="red"]common client prefix/suffix[/color]"):FilterOnce() - Remember that you need to join spectators before entering client slots at mission start (when joining the mission for the first time) Other than this, the script should work anywhere, you can test it in Nevada map if you want :thumbup: Client Static Replacement (Automated).miz Client Replacement with Statics (Automatic version).lua

Yes, that's correct. That reference info comes in handy when you need to know the terminal index and type of specific parking spots. However, I think I've just figured out a way to get the client's terminal index automatically...let me do some testing and report back.

The required terminal indices for the demo mission clients are already included in Reference_Table:

@ReflexArc If you haven't already, join the MOOSE Discord channel Share this info with the MOOSE community there. Also, please, report the issue (including your findings) here. Thanks for the nice detective work! :thumbup:

Trust me, you don't want to go through such torture :lol: I've already mapped all airbases in Caucasus (raw data file attached, pics are coming soon!), PG is next in the list. Don't worry, I'll do Nevada as well. Caucasus Parking Spots.lua

@ReflexArc Did you modify the SEADWeaponName values, like I suggested in the other posts? That didn't solve the issue for me, but looks like a necessary modification nonetheless. Also, that last error that you posted, was it also?: attempt to index global 'EVENT' (a nil value)

@ReflexArc MOOSE SEAD evasion doesn't work (it's already reported, btw). Setting SAM radar to alarm state green when SEAD missiles target them should do the trick (this is what I did when I wrote my own SEAD evasion script)

The mapping process is going smoothly, I'm done mapping all Georgian airbases (Blue) in Caucasus map (raw data file attached) . The reference pics will take more time to make, but I've already done Kobuleti and Vaziani: Caucasus Blue Coalition Parking Spots.lua

That funny issue happens when both conditions in the following logic check return true: if ClientSet:FindClient(client.ClientName) == nil and Spawned_Check(client.StaticName) == false then It might be a naming issue (affecting clients and / or statics), it might also be that the statics aren't populating Spawned_Static_Table on Birth. Also, perhaps the ClientSET isn't being updated properly... You can check whether ClientSET is updating properly by uncommenting the following message (line 94 in the "improved" demo mission script): -- MESSAGE:New("Static_Spawner running!\nClientSet count = "..ClientSet:Count(), 10):ToAll() It'll give you a count of active clients... make sure that it's consistent with the number of clients currently active (remember that they must all use the PILOT name prefix / suffix for it to work!)

Well, those "incomprehensible instructions" taught me how to do it... maybe the problem is that you didn't take the time to carefully examine the content of the several links I provided. I mean, this post alone provided the necessary information + an example of how to add and remove menus: https://forums.eagle.ru/showpost.php?p=3969423&postcount=20 On top of it, I linked the MOOSE documentation for MENU class (which contains all the methods + examples)...twice Sorry, I assumed you already had all the info you required, my bad :doh:

Hi guys! Don't worry, I'm currently mapping all airbases in Caucasus, then I'll move on to PG and Nevada airbases. My goal is for this script to work, no matter what you throw at it :thumbup: @Rudel_chw If you're using the second version of the script (the "improved" one), make sure to include one static per client (their names must be unique), otherwise you'll experience problems with aircraft of the same type not spawning. Also, in the following line, change 1000 for 100 (I suspect 1000 causes problems): SPAWNSTATIC_Table[i]:SpawnFromPointVec2( ZONE:New(client.ZoneName):GetPointVec2(), client.Bearing, client.StaticName..math.random(1, [color="Red"]1000[/color]) ) As for the static spawning on top of that structure, I haven't tested anything in NTTR yet, we'll get there ;)

I've made further improvements to the script and added extra clients (12 total) I experienced Rudel_chw's access violation the very first time I included an extra client, but looks like the issue is solved now (fingers crossed). New demo mission + script file attached IMPORTANT NOTE: I've gotten rid of spawn zones, spawn coordinates are now directly obtained from the parking spots on Kobuleti (other airfields are not supported at this point...unless you know the terminal IDs). Also, add a replacement static for each client and give it a unique name, otherwise there are problems. Set the static templates to DEAD, though, that way they shouldn't impact performance. You'll also notice that I've made further modifications to the reference table (and some other stuff elsewhere): Client Static Replacement (further improved).miz Client Replacement with Statics (further improved).lua

That doesn't sound right. It should work with any number of clients you want. Let me add a gazillion clients and report back... oh wait, you meant more than two people playing at the same time?

Alright, alright. You need to include all your clients in a set, then use event HIT and / or event SHOT handlers to check both the initiator and the target. If both the initiator and the target belong to the same coalition, you can punish the initiator in several ways. Let me know if you need a script example.

https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Core.Menu.html##(MENU_GROUP_COMMAND).Remove

@Pikey I've never used MIST, sorry. However, if you're interested in getting an offset spawn coordinate from a POSITIONABLE, Funkyfranky created :GetOffsetCoordinate(x,y,z) (keeps the relative offset, regardless of orientation, it's pretty neat) It's not included in the MOOSE documentation yet, but it's in the latest Moose include ( develop ), it works quite nicely. You can get the vec2 from the returned coordinate, which can be used by dynAdd.

@Rudel_chw Hi there! I've had the chance to test the mission in MP and it was all fine, no access violation crashes after switching clients (even after dying). There was increased delay, though, which caused statics to remain on the parking spots for just a tiny bit longer, but other than that, everything seemed fine. Looks like the problem might be on your end

I don't know about that marker, but I think your snippet has bad syntax in it (which might explain why it doesn't work): CaptureZone = ZONE:New( "CaptureZone1" ) ZoneCaptureCoalition = ZONE_CAPTURE_COALITION:New( CaptureZone, coalition.side.RED ) function ZoneCaptureCoalition:[color="Red"]OnEnterEmpty[/color]() [color="Blue"]-- The correct syntax seems to be :onenterEmpty()[/color] MessageToBlue( "Good Job", 20 ) end ZoneCaptureCoalition:Start( 10, 30 )

I wish there was an option to make DCS CTD, stress cpu / gpu like crazy and stop the fans. That'd teach 'em :megalol:

Thanks for testing it! Looks like you're getting access violations, for some reason... I created the mission using the latest openbeta, btw, if your dedicated server is running something else, that might explain the problem. It's also possible that the mission / script needs to be modified in a certain way for MP... I'll investigate and ask around, see if I can find answers