Ultra Modding | Unreal Engine Modding

DM-LEGO

UltraKill — Wed, 31 Dec 2014 01:18:37 GMT

Forum: [W.I.P] MAPS
Thread description: port from CSS
Thread starter: UltraKill
Last message posted by: UltraKill
Number of replies: 0

Collision / Коллизия моделей в SDK.

UltraKill — Mon, 20 May 2013 21:19:03 GMT

Всем нам знакомы ситуации когда можно проходить насквозь моделей, или при стрельбе по ним, пули пролетают насквозь.

Эта опция оптимизирует карту целиком, тем более если карта большая.

Начнем:

1. Открываем свойства предмета
2. Открываем вкладку Collision.

-Там видим список параметров:
- bAutoAligntoTerrain = Автоматически выравнивать по земле, крайне редко нужная штука.
- bBlockActors = Блокирует акторы. (зомби, игроков)
- bBlockKarma = Блокирует Камру (трупы зомби, другие объекты на карте)
- bBlockNonZeroExtentTraces = Блокирует Трейсы. (пули, ракеты, все что может летать и взрываться)
- bBlockZeroExtentTraces = Блокирует трейсы от эмиттеров, и других "прозрачных" объектов.
- bCollideActors = "сплющивает" с другими статиками на карте, находящиеся рядом.
- bPathColliding = Будут ли мобы идти к нему или через него.
- bProjTarget = прожектиль, Всегда на False должна быть, может быть неадекватное наложение света и др. еффектов.
- bUseCylinderCollision = Установить ему "контур" цилиндра, тоже иногда помогает.
- CollisionHeight / CollisionRadius = размеры и радиус "блокирования" (если установлено)
- SurfaceType = тип поверхности, часто зависит от текстуры которая наложена на объект.

И так, если статик находится вне поле зрения, или вне зоны досягаемости игрока, нужно установить Коллюжн как на скриншоте:

СОЗДАНИЕ МОДЕЛЕЙ / ТЕКСТУР ДЛЯ KILLING FLOOR SDK.

UltraKill — Tue, 14 May 2013 17:58:07 GMT

СОЗДАНИЕ МОДЕЛЕЙ / ТЕКСТУР ДЛЯ KILLING FLOOR SDK.

Нам понадобится софт. позволяющий экспортировать изменять и импортировать 3д модели разных форматов.
пример: 3DS MAX, Cinema 4D, MilkShape 3D.

1. Скачиваем / создаем нужную нам модель.
В данном уроке, будет модель танка.

2. Експортируем выбранную модель в формат (.ASE)

3. Открываем браузер статиков.

4. Далее, идем ко вкладке File > Import...

5. Заполняем поля, название пакета, группа объектов (необязательно) и название объекта - обязательно.
на рисунке я поставил Tank_sm (Tank_StaticMesh), для более удобной навигации и управления файлами, можно добавлять в конце названия пакетов аббревиатуры, например: Static Mesh - sm, Texture - Tex / T, Sounds - S / Snd, Animations - Anims / A.

6. Открываем браузер Текстур.

7. Также как и статик, текстуры нужно импортировать в редактор, они должны быть в формате (.TGA / .DDS)
с четным расширением (1*1, 2*2, 4*4, 256*256, 512*512, 512*256, 1024*1024, 2048*2024, 512*1024, 1024*2048)

8. Название пакета, так-же, как и со статиками, как Вам удобне - так и называйте. но без пробелов и только латинскими буквами.

9. В браузере текстур, открываем наш пакет (Tank_T) и проводим компрессию текстур.
ПКМ > Compress > DXT3,
DXT5 запоминает два значения для квада 4х4, а остальные значения получает через интерполяцию этих двух
DXT3 запоминает альфу для каждого пикселя по 4 бита на пиксель. самый оптимальный вариант.
при этом если у вас будет пакет с текстурами, где их количество будет около 10 и размер от 1024*1024 и выше, то Ваш пакет с текстурами будет весить около 100 мб. (редко кто дождется такой долгой загрузки с сервера)

