UE3:Mapping for Jailbreak (UT3) - Revision history

Wormbo: /* Jail setup */ wrong class name

2009-11-15T19:05:50Z

‎Jail setup: wrong class name

Wormbo: /* Jail Status */ the "Jail Doors" variable link was renamed to "Exit Markers" in beta 2

2009-11-13T20:35:14Z

‎Jail Status: the "Jail Doors" variable link was renamed to "Exit Markers" in beta 2

Wormbo: made TOC right-floated

2009-11-13T20:30:52Z

made TOC right-floated

Wormbo: /* Jail Status */ clarified blocking requirement for Jail Doors and corresponding DoorMarker setting

2009-09-13T20:13:40Z

‎Jail Status: clarified blocking requirement for Jail Doors and corresponding DoorMarker setting

Wormbo: /* JBKillZVolume */ fixed link: it's actually UTKillZVolume

2009-09-12T17:32:53Z

‎JBKillZVolume: fixed link: it's actually UTKillZVolume

Wormbo: /* Jailbreak-specific Kismet actions */ added actions and short descriptions

2009-09-09T20:47:32Z

‎Jailbreak-specific Kismet actions: added actions and short descriptions

Wormbo: /* Reference */ added Kismet conditions

2009-09-09T07:45:41Z

‎Reference: added Kismet conditions

Wormbo: /* Jailbreak-specific Kismet events */ added event descriptions

2009-09-08T11:28:43Z

‎Jailbreak-specific Kismet events: added event descriptions

Wormbo: added info about PIE and JB testing mutator

2009-09-07T20:33:56Z

added info about PIE and JB testing mutator

Wormbo: /* Reference */ added actors

2009-09-07T19:20:23Z

‎Reference: added actors

