First Mission
Now that you're in the editor, let's start with a simple step and place a few units for yourself and other players.
Name them something like p1 and p2 .
If you want to change the name of the units in the lobby, you can change their name in the description section.
Name them something like p1 and p2 .
If you want to change the name of the units in the lobby, you can change their name in the description section.
Now that we got our units named and created, let's make a simple lose scenario. (If you and your partner die, game over)
Create a trigger.
Condition: !alive p1 && !alive p2
- (!alive means the unit is dead. alive means the unit is alive.)
On Act: forceEnd;
- (forceEnd ends the game)
Click the Type scrolldown box and select something (I prefer choosing End #3 for my lose scenario)
Now click ok.
Create a trigger.
Condition: !alive p1 && !alive p2
- (!alive means the unit is dead. alive means the unit is alive.)
On Act: forceEnd;
- (forceEnd ends the game)
Click the Type scrolldown box and select something (I prefer choosing End #3 for my lose scenario)
Now click ok.
Let's save the mission at this point.
Because we have 2 players, let's call this file co02_examplemission. If you have more players, name it accordingly or if it is a different gamemode, name it accordingly. For example, the prefix for a team deathmatch gamemode is tdm and capture the flag is ctf.
Please do not put space in between your mission file name and don't forget the prefixes. It saves server admins a lot of trouble and keeps thing more tidy and organize instead of creating a huge mess. There's various views on mission naming standards, but Celery got a good idea on how it should be done here.
Because we have 2 players, let's call this file co02_examplemission. If you have more players, name it accordingly or if it is a different gamemode, name it accordingly. For example, the prefix for a team deathmatch gamemode is tdm and capture the flag is ctf.
Please do not put space in between your mission file name and don't forget the prefixes. It saves server admins a lot of trouble and keeps thing more tidy and organize instead of creating a huge mess. There's various views on mission naming standards, but Celery got a good idea on how it should be done here.
Now let's go to the Advance Intel tab and edit some stuff there.
Change all the settings you like and add a description here. For the Name section, you have 2 choices. You can leave it blank or add a name to it, but once again, please try to stick to a mission naming standard to make it easier for server admins. If you want to stick to old school Flashpoint way where all you read is the filename for the mission, then leave it blank. If you want to go by the new way, let's name this mission something like CO 02 Example Mission. Once again, read Celery's thread for the topic about mission naming standards. Click ok when you're done.
Change all the settings you like and add a description here. For the Name section, you have 2 choices. You can leave it blank or add a name to it, but once again, please try to stick to a mission naming standard to make it easier for server admins. If you want to stick to old school Flashpoint way where all you read is the filename for the mission, then leave it blank. If you want to go by the new way, let's name this mission something like CO 02 Example Mission. Once again, read Celery's thread for the topic about mission naming standards. Click ok when you're done.
Save the mission again and now let's go alt tab out of the mission editor and see the files we need for the mission (which comes which my template). You should grab it if you haven't already.
Open up the template and then drag and drop everything inside your mission's folder EXCEPT for the mission.sqm.