10. Проверяем, если ничего не пропустили, и приступаем к сохранению.
После компрессия текстуры, рядом с ее именем появляется слово в скобках [DXT3] если оно есть, компрессия прошла успешно.

11. Далее, открываем браузер статиков (шаг 3)
Внизу, есть вкладка Materials, нажимаем на нее, и появляются еше вкладки, далее, там нужно будет вставить текстуру на танк, это делается нажав на текстуру в браузере текстур (шаг 6), нажимаем на одну из текстур, и в вкладке Material 0, жмем на Use (справа, в том же ряду)
и так все материалы нужно заполнить, сначала на угад, но когда разберетесь какая текстура, куда идет, быстро привыкните.
Не все объекты имеют такую возможность, если объекты, у которых одна текстура, а есть у которых 15 текстур.

12. Далее, сохраняем наш пакет с моделью танка, после текстурирования.

13. Сохраняем пакет Текстур.

Теперь, можно будет пользоваться моделью танка на Любой карте, и менять ему текстуры, цвета и форму.

Вот что у меня получилось с этим малышом сделать.

Скачать карту с Танком и посмотреть как его можно "оформить" можно пройдя по этой ссылке.
http://ultramodding....c_mesh/1-1-0-13

Кстати, нужно бы написать гайд по эмиттерам..

KF-ROMAN-ARENA [UltraMapping]

UltraKill — Wed, 08 May 2013 15:20:49 GMT

About:

map in the style of "ancient Rome" in the bright summer sky .. far away from the world .. Zombies want to grab one of the last paradises of distant places in the universe

decided to finish before the end of a good map, since already ashamed to answer to everyone who asks of "Now is no time, or I'm too lazy" =)

ChangezLog:

- Fixed textures. (maked shaders, combiners,now looks awesome :P)
- Corrected some of the objects (or rather their display in the game).
- Added ZED spawnz.
- Removed unnecessary files. (music)
- Changed color. (now more beautiful and realistic)
- Fixed ZED's ways (nodes)
- Finally added a beautiful sky =)
- Corrected, or rather I am the one who found the solution to the "demonization" of textures on the approach. (planning and Cannon Fodder correct, he has the same problem.)

Screenz of finally version:

Beautiful textures was created after maked video =)..
(80% of the finished map)

FIrst version:

КОПИРОВАНИЕ / ДОБАВЛЕНИЕ ОБЪЕКТОВ НА КАРТУ.

UltraKill — Mon, 22 Apr 2013 21:22:35 GMT

КОПИРОВАНИЕ / ДОБАВЛЕНИЕ ОБЪЕКТОВ НА КАРТУ.

СПОСОБ № 1.

1. Открываем желаемую карту в редакторе.
2. Выбираем нужный нам объект.
3. Жмем ПКМ на него, далее Convert > To Static Mesh

4. Пишем желаемое имя пакета объектов, название Группы (необязательно) и имя объекта.

5. Открываем браузер статиков

6. Выбираем созданный пакет, для проверки и сохранения.

7. После визуальной проверки, можно перейти к сохранению.

8. Название пакета остается то-же что ставили ранее (шаг 4).

9. Открываем свою карту, добираемся до нужного места, куда хотите поставить объект, жмем ПКМ на поверхность, при этом нужно заранее выбрать нужный нам объект в браузере (см шаг 5)
и жмем Add Static mesh (имя пакета .имя группы .имя объекта)

СПОСОБ №2.

1. Открываем желаемую карту.
2. Открываем браузер объектов.

3. Выбираем нужный пакет, и нужный нам объект.
(например: KillingFloorLabStatics)
Выбираем вкладку Edit > Rename...

4. В появившемся окошке вписываем название пакета MyLevel*, остальное можно назвать как угодно.

