Difference between revisions of "Bethesda Tutorial Encounters"

1,193 bytes removed ,  19:02, 29 March 2019
m
Changed grammar from "an LvlWarlockFire" to "a LvlWarlockFire"
imported>JBurgess
imported>Leotheleopard
m (Changed grammar from "an LvlWarlockFire" to "a LvlWarlockFire")
 
(3 intermediate revisions by 2 users not shown)
Line 34: Line 34:
''Encounter'' actors (prefixed "Enc") are non-randomized characters and creatures that typically populate Leveled Lists (''EncBandit01Melee1HImperialF01/02/03/etc...''). For example, if you need a Skeever you'd just simply place an ''EncSkeever'' actor.  You always know that this placed reference will spawn a Skeever when you enter the level.  This is also the way you'd place something like a ''EncFox'', ''EncDeer'', or ''EncSabreCat''.  
''Encounter'' actors (prefixed "Enc") are non-randomized characters and creatures that typically populate Leveled Lists (''EncBandit01Melee1HImperialF01/02/03/etc...''). For example, if you need a Skeever you'd just simply place an ''EncSkeever'' actor.  You always know that this placed reference will spawn a Skeever when you enter the level.  This is also the way you'd place something like a ''EncFox'', ''EncDeer'', or ''EncSabreCat''.  


:{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
{{InDepth|Enc Actors with 'Template' in them (ex.EncBandit00Template) and anything that looks like it's part of a long list (ex. EncBandit01Melee1HImperialF) typically shouldn't be placed in your level.  These types of Enc actors are used to form Leveled Lists and should instead be placed as such (ex. LvlBanditMelee1H, or LvlBanditMeleeAny).}}
|-
|style="border-style: solid; border-width: 0"|[[Image:InDepth.jpg|48px]]
|style="border-dash: solid; border-width: 0"|Enc Actors with 'Template' in them (ex.EncBandit00Template) and anything that looks like it's part of a long list (ex. EncBandit01Melee1HImperialF) typically shouldn't be placed in your level.  These types of Enc actors are used to form Leveled Lists and should instead be placed as such (ex. LvlBanditMelee1H, or LvlBanditMeleeAny).
|}


Let's place our first encounter in Lokir's Tomb. Select an '''LvlWarlockFire''' and drag it into the second room.  With that placed in your level, save your plugin and test it in-game. You'll notice a Warlock that uses Fire Spells.  You may also notice (or not) that the Warlock will simply stand around until detecting an enemy.  Let's do something about that.
Let's place our first encounter in Lokir's Tomb. Select a '''LvlWarlockFire''' and drag it into the second room.  With that placed in your level, save your plugin and test it in-game. You'll notice a Warlock that uses Fire Spells.  You may also notice (or not) that the Warlock will simply stand around until detecting an enemy.  Let's do something about that.


:{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
{{WarningBox|Try to avoid placing enemies where they will attack the player as soon as he loads in.  Bethesda calls this the "Sandwich Rule."  It's best to assume that the player's attention will drift at every load screen - and may set the controller down, daydream, or go to get a sandwich. Observing the sandwich rule means that the player determines when to re-engage.}}
|-
|style="border-style: solid; border-width: 0"|[[Image:achtung.png]]
|style="border-style: solid; border-width: 0"|Try to avoid placing enemies where they will attack the player as soon as he loads in.  Bethesda calls this the "Sandwich Rule."  It's best to assume that the player's attention will drift at every load screen - and may set the controller down, daydream, or go to get a sandwich. Observing the sandwich rule means that the player determines when to re-engage.  
|}


==Linked-Refs and Patrols==
==Linked-Refs and Patrols==
Line 64: Line 56:
# If you don't put a time here the Warlock will simply walk up to the table, interact with it, then back out of it and just stand there. Giving a patrol time here ensures the Warlock will stay at the table in perpetuity since there are no other references in the patrol for now.
# If you don't put a time here the Warlock will simply walk up to the table, interact with it, then back out of it and just stand there. Giving a patrol time here ensures the Warlock will stay at the table in perpetuity since there are no other references in the patrol for now.


