EDIT: If you want to learn about the studio beyond what I talked about here, do check out @TommyCD1's stream where he expands on everything I talked about in this video! kzread.info/dash/bejne/mHqKyc6Bia6nkrw.html More on objectives: As the name implies, they can be used to create game-ending objectives. Like in mission 10, if the green team reaches the region on the opposite side of the counter, they'll be given a victory condition following the cutscene of the heroes escaping the bathroom ants. But the objective system also handle where objective markers appear on the minimap, completing medal objectives, starting cutscenes, whether a cheatcode was unlocked, unit spawns, activating/deactivating other objectives, and more. Basically anything that can be tied to mission-specific scripts are handled by the objective system. But good luck coding your own, in C++ no less. Best to just copy what's already there and try to tweak it to your needs. Going through pre-existing code often does wonders for learning how to work it. Here are the default objectives and their function: *common.timer.win* - Fade out and declare this team and any allies the victor *common.timer.lose* - Fade out and declare this team and any allies defeated *common.timer.eliminate* - Eliminate this team after a few seconds, barring them a victory condition for the remainder of the match *common.eliminate* - Wait until this team has no units and no allies with units, then initiate common.timer.eliminate for this team *common.killallenemy* - Wait until this team has no enemies with any units, then initiate common.timer.win for this team *common.aivictory* - Wait until there are opposing human-controlled teams remaining AND no human-controlled enemies remaining, then initiate common.timer.win for this team (I might be phrasing this one wrong) *common.gbtan* - Wait until this team has no HQs, resource depots, barracks, or garages left, then initiate common.timer.lose for this team *common.gbgreen* - Wait until this team has no units and no allies with units,then initiate common.timer.lose for this team [Ruleset "protect"] *protecthq.checkgame* - Wait until this team doesn't have an HQ, then warn them + allies that they'll be eliminated if one cannot be built in 3 minutes, then initiate protecthq.timer AND protecthq.build for this team [Ruleset "protect"] *protecthq.build* - Wait until this team has an HQ that's fully built, then abandon protecthq.timer for this team and deactivate the on-screen timer, then initiate protecthq.checkgame [Ruleset "protect"] *protecthq.timer* - Wait until the 180 second timer expires, then knockout and destroy everything this team controls [Ruleset "protect"] *protecthq.check* - Same as protecthq.checkgame, but allies won't be notified the team doesn't have an HQ (used as the starting objective for this ruleset)

Would it be okay if I watched this video on stream? I wanted to try doing some more studio how to stuff, since I'm having real trouble writing my own from scratch.

@july-lion

6 ай бұрын

I'm a little embarrassed with how rushed and unpolished this tutorial is, but that'd be ok. As far as writing stuff down, I am still (slowly) working on the AMRTS Developer Manuel I mentioned on the ExF forums: clanexf.com/forums/viewtopic.php?p=15562#p15562