5. В браузере выбираем пакет MyLevel, чтобы проверить, все ли объекты скопированы. (Если нет, то возвращаемся к шагу 3)

6. Закрываем браузер, и сохраняем проект (сохраняем карту)

7. Далее, перезапускаем редактор, открываем карту которую только что сохранили,
выбираем нужный нам объект, нажимаем CTRL+C (если несколько то зажав CTRL выбираем несколько), открываем наш проект (карту, на которую хотите поставить скопированные объекты) и в любом месте жмете CTRL+V, далее располагаете вставленные объекты как вам угодно.

ПРИМЕЧАНИЕ:
Второй метод не всегда уместен, иногда не самый лучший вариант сохранять карту, если вы на ней будете играть, потомучто Вам придется скачивать ее по новой с сервера при подключении.

По этому первый вариант самый лучший, но при этом, нужно будет вставлять и используемые пакеты текстур / статиков в архив с картой, например если вы используете объекты из пакета Example, то в конце, нужно будет создать папку Static Meshes, скопировать туда этот пакет.
---
При создании пакетов с объектами, необходимы пакеты с текстурами.
он этом чуть позже.
---
На многих кастомных картах, объекты уже вставлены в пакет MyLevel (его не нужно вставлять в архив с картой, это пакет вшитый в карту) остается лишь скопировать их и сохранить карту.
Решил поделится простым способом.

Ссылка на оригинал

by UltraKill*

СОЗДАНИЕ / НАСТРОЙКА ТЕЛЕПОРТЕРОВ В KILLING FLOOR SDK.

UltraKill — Mon, 22 Apr 2013 21:21:17 GMT

СОЗДАНИЕ / НАСТРОЙКА ТЕЛЕПОРТЕРОВ В KILLING FLOOR SDK.

1. Открываем нужную карту.
2. Жмем на кнопку "Actor Browser".

3. Выбираем вкладку "Navigation point"
4. Ставим нужный тип Телепортеров (KFTraderTeleporter это телерепортер от торговца)

5. Жмем Правый клик в нужном месте на карте, затем "Add KFTeleporter Here"

(раскидать 2 телепортера в разных концах карты к примеру)
6. Открываем "Proprietes" Второго. телепортера, вкладка "Event" ставим Tag (к примеру TestTeleport1), это путь где появится игрок зашедший в телепортер.

7. Открываем "Proprietes" Первого. телепортера, открываем вкладку "Teleporter" , затем в "URL" пишем Tag который написали в Втором телепортере, то-есть "TestTeleport1".

Принцип Телепортеров:
Первый актор телепортирует по Tag-у, ко второму.
Если на втором тоже стоит какой-либо URL, на первый, то можно сделать телепортер в 2 конца (с точки А в точку Б и с точки Б в точку А, по тому же пути.)
В уроке присудствует карта, с телепортерами, в оба конца, и стандартные, в один конец.

Скачать Карту можно отсюда:
http://www.mediafire...itxtnd54w31s8tn

Так-же есть другие способы телепортировать игроков / мутантов, при помощи триггеров, но об этом чуть позже.

How To Optimize Your Map

UltraKill — Thu, 04 Apr 2013 12:59:35 GMT

This thread is to give mappers tips on making faster running maps. If you have anymore suggestions, please post below

-----------------------------------------------------------------------
Ways to Optimize Your Map

1: Add cull distance to meshes and emitters

2: Put No collision on complex meshes, or even simple ones. Then add a blocker around them

3A: Convert Solid brushes to mesh, then add no collision

OR

3B: Right click your solid brushes (Blue) goto Type> Non-Solid NOTE: Only works on solid brushes

4: Zone Portals

5: Add anti portals inside walls

6: Open up the Mesh browser, for your meshes, select the mesh, then, (up top of the window) Collision Tools> Fit 6-DOP

7: All surfaces unseen by player, Goto properties (F5) and set Unlit

8: All surfaces unseen by player, Set the texture to a solid black texture