:{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
{{InDepth|Link-Refs are ways of letting one reference know about another. This is a "dumb" connection, and carries no data beyond a simple association.  This lets us assign whatever meaning we need to that association.  In the case of this tutorial, they help the actor know what he can patrol to, because the [[Default_Master_Package|Default Master Package]] looks for the association .  They're also very powerful when it comes to referring to them in [[:Category:Papyrus|Papyrus]] Scripts.}}
|-
|style="border-style: solid; border-width: 0"|[[Image:InDepth.jpg|48px]]
|style="border-style: solid; border-width: 0"|Link-Refs are ways of letting one reference know about another. This is a "dumb" connection, and carries no data beyond a simple association.  This lets us assign whatever meaning we need to that association.  In the case of this tutorial, they help the actor know what he can patrol to, because the [[Default_Master_Package|Default Master Package]] looks for the association .  They're also very powerful when it comes to referring to them in [[:Category:Papyrus|Papyrus]] Scripts.
|}


<gallery widths="220px" heights="120px" perrow="3">
<gallery widths="220px" heights="120px" perrow="3">
Line 120: Line 108:
Try running this in-game.  Observe the difference: instead of re-tracing steps, the Necromancer should continue in a loop, with the skeleton staying a small distance behind.
Try running this in-game.  Observe the difference: instead of re-tracing steps, the Necromancer should continue in a loop, with the skeleton staying a small distance behind.


:{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
{{ProTip|PatrolIdleMarker is an '''[[IdleMarker|Idle Marker]]''' which already has a range of subtle animations associated with it.  This makes it preferable to other objects, such as an XmarkerHeading, when setting up patrols.  There are also other [[IdleMarker|Idle Markers]] available, such as '''SearchingTableIdleMarker ''' and '''WarmHandsStandIdleMarker ''', which can be used to trigger specific animations which are more deliberate and grounded with the environment.  Try swapping some of your patrolIdleMarker objects with these and experiment to get results you're happy with.}}
|-
|style="border-style: solid; border-width: 0"|[[Image:Protip.jpg|48px]]
|style="border-style: solid; border-width: 0"|PatrolIdleMarker is an '''[[IdleMarker|Idle Marker]]''' which already has a range of subtle animations associated with it.  This makes it preferable to other objects, such as an XmarkerHeading, when setting up patrols.  There are also other [[IdleMarker|Idle Markers]] available, such as '''SearchingTableIdleMarker ''' and '''WarmHandsStandIdleMarker ''', which can be used to trigger specific animations which are more deliberate and grounded with the environment.  Try swapping some of your patrolIdleMarker objects with these and experiment to get results you're happy with.
|}


==Setting Actor Difficulty==
==Setting Actor Difficulty==
Line 136: Line 120:
It's a good rule of thumb to set about 50% of your leveled actors to "easy", and not throw too many non-easy actors into any single encounter.  It's also generally advised to place only one "very hard" list per dungeon.  These, of course, are only guidelines, and may not always be the best course.  Test your content mercilessly, get feedback from players, and tune according to that.
It's a good rule of thumb to set about 50% of your leveled actors to "easy", and not throw too many non-easy actors into any single encounter.  It's also generally advised to place only one "very hard" list per dungeon.  These, of course, are only guidelines, and may not always be the best course.  Test your content mercilessly, get feedback from players, and tune according to that.


:{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
{{InDepth|The relative difficulty of an encounter is based upon the [[Encounter Zone]], player level and the leveled list itself.  So, for example, a level one player who enters a dungeon with an encounter zone of twenty may encounter very difficult draugr, even from the easy leveled lists.  Try testing your dungeon by [[IncrementPCSkill|setting yourself to different levels]] before entering.}}
|-
|style="border-style: solid; border-width: 0"|[[Image:InDepth.jpg|48px]]
|style="border-style: solid; border-width: 0"|The relative difficulty of an encounter is based upon the [[Encounter Zone]], player level and the leveled list itself.  So, for example, a level one player who enters a dungeon with an encounter zone of twenty may encounter very difficult draugr, even from the easy leveled lists.  Try testing your dungeon by [[IncrementPCSkill|setting yourself to different levels]] before entering.
|}


<gallery>
<gallery>
Line 149: Line 129:
</gallery>
</gallery>


{{Template:Tutorial_Bottom_Bar
{{Tutorial_Bottom_Bar
|Prev=Bethesda_Tutorial_Navmesh
|Prev=Bethesda_Tutorial_Navmesh
|Next=Bethesda_Tutorial_Traps_and_Prefabs
|Next=Bethesda_Tutorial_Traps_and_Prefabs
}}
}}
{{Languages}}