Death Merchant

Guys, I've written a simple script to spawn new units from a group of units. It works fine in SP, but does not in MP. From what I can figure, it's a problem with the Event Handler. Does the Event Handler work differently for MP? Here is the code I am using. It uses the Player Enter Unit event. EventHandlerControlUnit = {} function EventHandlerControlUnit:onEvent(Event) if ( Event.id == world.event.S_EVENT_PLAYER_ENTER_UNIT and Event.initiator:getPlayerName() ~= nil ) then EventGroup = Event.initiator:getGroup():getName() EventGroupType = Event.initiator:getTypeName() EventGroupID = Event.initiator:getGroup():getID() EventPlayerName = Event.initiator:getPlayerName() trigger.action.outText("Control Detected "..EventGroupType.." "..EventGroup, 15) if ( EventGroupType == "Tigr_233036" ) then trigger.action.outText("Get out of my truck!", 15) end NasamSpawn(EventGroup) end end world.addEventHandler(EventHandlerControlUnit) Any ideas? Thanks, DM

I've been having trouble setting up the LDT, I keep getting errors, so I've been using Notepad++ for my LUA editing. I need to get the LDT setup, I hear it's really helpful.

Thanks guys, you were a big help! It took some work, but I got everything working. I've taken the SnowFox Escalation Misison, added the Hercules mod and added persistent functionality for the units dropped from the Herc. This is going to help a lot. DM

Hey guys, I'm learning scripting and using MOOSE. I've been having limited success with GROUP:FindByName and UNIT:FindByName. From what I can tell the problem usually stems from not knowing the GROUP or UNITS proper and complete name. Is there a way to generate a list of all of the GROUPS and UNITS in a mission so that I can verify the I have the name correct? Thanks, DM

Wizxrd, Thanks for the heads up about the log file. I didn't even know it existed. I've done some more testing and found the line in the code that was keeping the script from running. It's a Moose ZONE command, which I am just now learning about, so I'll post something in the Moose forum. DM

Help!! I am working on a mission and I have a DO SCRIPT FILE trigger, but the file doesn't run. I've looked in the .miz file, and the script is present in the default folder, along with the other scripts, but this particular one won't run. How should I start troubleshooting this? I've tried erasing the trigger, and recreating it, I've also copied the trigger that runs another script and changed the file name, but no success. Any thoughts? Thanks, DM

Is there a tutorial or other resources for learning how to create a persistent campaign. I'm currently learning how to create missions. I have a background in coding and I am in the process of learning LUA. I would love to be able to create persistent campaigns but have not been able to find any information on how to create them. Thanks

It seems to have been SAM threats. I guess the bombers were using terrain masking or something to avoid detection. I've removed a lot of the unnecessary elements from this mission, including some SAM sites. The bombers are now behaving as expected. Thanks for the help guys.

Wow, this is a great guide. I've been having trouble getting bombers to perform the way I expected, but this was a big help. Is there somewhere I can look up typical mission profiles? Alt, airspeed etc.?

MSL, above sea level. No, they are actually in enemy (their own) territory, so no SAMs or other threats. In fact they are supposed to reach their missile launch altitude inside one of their own SAM site coverage zones. I'll give this a try. I did set the speed to Mach 0.85. I'll bring it down a bit a see what happens.

I'm working on a mission and I keep getting strange behaviors from my AI bombers. I have waypoints set with altitudes of 15,000 - 35,000 feet, but some of the bombers are flying nap-of-the-earth down in the valleys, sometimes even crashing into mountains. What information do you need from me to help me solve this problem? Can I post the *.miz file?

I don't have the exact date, but it was sometime in the last couple of months.

It's a recent Win 10 update that has caused graphics problems for some users. I had some problems after Win 10 installed KB5001330. I cured the problem by moving the system paging file to a non-OS SSD. Win 10 had assigned it to the only HDD in my system. I don't know if that problem was caused by KB5001330, but the timing seem coincidental.

I think that's a great idea. The old Command & Conquer series had an entire collection of maps to use for mission making, as well as an editor. It made for some great terrain or scenario missions like the ones you've listed.