9: Reduce the MaxParticles in your emitters. (F4) > Emitter > General > MaxParticles

10: Com-pres Lights to Dxt-1 Goto your build options, and under lights, select Dxt-1 then build all in that window

11: Set all complex terrain items (aka: groups of trees, grass, bushes) to a deco layer

12: Set bshadowcast to False on meshes that dont require a shadow

13: DONT FORGET TO USE THE DEPTH COMPLEXITY VIEW (3D Window) Anything red is laggy

------------------------------------------------------------------------------------------------------------

How to convert complex brushes to mesh

Note: It is easier to select your brushes, then copy and paste into a new map

Also note: I refer to the group of brushes that you want to convert as an object.

Step 0: Make sure you object is suspended in mid air

Step 1: Take your builder brush (red brush) and cover the tops bottoms and sides of your "object"

Step 2: Once the Brush is completely covering the object, press the intersect button (its below add)

Step 3: Make sure you click one of the corners so you have a pivot point

Step 4: Right click the brush tool (which is now in the form of your object) and select Convert > StaticMesh

Step 5: Package: MyLevel
------- Group: Whatever
------- Name: TheMeshIMade
-------
Step 6: Goto your static mesh browser, your mesh is in the MyLevel group (Pull down tab)

-------------------------------------------------------------------------------------------------------------

How to make custom collision for complex objects

For complex collision meshes, you can edit the collision brush.

A- Right click 3d window> view> collision

B- Position the builder brush (red brush) where you want the collision to be for that mesh

C- Select the builder brush, and the mesh. Right click(mesh)> Save brush as collision

D- This will remake the collision for this object, so you can make a simple collision brush, instead of a complex many angle collision

E- Dont forget to do number 6 up top

[DA2] Basic Mapping Tutorial

UltraKill — Thu, 04 Apr 2013 12:58:10 GMT

In this basic tutorial I will explain step by step how to make your own Defence Alliance 2 map. It is required that you know the basics of level design in order to follow this tutorial.

I've already made a simple level, where I plan to have one destroyable objective. I will also place serveral actors in which I let bots defend and make a turret. And finally I will place a defensive turret in my level.

TeamConfig

We will begin with the TeamConfig actors. These will determine how many turrets and ammoboxes a team can built.
We have to place two TeamConfig actors, for each team. We have to set the team numbers for each actor, by default they are defenders. So in the first actor we have to change the turret limits and bot behaviour to Defend. In the second one we only have to change the team number to 1.

Team 0 = Defenders
Team 1 = Attackers

Objective

Now that we have deterimed what team will attack and defend (ps.teams cannot be switched around), we will add our Objective. As I said in the introduction, I have chosen for a destroyable Objective, but it's also possible to add a switch or an area that needs to be reached by the attackers.

By default the static mesh will be a switch when you first place it, I have changed it into an oil tower. When rebuilding our map, i've received an error that our Objective is not on a valid base. This means that the collision circle isn't in touch with the ground. We have to change the PrePivot in order to fix this issue.

When we rebuild our map now, it doesn't give any errors. We now have to set the health of the Objective, I've changed it to a 1000 health.

Finally we can set this Objective as win. This means that when this Objective has been accomplished, the game will end. In every map it is required that you have atleast one Objective that wins the game. We can also set a value for BonusTime. When this Objective has been accomplished, this time will be added to the clock, and will give the attackers more time to get to the following objectives.

Under MUB, Mission Update B.. (I forgot), we can set a message that will be shown to the defenders and attackers when this objective has been accomplished.

When you have multiple Objectives, you have to change the DefensePriority in +GameObjective. The first objective will start with the lowest priority, for instance we have four objectives, then the first objective has DefensePriority 3, the second: 2, etc and then the final Objective has 0.

In the GameObjective tab, we can also set the score that the attacker will receive when he accomplishes this Objective.
And the name of the Objective, which will be shown in the HUD.

Finally we have to set the DefenseScript here, which we will talk about next.

