If you take a look at the entity list you will see that there are lots of 'monster' entities. Now that you have created a simple map you probably want to know how to get it to interact with the player (or in other words, put in something to blow away). While it can be fun running around looking at great scenery and impressive detail, it becomes boring after a while. So this tutorial is a really basic guide to placing monster entities.
First up, we are going to look at how a
can make a map interesting. Use your entity tool to place a
in the second room. Leave all of his properties as default. Run the map, pick up the crowbar and go to Barney. First up try getting him to follow you into the other room with the Use
key. If that isn't successful give him whack on the forehead with the crowbar. Now run back into the other room.
A couple of things you have probably noticed already: getting him to follow you was like pulling teeth and then once you had banged him on the head, he pulled out his gun but didn't chase you. Main reason for this is that poor old Barney didn't know where to go.
Barney is one of the monster entities that will follow
s as well as
s. To get Barney to chase you into the next room, he needs a map.
s provide Barney with a path to follow. Same as you would place a normal entity, place an
at the entrance to the corridor, one in the middle and one at the other end.
s are shown here as yellow squares. It doesn't matter how high of the ground you put them as the game engine always drops them down to 8 units off the floor; what does matter is where you put them. I have placed these nodes just 3 units from each corridor wall. This really isn't a good thing as it is better to place them a minimum of 24 units from walls or any other brush in your map. Included in the download is a small text file that was part of the original Wordcraft tutorials, which includes good information about placement.
If you compile the map now and talk to Barney with the Use
key and move into the other room he should follow you down the corridor. If you hit him with the crowbar, he will draw his gun and come looking for you. [Note that
s are not interchangable: the former are used by all monsters that need to act on AI, and move dynamically, while the latter are used to specify movements - Barney will follow the
s until you bash him, and then he will rely on the
s to hunt you down.]
s work with flying monsters like the
You can get Barney to follow
entities as though he was checking security. Just place one at each end of the corridor (In their properties name them p1
and set their next stop targets
. In this case p1
with a next stop of p2
with a next stop of p1
). In Barney's properties, change his Target
. If you compile the map now and don't move, Barney will be walking up and down the corridor. If you approach him, he will stop following the
s. All monsters do this to some extent.
s behave in pretty much the same way and you can make them follow
s behave slightly differently. First of all you don't really interact with them, you try to kill them. So the main thing is to decide if you want them to chase after the player. If so,
placement is important (and reading the file included with the example map for this tutorial will save time). A good coverage of
s (maximum 128 visible at any point) within a room will make it impossible for the player to hide. The grunts will attack until killed, or you get capped, whichever is first.
In the Flag properties, checking WaitTillSeen
will make the monster stand there until the player sees him, then he will revert to his normal AI (This will not work if the monster is following
s). Checking Gag
will shut them up. This means that the player will not know they are around the corner. Checking Prisoner
for any monster entity will stop the monster from attacking the player. You can use monsters to activate or deactivate things by entering the name of the target you want to trigger in Trigger Target
. There are Trigger Conditions
that can be set and are pretty much self-explanatory [Ok, well maybe not, it seems that some of the conditions are redundant. So test each one.] One of the things that can be done is to trigger a monstermaker
entity. By using this trigger, the new monsters don't appear until the Trigger Condition
is met. Monstermakers
are a tutorial in their own right, there is so much you can do with them. If you try them out, just remember to change the Angle
of the entity so that the monsters it produces face the player or the
path when they appear. If you don't they will appear and end up looking at the walls, not doing much until the player attacks.
I have included a test room map to show how info nodes, Trigger Conditions
entities work. Kill the first
and watch the fun start. One last note: There are so many things you can do with monsters. Some of them can be used in conjunction with
s which is outside the scope of this tutorial, but set up a test map, and check out what the different flags and properties of monsters do. It pays to be in God Mode when working with monsters. Remember that monsters that wait to get shot at are boring so get them to do something! And also, too many monsters can ruin the pace of play.
Now you're an "Expert mapper" like Atom, SlayerA and me! Well, better than me, but not quite as good as the other guys.
Try: Tutorial: Dimensions
to help you make it look right.
Try: Tutorial: Environment
to get the sky right.
Try: Tutorial: Dark Outdoor Maps
to add the night feel..
Try: Tutorial: Compiling Introduced
to make the most of your compile.
Try: Tutorial: How to load a map (.bsp file) in-game
to help you run the .bsp you have created.
Have fun, and remember that if you have questions or comments you can let us know through the forums.