Worst-case scenario: the UEd Goblin wipes the map and burns down your house.
Search results
From Unreal Wiki, The Unreal Engine Documentation Site
Create the page ""NavigationPoint (UT)"" on this wiki! See also the search results found.
Page title matches
- {{classbox| [[Legacy:UT|UT]] :: [[Legacy:Actor (UT)|Actor (UT)]] >> NavigationPoint (Package: Engine)}} ...ould go there at least in one direction. Each [[Legacy:Pickup (UT)|Pickup (UT)]] and [[Legacy:PlayerStart|PlayerStart]] has its own NavigationPoint. The6 KB (746 words) - 15:40, 11 April 2015
-
6 KB (716 words) - 10:11, 17 May 2008
Page text matches
- ...:Actor (UT)|Actor (UT)]] >> [[Legacy:NavigationPoint (UT)|NavigationPoint (UT)]] >> AlarmPoint (Package: Engine)}} ...usage, I made educated guesses as to the property type, but I do not have UT to check against. If incorrect, please fix.3 KB (427 words) - 16:26, 21 April 2006
- ...:Actor (UT)|Actor (UT)]] >> [[Legacy:NavigationPoint (UT)|NavigationPoint (UT)]] >> AlternatePath (Package: Botpack)}} and a snip from the UT AI article:7 KB (1,187 words) - 18:28, 20 July 2013
- ...:Actor (UT)|Actor (UT)]] >> [[Legacy:NavigationPoint (UT)|NavigationPoint (UT)]] >> AmbushPoint (Package: Engine)}} ...ationPoint (UT)|NavigationPoint (UT)]] upon which a [[Legacy:Bot (UT)|Bot (UT)]] will stop. Whether a bot stops will depend on how healthy it is, if it i1 KB (213 words) - 19:53, 27 January 2006
- {{classbox| [[Legacy:UT|UT]] :: [[Legacy:Object (UT)|Object (UT)]] >> Actor (Package: Engine)}} ...|bot]]s, [[Legacy:Light (UT)|light]]s and [[Legacy:Triggers (UT)|Triggers (UT)]]. This is an important class because it's the base class for all in-game3 KB (465 words) - 01:50, 7 April 2006
- ...uty and glory. The Actor class inherits from [[Legacy:Object (UT)|Object (UT)]]. There are a whole host of non actor classes that might get added in he ...e, for example: Effects are expanded on the [[Legacy:Effects (UT)|Effects (UT)]] class page anyway; with Decoration it's worth marking as you have that t19 KB (1,790 words) - 00:29, 28 May 2007
- ...:Actor (UT)|Actor (UT)]] >> [[Legacy:NavigationPoint (UT)|NavigationPoint (UT)]] >> AssaultRandomizer (Package: Botpack)}} ...ff by being triggered, and the cost only applies to [[Legacy:Bot (UT)|Bot (UT)]]s on the attacking team.929 B (129 words) - 15:34, 11 April 2015
- ...:Actor (UT)|Actor (UT)]] >> [[Legacy:NavigationPoint (UT)|NavigationPoint (UT)]] >> BlockedPath (Package: BotPack)}} [[Category:Legacy Class (UT)|{{PAGENAME}}]]1 KB (141 words) - 01:54, 18 November 2007
- ...:Actor (UT)|Actor (UT)]] >> [[Legacy:NavigationPoint (UT)|NavigationPoint (UT)]] >> ControlPoint}} * [[Legacy:Mapping For DOM|Mapping for DOM]] (UT)2 KB (400 words) - 14:50, 20 January 2006
- ...:Actor (UT)|Actor (UT)]] >> [[Legacy:NavigationPoint (UT)|NavigationPoint (UT)]] >> [[Legacy:AmbushPoint|AmbushPoint]] >> DefensePoint (Package: Botpack) [[Category:Legacy Class (UT)|{{PAGENAME}}]]2 KB (319 words) - 18:30, 9 February 2006
- ...:Actor (UT)|Actor (UT)]] >> [[Legacy:NavigationPoint (UT)|NavigationPoint (UT)]] >> [[Legacy:Teleporter|Teleporter]] >> DelayedTeleporter}} ...as no effect anymore. (like the [[Legacy:YawTeleporter|YawTeleporter]] for UT)5 KB (728 words) - 16:07, 18 November 2007
- ...:Actor (UT)|Actor (UT)]] >> [[Legacy:NavigationPoint (UT)|NavigationPoint (UT)]] >> [[Legacy:Teleporter|Teleporter]] >> DelayedTeleporter (Code)}}5 KB (574 words) - 15:43, 25 November 2006
- ...:Actor (UT)|Actor (UT)]] >> [[Legacy:NavigationPoint (UT)|NavigationPoint (UT)]] >> HomeBase (Package: Engine)}} ...part of the [[Legacy:ScriptedPawn|ScriptedPawn]] family of NavPoints that UT mappers used to help define the AI for NPCs and Bots. In terms of organiza2 KB (279 words) - 07:39, 6 March 2011
- ...:Actor (UT)|Actor (UT)]] >> [[Legacy:NavigationPoint (UT)|NavigationPoint (UT)]] >> InventorySpot (Package: Engine)}} ...d by the editor for every [[Legacy:Inventory (UT)|Inventory (UT)]] item in UT or [[Legacy:Pickup|Pickup]]/[[Legacy:XPickUpBase|xPickUpBase]] in UT2003. T1 KB (133 words) - 13:56, 2 September 2004
- ...nPoint (UT)|NavigationPoint (UT)]] >> [[Legacy:LiftCenter (UT)|LiftCenter (UT)]] >> JumpSpot}} ...imes be finetuned between the starting ("ground floor") [[Legacy:LiftExit (UT)|LiftExit]] and the JumpSpot. Often it needs to be in the apex for two-way3 KB (453 words) - 10:52, 19 January 2016
- ...:Actor (UT)|Actor (UT)]] >> [[Legacy:NavigationPoint (UT)|NavigationPoint (UT)]] >> LiftCenter}} These are used in a similar fashion with [[Legacy:LiftExit (UT)|LiftExit (UT)]] to create different types of path.2 KB (221 words) - 16:17, 5 September 2015
- ...:Actor (UT)|Actor (UT)]] >> [[Legacy:NavigationPoint (UT)|NavigationPoint (UT)]] >> LiftExit (Package: Engine)}} ...ding a lift. It works together with a [[Legacy:LiftCenter (UT)|LiftCenter (UT)]] actor. See [[Legacy:Pathing Lifts|Pathing Lifts]] for full details on ho980 B (138 words) - 23:32, 29 March 2004
- ...:Actor (UT)|Actor (UT)]] >> [[Legacy:NavigationPoint (UT)|NavigationPoint (UT)]] >> [[Legacy:ControlPoint|ControlPoint]]}}4 KB (754 words) - 14:32, 18 November 2005
- {{classbox| [[Legacy:UT|UT]] :: [[Legacy:Actor (UT)|Actor (UT)]] >> [[Legacy:Brush|Brush]] >> Mover (Package: Engine)}} In UT '''Movers''' are brushes that move. They are not part of the [[Legacy:BSP|B17 KB (2,517 words) - 18:28, 9 November 2016
- ''See also [[Legacy:NavigationPoint (UT)|NavigationPoint (UT)]] for the Unreal Tournament class.''10 KB (1,300 words) - 07:39, 27 July 2007
- ...:Actor (UT)|Actor (UT)]] >> [[Legacy:NavigationPoint (UT)|NavigationPoint (UT)]] >> PathNode (Package: Engine)}} ...([[Legacy:Inventory (UT)|Inventory (UT)]] and [[Legacy:Pickup|Pickup]] for UT and UT200x respectively) instead of pathnodes.2 KB (222 words) - 09:01, 27 July 2007