We can now also give the Objective an Event. With this event you can trigger a series of other actors, like TriggeredPlayerstarts, so the attackers can spawn at this objective.
We give this Objective the following event: first_objective.

DefenseScript

We can now place actors which let defenders stand at. These are called UnrealScriptedSequence. They are already setup, so you only have to place them in the map, and change it's Tag. We gave it the same name as the objective: first_objective, this has to be entered at the GameObjective tab in the properties of the Objective, like we just talked about.

You can also change the time the defender has to stand at this actor and a certain other options, which I won't go into detail in this tutorial.

BuildBeacon

To let the defending bots built structures, like turrets or ammoboxes. We have to place a builtBeacon somewhere we thing would fit. We first have to get the object name, that is given to the Objective, we want the defending bots to built their turret at. In our case it's called: "da_objective_destroyable0"

After placing our builtBeacon, we then have to type at Objective: "da_objective_destroyable0", and it will automaticly change to "da_objective_destroyable,mylevel.objectivedestroy able0". We can also choose if we want it to built a random structure there. But in our case we will let it at False, and select a turret from the dropdown list.
You can then also set the suggestbuilt, which determines the priority which turret should be built first (0 has most priority) And finally we have to set the team. (Team 0 = Defenders, Team 1 = Attackers)

by Dest

Killing Floor SDK and Mapping Guide

UltraKill — Thu, 04 Apr 2013 12:57:01 GMT

You can download the Killing Floor SDK from the Tools section in Steam.

The official SDK and mapping guide for Killing Floor is now available! The guide can be found in:

\Steam\steamapps\common\killingfloor\MappingGuide

And the SDK can be found in the Tools section in Steam. You can also launch it from your system folder:

\Steam\steamapps\common\killingfloor\System\KFEd.exe

How To Make A Story Map

UltraKill — Thu, 04 Apr 2013 12:54:26 GMT

Hey guys!

So as some of you are aware I've been developing a Story gametype for Killing Floor. It dawned on me that there's currently no documentation on how to actually use this mode in a map. So i'm here to shed a little light on that Please note - this is not an unreal mapping tutorial. I am assuming that if you are reading this you already understand the basics of using the editor and putting a level together (bsp, playerstarts, etc)

Things you'll need :

1. The StoryMode code/content. you can find the latest version in this thread. Extract it to your root KillingFloor folder.

2. You'll need to modify your KillingFloor.ini file to get it to load the story scripts in the editor. To do this, open up the afformentioned file and scroll to the 'editPackages' section (beneath Editor.EditorEngine) You should add an entry for KFStoryGame. it would look like so :