@@ Line 44: / Line 44: @@
 Jail areas are defined with volumes associated to a [[#JBInfoJail|JBInfoJail]], a subclass of [[UE3:Info (UT3)|Info]]. Any kind of volume can be used, but the preferred type is [[#JBVolumeJail|JBVolumeJail]], because it prevents players from using the Translocator to escape. The names of the volumes can be entered in the JailVolumes list of the JBInfoJail, but a much easier way is to use Kismet. The JBInfoJail actor has a Kismet event called [[#Jail Status|Jail Status]], which controls most of the jail functionality. That Jail Status event can be used to assign volumes to the jail as well.
-Jails are not owned by any team directly. To ensure only players of one team are put in a jail, simply place [[UE3:UTPlayerStart (UT3)|UTPlayerStart]]s for that specific team inside any of the volumes assigned to the JBInfoJail. There's a property called ''bReleasesBothTeams'' in JBInfoJail that should have the value ''True'' in most cases. Only set it to ''False'' if your jail prevents the opposite team from leaving this jail, for example if you have a shared jail with separate exits for both teams. Keep in mind that regular jails allow people to walk in while the door is open. Such jails, even though designed to only contain one team's players, should allow the enemy player to get out as well while the jail is open.
+Jails are not owned by any team directly. To ensure only players of one team are put in a jail, simply place [[UE3:UTTeamPlayerStart (UT3)|UTTeamPlayerStart]]s for that specific team inside any of the volumes assigned to the JBInfoJail. There's a property called ''bReleasesBothTeams'' in JBInfoJail that should have the value ''True'' in most cases. Only set it to ''False'' if your jail prevents the opposite team from leaving this jail, for example if you have a shared jail with separate exits for both teams. Keep in mind that regular jails allow people to walk in while the door is open. Such jails, even though designed to only contain one team's players, should allow the enemy player to get out as well while the jail is open.
 ===Release setup===

@@ Line 199: / Line 199: @@
 '''Variables:'''
 :;Jail Volumes (in): The volumes making up the jail arena. Volumes from all Jail Status events are merged with the JailVolumes list of the JBInfoJail actor.
-:;Jail Doors (in): The [[UE3:NavigationPoint (UT3)|NavigationPoint]]s marking exit locations of this jail. Make absolutely sure these NavPoints are initially blocked, otherwise the game considers the jail open all the time. This manifests in the release switch not working and the round not ending despite all players being captured. If you use a [[UE3:DoorMarker (UT3)|DoorMarker]], make sure you set ''bBlockedWhenClosed'' to ''True''. If a ''ReleasingTeam'' other than -1 is specified, the jail exit marker is used only for that team.
+:;Exit Markers (in): The [[UE3:NavigationPoint (UT3)|NavigationPoint]]s marking exit locations of this jail. Make absolutely sure these NavPoints are initially blocked, otherwise the game considers the jail open all the time. This manifests in the release switch not working and the round not ending despite all players being captured. If you use a [[UE3:DoorMarker (UT3)|DoorMarker]], make sure you set ''bBlockedWhenClosed'' to ''True''. If a ''ReleasingTeam'' other than -1 is specified (strongly recommended), the jail exit marker is used only for that team.<br/>(This variable link was formerly called "Jail Doors", but had the same meaning.)
 :;Releaser (out): The player who activated the release switch. Might be empty if the release was activated via script.
 :;Release Switch (out): The JBObjectiveRelease actor used to activate this jail. Use this to distinguish between the different switches if this jail is associated to more than one switch, e.g. because it has an alternate escape route.

← Older revision		Revision as of 20:30, 13 November 2009
Line 1:		Line 1:
		+	<div style="float:right;">__TOC__</div>
	This article gives an overview about how to create maps for the custom UT3 gametype [http://jailbreak.beyondunreal.com/ Jailbreak].		This article gives an overview about how to create maps for the custom UT3 gametype [http://jailbreak.beyondunreal.com/ Jailbreak].

@@ Line 198: / Line 198: @@
 '''Variables:'''
 :;Jail Volumes (in): The volumes making up the jail arena. Volumes from all Jail Status events are merged with the JailVolumes list of the JBInfoJail actor.
-:;Jail Doors (in): The [[UE3:NavigationPoint (UT3)|NavigationPoint]]s marking exit locations of this jail.
+:;Jail Doors (in): The [[UE3:NavigationPoint (UT3)|NavigationPoint]]s marking exit locations of this jail. Make absolutely sure these NavPoints are initially blocked, otherwise the game considers the jail open all the time. This manifests in the release switch not working and the round not ending despite all players being captured. If you use a [[UE3:DoorMarker (UT3)|DoorMarker]], make sure you set ''bBlockedWhenClosed'' to ''True''. If a ''ReleasingTeam'' other than -1 is specified, the jail exit marker is used only for that team.
 :;Releaser (out): The player who activated the release switch. Might be empty if the release was activated via script.
 :;Release Switch (out): The JBObjectiveRelease actor used to activate this jail. Use this to distinguish between the different switches if this jail is associated to more than one switch, e.g. because it has an alternate escape route.

@@ Line 118: / Line 118: @@
 ===Jailbreak-specific volumes===
 ====JBKillZVolume====
-A [[UE3:KillZVolume (UT3)|KillZVolume]] that only affects specific classes.
+A [[UE3:UTKillZVolume (UT3)|UTKillZVolume]] that only affects specific classes.
 ====JBLadderVolume====

@@ Line 217: / Line 217: @@
 ===Jailbreak-specific Kismet actions===
-{{sectstub}}
+{{expand}}
 ===Jailbreak-specific Kismet conditions===

@@ Line 87: / Line 87: @@
 ==Reference==
 ===Jailbreak-specific actors===
@@ Line 218: / Line 217: @@
 ===Jailbreak-specific Kismet actions===
 ===Jailbreak-specific Kismet conditions===
 [[Category:Mapping tutorials|Jailbreak UT3 Mapping]]

@@ Line 145: / Line 145: @@
 A permanent version of the [[liandri:X-Ray Field|X-Ray Field]], but without the inverted vision effect. (It's up to the mapper to provide visual effects.)
-===Jailbreak-specific Kismet objects===
+===Jailbreak-specific Kismet events===
 [[Category:Mapping tutorials|Jailbreak UT3 Mapping]]

@@ Line 1: / Line 1: @@
-This article gives a short overview about how to create maps for the custom UT3 gametype [http://jailbreak.beyondunreal.com/ Jailbreak].
+This article gives an overview about how to create maps for the custom UT3 gametype [http://jailbreak.beyondunreal.com/ Jailbreak].
-{{expand}}
-==Getting started==
+==Preparing the UT3 Editor==
-Before you start diving into the editor, get the latest version of UT3 Jailbreak first. (See sticky release threads for the download link.) You'll be needing actors and Kismet objects from the Jailbreak.u and JailbreakContent.u packages (and possibly from JailbreakTitanContent.u as well, depending on your map) to set up Jailbreak-specific things in your map. To load them automatically, open your UTEditor.ini (''MyDocs\MyGames\UT3\UTGame\Config''), find the <code>[ModPackages]</code> section and add the following lines to it:
+Before you start diving into the editor, make sure you have the latest version of UT3 Jailbreak installed. You'll be needing actors and Kismet objects from the Jailbreak.u and JailbreakContent.u packages (and possibly from JailbreakTitanContent.u as well, depending on your map) to set up Jailbreak-specific things in your map. To load them automatically, open your UTEditor.ini (''MyDocs\MyGames\UT3\UTGame\Config''), find the <code>[ModPackages]</code> section and add the following lines to it:
 <pre>
 ModPackages=Jailbreak
@@ Line 11: / Line 10: @@
 Now you can open the editor and map right away. See [[Legacy:Mapping For Jailbreak|Spoondog's Guide to Mapping for Jailbreak]] for general considerations about Jailbreak maps, but keep in mind that it was written for JB2004.
 As always in [[UT3]] it's probably better to start out additive, i.e. with an empty world, because it saves you a lot of time when rebuilding lighting. If your Jailbreak map is going to be indoor, just add a cube of about the size your map will be and start subtracting from that.
 The first thing you should probably do when you start a new Jailbreak map is setting up the map info: