Last active 49 minutes ago
Put the x folder in your mission’s root folder.
Have fun with it! It’s developed by at least two members on our team (Tupolov and AuTigerGrad) so yes it’s made with ALiVE in mind first and foremost.
Oh you don’t need that many then. Just put one civilian/military for each side, then add the marker names to the whitelist in each objective placement module. If they don’t pick up objectives where your markers are, place custom objectives in the dead places instead.
I’m assuming all those objective placement modules over the markers are custom objective modules? First thing I notice is that you don’t have the opposing sides synced to either of the other side’s objectives. So first things first I’d synced the bottom Commander module to the top side’s custom objective modules.
That’s what I’d try. Though without military or civilian placement objective modules, I’m not sure if the groups spawned by the custom objective modules will leave their areas and attack the synced modules. One way to find out though.
Holy moly the mods :(
I accidentally wrote it with the underscore after call above. Oooopppppppss :(
I know my bad. I tried to unping you but I guess I couldn’t unring that bell fast enough. Sorry :)
EDIT: there is no underscore needed after using call. See my post above with the code. Copy and paste if you have to. That’s the problem.
Fairly certain ALiVE written like this is not optional, and needs to be written exactly how I have it in the code (all capital with a lower case i ). Try putting a ; after it also to see if that works.
I’m not 100% on this but try it.
Also be sure to click local exec when running the code.
^ you may need to enable debug console in your mission though. There’s an option for it in the editor, or you can put enableDebugConsole= 1; in your description.ext file in your mission root folder (either or, not both).