Code:
EditPackages=KFStoryGame
Last step would be to delete your 'User.ini' file (after making sure the DefUser.ini from the StoryMode zip file is in your system folder. This will enable key-binds necessary for story mode.

Done all that? Alright! You're now ready to start story mapping!

The main components of a story mission

Story mission gameplay is built using several different actors to create a web of conditions and events that can tell the game when to spawn enemies, open doors, save player progress, and so on . The main actors you will be using in your missions are as follows :

KF_StoryCheckPointVolume
KF_StoryZombieVolume
KF_StoryObjective
KF_LevelRules_Story

KF_StoryObjective

This is the most important component of a story mission as it defines what a player's goals are and what is required of him to complete the mission (or fail it). Every story map should have at least one of these actors. You can find them in the actor browser under 'navigation point'

KF_LevelRules_Story

This actor defines some broad gameplay rules in your map . Things like the maximum number of zombies that are allowed at once... or the amount of cash players lose when they die. Every map should have ONE of these actors, no more.

KF_StoryCheckPointVolume

This volume is used to save players progress as they work their way through the mission. If they die, they will respawn from the last activated checkpoint, and the game state will reset itself to closely resemble what it was at the time that checkpoint was reached. Most story maps will have multiple checkpoints. Note that it is possible to stack checkpoint volumes on top of one another, if you want to save progress without having players actually move through the level. More on that later.

KF_StoryZombieVolume

This one should be fairly self explanatory. It is a modified version of the default 'ZombieVolume' used in the Vanilla KF Game mode, with additional features to give level designers control over when and how zombies should spawn.

Creating a Simple Mission

Now that I've covered the boring stuff, i'm going to skip right ahead to practical application of these actors. We're going to be putting together a simple map with a type of gameplay quite similar to the regular KF survival GameType. The twist is - As you defeat specimens new areas of the map will unlock and you will have to progress through each area to the final one before you can win.

Let's get started

This is the map you will be making

This tutorial map is very simple. it is 3 long corridors separated by doors. Players spawn at one end and progress to the other end. The doors unlock as each 'wave' is completed. All of which is triggered by the Objectives you will be placing.

The very first step in making a story map should be to place a starting checkpoint. You must ensure that there is at least one playerstart inside any checkpoint you place or it will not function correctly. In my example, I have added six (because it is the KF max player count).

Next you need to adjust a few properties. in the 'StoryCheckPoint' rollout, set 'bStartEnabled' to true , and then give the checkpoint a name. bStartEnabled means that when the match begins your team will spawn at one of the playerstarts inside the checkpoint volume. If your team dies, it will restart from that spot. Each story map should only have *one* checkpoint marked bStartEnabled, otherwise the game will get confused about where to place you.

The next step is to add a levelRules actor. Story maps require these to work correctly. You can find this actor here :Code:
Info-->LevelGameRules-->KFSPLevelInfo---->KFLevelRules_Story
The level rules actor has a bunch of cool properties, but the most important one by far is the 'Objectives' tab. Open that one up and you will see an empty array. This is where you will be setting up a list of all the objectives in your map and the order they must be completed in. An Objective at index 0 is to be completed before an objective and index 1, for example.

This map will have seven objectives. They should proceed in a similar order to what I show in the above screenshot, with a wave timer followed by a wave, followed by a progression into the next area.

So let's take a look at the very first objective in that list - 'WaitForWave1'

The first thing you will notice is that there are *alot* of properties in objective actors. Don't worry about it. 90% of them won't apply to the objective you are making. I have highlighted the key ones in Red. ObjectiveName is important because this is how the LevelRules actor identifies it and puts it in the Objective que. Whatever you enter for 'ObjectiveName' *must* match what you put in the LevelRules , or it won't work.

The next important property would be the 'SuccessCondition'. This is what determines how this objective must be completed. For our 'WaitForWave1' objective, it's nothing too complex - We just want abit of time to pass before the first wave begins, so we set the Success condition to OBJ_Timed, and the duration to 10 seconds (in the OBJ_Timed rollout).

Next, note the 'SuccessAction'. This is what tells the game what should happen when this objective has been completed. The default behavior is to just proceed to the next objective on the level rules list. We'll leave that unchanged because the next objective is the first specimen wave, and we want it to start immediately once the time is up.

Finally, there is the 'HUD' rollout. This is not crucial, but it provides the player with some idea of what the objective is all about, so it would be a good idea to fill it in. Here's how I set mine up :

So after all that, here's how the first objective would look when we start the mission up.

Alright, so that's it for the timer - But now we need to figure out how to spawn some zombies and start the 'wave' for real.

To do this, we first need to place a KF_StoryZombieVolume.

Again, lots of properties here. By default any zombie volume you place will just spit out zombies automatically. to prevent this, you need to set 'bTimerStartsDisabled' so that it can be activated at an opportune time. The 'SpawnTypes' array controls the type of ZED this volume spits out, and the chance of it being one type of ZED or another. I won't get into that in too much detail ... suffice it to say, you need *something* in there for the volume to spawn.

Next , take a look at the 'Tag' and 'ZombieEvent' properties in the Events rollout. These are very important. To get your volume to start/stop spawning zombies you need to trigger it & that's what the tag is for. The 'ZombieEvent' is an event any Zombie spawned by this volume fires off when he dies. We will be using this event to increment our second Objective, a way of letting it know that we're killing stuff and completing our goal.

Speaking of that second objective - Let's take a look at how it's set up.

Our 'SuccessCondition' for this objective is a 'Counter'. Counters are used for ... you guessed it, counting. Each time an objective with that type of success condition is triggered, it will increment the counter by one. So we match the tag of our counter objective with the 'ZombieEvent' property from our ZombieVolume ... and suddenly, killing zombies will bring us closer to completing this objective.

The Objective Events tab is also relevant here. There are separate arrays of events you can fire off at different times. the 'Activation Events' array is fired off at the moment when that objective becomes your goal in the mission. The Completion events fire off when the objective is successfully finished. As you can see, 'Wave1Zombies' (the tag from our zombie volume) has been added to both arrays. This means that when the Counter objective starts, it will activate the Zombie volume, and when it finishes it will shut the Zombie volume off.

Here is how the finished result looks in-game.

I'm going to skip over the part about the Door Movers , because I'm sure everyone here knows how those work. The Completion event from our counter objective causes the door to lower so you can move to the next area.

Which brings us to the next Objective in the list 'GoToNextRoom'. This objective has a 'Triggered' Success condition - which means that it will be considered complete whenever it is the recipient of an event. We will be using a second Checkpoint volume in the next room to fire off that event and tell the game that all the players are inside.

This is how the second checkpoint in the map looks :

As you can see it spans the entire length of the corridor. This was intentional. When you enter the second room the door will close behind you so you can't escape the next wave. But in a multiplayer game it would be possible for one player to enter the next room while the rest of his team stayed in the first room. They would then be locked out. That's where the large volume size and 'bRequiresWholeTeam' flag comes in handy. A checkpoint with that flag will not activate until all living members of a team are inside the volume's bounds.

When everyone is safely inside the second checkpoint's bounds, it will activate and trigger the event 'GoToSecondAreaObj' (this is GoToNextRoom's tag). At this point the team's progress will have been saved (if they die they will now restart from this checkpoint, not the starting one) and the next wave timer objective will be starting its countdown in preparation for the second attack.

