Every map has to have a map number, it's set on the impulse key of worlspawn. This was supposed to be for multiple save points originally, but that use has faded. Primarily now map numbers are used for player spawn points. If the player spawn point's 'worldtype' key matches the map number of the previous map, that is where the player will spawn. This, for example allows you to spawn by the sewer entrance when you come from the sewer map in curig2.
Making doors isn't as easy as Quake, but it's not as hard as regular hipnotic rotating stuff. The first thing you need to do is create your door brush(es). Attach them to the "rotate_object" entity.
Rotate object can have a few properties:
The next thing you need to do is either make a copy of your door, or it it's excessively detailed, a simple box shape roughly the same size will do. Then tie these brushes to func_blockwall. This entity is the blocking of the door unlike Hipnotic or Quake, doors in Prydon are on or off deals. Either the blockwall blocks the way, or it's impassible.
The blockwall can have the following values set:
Note that to set up story parameters (see Story Level on a door, set them on the func_blockwall. So in short, a door consists of these three entities: rotate_object, func_blockwall and info_null. Note that regular Quake doos aren't supported, in fact no moving BSP entities are supported. If you want some drop me a line and I'll see what I can do.
Signs are crossed between a door and an NPC. They can display a large amount of text or (more commonly) a single phrase when the cursor hovers over it. Using them is easy, simply make some brush(es) in your map into the classname "sign" (I normally don't use prefixes such as func_ etc, so it's just sign). Then set the netname key to what you want to say. netname is the universal 'mouse over text' field, by the way. If what you want to say is a lot bigger than one or two lines (at 40 characters each) then you'll need to make it a clickable sign. To do add a "message" field. Here you can put as much text (be sure to put an \n after 40 chars) as your map editor will allow. Since I use worldcraft and it's profoundly weird (I think it might be related to a QBSPe token limit also) I've also added the ability to extend the message across multiple fields. You can make another piece of the message on message1, another on message2 and another on message3.
Signs do not dynamically respond to story changes, they do however check the story level when the map starts, they just don't respond if the story level changes while on that map. See Story Level for more details.
There are four entities to place items directly into a level, the most basic of these is just "item". All other item placing entities just set up additional parameters and become 'item'. The other two are "shopitem", which has aditional code to make an item into a buyable object. The other two "magicitem" and "armoryitem" are shopitems with even more additional parms - however they also have special properities - they both will only spawn a specific class of item, magic shop stuff for magicitem and armory stuff for armoryitem.
The principle value for any item placement is the key "items" this can be any item code (see Item code generator.) In addition, and just like item drops, below, an item can have a "droprandom" field. Unlike drops, this should either be 1 or 0 since placed items do not have multiple inventory slots. droprandom is ignored on "magicitem" and "armoryitem", since these two are always randomized. Also any placed item can have a "menu" field, this will be the sale price of the item, if ever set the player must buy the object to pick it up. The "menu" field is automatically set tp the price of the item by the shopitem, armoryitem and magicitem entites.
"netname" operates something like a targetname on items, it tells Prydon Gate what 'shop' this item is part of. This is automatically set to 'wepshop' on armoryitems and 'magshop' on magicitems. You'll really only need to set this if you're creating customized shop items using the 'shopitem' entity.
Also worth noting is the first spawnflag on all items is an 'infinite flag'. Setting this means that when purchased or picked up, the item doesn't go away. This is used to create limitless supplies of arrows, spears, throwing knves, and potions in the towns. It's really irritating when someone buys the last potion, and this prevents that from ever happening.
So to recap, the "item" entity is what you should use for any generic item placement. If you want to place a specific sword by a dead body, say for example, then you'd place an item entity, grab the appropriate item code from the Item Code Generator and you'd be all set. If you wanted just any old sword, do essentially the same thing, grab a generic code from the item codes list and set droprandom to one.
"armoryitem" is the the entity you need to make 'blacksmith shops'. Put one of these in and with no real configuration you'll have a armor shop. The same rings true for magicitem.
"shoptiem" is what you need for making more advanced shops, or, recommended - a limitelss supply of heal potions. To make something like that, give the shopitem entity a items item code of 34 (taken from the list), set spawnflags to one, and viola!
Most everything in Prydon Gate can drop items. Most notably: monsters (info_class,monster_spawn), npcs, chests and barrels. This section applies to all of them. To this end everything has an inventory, just like the player. The inventory is stored in a series of fields. "slot1", "slot2", "slot3", "slot4", "slot5", "slot6", "slot7", and "slot8". These fields can contain any item code (see Item code generator.). When killed or opened, the entity will drop all items in it's inventory. So you could easily drop just a golden axe by putting it's item code in the "slot1" field. Having the same items over and over can be a bit boring though, so there's a field called 'droprandom'. Droprandom is really a bitflags field. droprandom = 1 means to randomize slot1, droprandom = 2 means to randomize slot2, droprandom = 3 means to randomize both 1 and 2. Now if drop random is set to randomize slot 1 for example and there's no item code in slot1 (0). It will either create A) A completely random item or B) Nothing at all. Actually, with droprandom there's always a chance nothing will be created. The code is limited in the number of times it can reroll until it gets a valid item setup, and if it exceeds that, the item is essentially removed. What that means in layman's terms, don't randomize anything you're counting on being there.
Story level is the basic quest mechanism in the game. The game encodes a global story level and remembers it from map to map. There's actually two active story lines at any given time, the main story line and the 'optional quest story line'. The spawning or locking of everything is compared against the story value. If lower than the story_min key on something the object is locked or not spawned, if greater than or equal to story_max, the same. This results in a odd configuration. a story min of 2 and story_max of 3 means only level 2. It was an initial mistake in the code and it has just carried over. Sorry. Note: NPCs, monsters, barrels and most other ents are not spawned. Doors & chests, are locked. If an object isn't spawned due to story constraints.
The story level can be controlled with two entities, the "storyup" entity can be used to advance the plot by it's 'lip' key or if lip is not specified, by 1. This entity is less useful than the other story control entity, storyset, but it's still supported since it was the first story entity I designed.
storyset sets the story level to whatever the lip key says. It has two spawnflags as well, the first spawnflag indicates that the story set is to ignore the mask for optional quest/main story quest, and take whatever combined value the lip is set to. This could be used to clear the side quest while advancing the main plot. Or anything like that. In short it sets the progress of both storylines simultaneously if the first spawnflag is on. The second spawnflag tells Prydon Gate to clear the selected storyline. Since storyset with a lip of 0 is considered illegal, you need to specify story level 1 for either the main or optional quest and set the second spawnflag if you want 0.
| Prefix | Item | Suffix | Qty/Dur | MAX | |
|---|---|---|---|---|---|
| Identified | |||||
| Item code: | |||||
When using drop random there's a number of item codes that may come in handy. These item codes are essentially the bare value of an item, and allows the randomizer to fill in the details.
| Name | Value |
|---|---|
| Cloth | 1 |
| Aketon | 2 |
| Chain Mail | 3 |
| Plate Mail | 4 |
| Dirk | 5 |
| Dagger | 6 |
| Sabre | 7 |
| Rapier | 8 |
| Broadsword | 9 |
| Club | 10 |
| Mace | 11 |
| Staff | 12 |
| Scepter | 13 |
| Hatchet | 14 |
| Axe | 15 |
| War Axe | 16 |
| Short Bow | 17 |
| Long Bow | 18 |
| War Bow | 19 |
| Knives | 20 |
| Buckler | 21 |
| Shield | 22 |
| Aegis | 23 |
| Skull Cap | 24 |
| Helm | 25 |
| Great Helm | 26 |
| Boots | 27 |
| Greaves | 28 |
| Amulet | 29 |
| Spears | 30 |
| Arrows | 31 |
| >Gold | 32 |
| Lesser Heal Potion | 33 |
| Heal Potion | 34 |
| Greater Heal Potion | 35 |
| Lesser Mana Potion | 36 |
| Mana Potion | 37 |
| Greater Mana Potion | 38 |
| Elixir | 39 |
| Book | 40 |
| Scroll | 41 |
| Scroll of Identify | 42 |
Note: 1024 is used by Curse of Korweh for The Eye of Kor.
| Stage | Number | Stage | Number |
|---|---|---|---|
| Main Story #1 | 1 | Optional Story #1 | 16 |
| Main Story #2 | 2 | Optional Story #2 | 32 |
| Main Story #3 | 3 | Optional Story #3 | 48 |
| Main Story #4 | 4 | Optional Story #4 | 64 |
| Main Story #5 | 5 | Optional Story #5 | 80 |
| Main Story #6 | 6 | Optional Story #6 | 96 |
| Main Story #7 | 7 | Optional Story #7 | 112 |
| Main Story #8 | 8 | Optional Story #8 | 128 |
| Main Story #9 | 9 | Optional Story #9 | 144 |
| Main Story #10 | 10 | Optional Story #10 | 160 |
| Main Story #11 | 11 | Optional Story #11 | 176 |
| Main Story #12 | 12 | Optional Story #12 | 192 |
| Main Story #13 | 13 | Optional Story #13 | 208 |
| Main Story #14 | 14 | Optional Story #14 | 224 |
| Main Story #15 | 15 | Optional Story #15 | 240 |