Jump to content

Moose set_zones doesn't like me... no idea why


Recommended Posts

Posted

I'm starting to learn Moose to make some more lively missions for me, and one of the first things i wanted to do (after just random unit compositions each run of the map) was some AI heli troop drops. Looking at the example stuff i just went for the random deploy zones off the bat because why not.

 

So i set 3 deploy zones, called Deploy 1, etc... and set my cargo/helis and loaded it up, breaking the mission entirely. DCS.log says: ".../~mis00001DD2"]:7: attempt to index global 'SET_ZONE' (a nil value)"

 

Not sure what it was talking about (before i realized it had a line number there) i commented out all the cargo stuff until the mission worked again (thinking it was the nil in the pickup zone, since i wanted air loaded cargo). It ends up being this line:

DeployZones = SET_ZONE:New():FilterPrefixes( "Deploy" ):FilterStart()

 

So i added local to it, because it did say something about global. No change. I tried loading the Gori Valley mission, which has the same line basically in it, and it seemed to work just fine?

 

local SetDeployZones = SET_ZONE:New():FilterPrefixes( "US Troops Landing Zone" ):FilterStart()

 

Not sure what to do, as best i can tell i haven't done anything wrong?

Posted

Since it had to be something on my end wrong, i pulled out the moose files from both my and the example mission and ran a compare in notepad++. Turns out i had ended up with an old moose file in my mission, but not the editor? (though i just downloaded the stuff a couple of days ago).

 

New moose put in and it seems to be working fine.

 

Just watching a troop deployment heli right now to see if it actually is gonna deploy, such excitement and i'm not even playing!

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...