The methods I have been describing are more or less duplicated in the final corridor of the map, so I won't go into much detail on that. There is one notable difference however.

With the final wave, I wanted to add abit more difficulty (other than including harder zeds) so I added a 'FailureCondition' to the final wave's counter objective. Failure conditions are the counterparts to Success Conditions. Essentially, they represent a way in which the player can screw up an objective. A common FailureCondition is a Time Limit. I decided that for the Final wave players would have to kill 60 Specimens in 60 seconds, or they would fail the entire objective and be forced to restart from the last checkpoint!

Here is how the failure condition looks for the final wave objective

It is important to note that Objectives do not need to have Failure conditions. In fact, most of the objectives in the maps you create probably won't. It's simply a way of putting abit of additional pressure on players and possibly creating a more interesting type of objective. Failure conditions and Success conditions can be mixed and matched without any problem. The only exception is that you can't have a TimeLimit failure condition with a Timed Success condition. I hope it's obvious why that wouldn't work :P

Here is how the final objective looks (with failure condition) in-game

When the last objective in the level rules list is completed, the game will end in victory. Unless that objective is not marked MissionCritical, or it has a SuccessAction of DoNothing. As you will probably notice (if you manage to kill 60 zombies in 60 seconds!) you will win the mission.

Anyway, I hope that all made some sense and I am really looking forward to seeing what kind of cool story maps you guys can come up with using these methods. If anyone has any questions at all, don't hesitate to add me on Skype (A_Jim_Quick) or leave a post either here, or in the main story mode thread. The more feedback I get and the more people who use my code in their maps, the more awesome I can make it

Note : You can find the map used in this tutorial in the latest story mode .zip file over here

it is called : "KFS-TestmapB" ( super imaginative, I know)