Difference between revisions of "Delivery Missions (Game Mechanics)"

From SWGANH Wiki
Jump to: navigation, search
(→‎Game Mechanics)
(→‎System Messages)
 
(18 intermediate revisions by the same user not shown)
Line 50: Line 50:
 
{| align="center"
 
{| align="center"
 
|-
 
|-
−
||{{D0%}}
+
||{{D25%}}
 
|-
 
|-
 
||{{GameMechanics}}
 
||{{GameMechanics}}
Line 56: Line 56:
 
|}
 
|}
 
|}
 
|}
 +
 +
== System Messages ==
 +
 +
* [[Delivery Missions (Game Messages)|Delivery Missions]]
 +
 +
 +
== Dialogue Responses ==
 +
 +
* [[Delivery Dialogue Response (Game Messages)|Delivery Dialogue Response]]
  
 
== Game Mechanics ==
 
== Game Mechanics ==
  
  
−
Delivery missions are missions that the player can take that require them to retrieve a message from the mission giver and then deliver that to another npc. Delivery missions work in two parts:
+
Delivery missions are missions that the player can take that require them to retrieve a message from the mission giver and then deliver that to another npc. Delivery missions may be picked up from the Delivery tab on Mission Terminals or from mission giving npcs. Delivery missions have two stages:
  
 
* Acquiring the message
 
* Acquiring the message
 
* Delivering the message  
 
* Delivering the message  
 +
  
 
When the player picks up the mission from the terminal they are given a waypoint to the mission giver's cordinates. The player then goes to this npc, uses the converse radial menu with it and then the npc will update the player's waypoint to the delivery point location. Both the mission giver and the delivery target are considered delivery mission targets.
 
When the player picks up the mission from the terminal they are given a waypoint to the mission giver's cordinates. The player then goes to this npc, uses the converse radial menu with it and then the npc will update the player's waypoint to the delivery point location. Both the mission giver and the delivery target are considered delivery mission targets.
Line 90: Line 100:
 
For a listing of commoner spawn see: [[Commoner NPC Loactions (Game Mechanics)|Commoner NPC Locations]]
 
For a listing of commoner spawn see: [[Commoner NPC Loactions (Game Mechanics)|Commoner NPC Locations]]
  
 +
 +
 +
The destination point for delivery missions can be any one of three types:
 +
 +
* Delivery point within the same city as the mission giver
 +
* Delivery point on the same planet but different city
 +
* Delivery point on a different planet and randomly selected city
  
 
Once the delivery point has been reached then the player uses the converse radial option again and the mission will be flagged as completed and the player rewarded.
 
Once the delivery point has been reached then the player uses the converse radial option again and the mission will be flagged as completed and the player rewarded.
Line 95: Line 112:
  
 
Note: Players who interact with commoner npcs without a mission or without a mission that links to that particular npc will receive a [[media:CommonerResponse.jpg|randomly selected statement]] from the npc informing them that they have no business with the player.
 
Note: Players who interact with commoner npcs without a mission or without a mission that links to that particular npc will receive a [[media:CommonerResponse.jpg|randomly selected statement]] from the npc informing them that they have no business with the player.
 +
  
 
<br><br>
 
<br><br>
Line 102: Line 120:
  
 
The following is a list of stfs that contain mission terminal delivery mission data:
 
The following is a list of stfs that contain mission terminal delivery mission data:
−
 
−
'''Imperial Faction Terminals:'''
 
−
 
−
 
−
* mission_deliver_imperial_easy.stf
 
−
* mission_deliver_imperial_medium.stf
 
−
* mission_deliver_imperial_hard.stf
 
−
 
−
'''Imperial Faction Mission Giving NPCs'''
 
−
 
−
 
−
* mission_deliver_imperial_easy_non_persistent_from_npc.stf
 
−
* mission_deliver_imperial_hard_non_persistent_from_npc.stf
 
−
* mission_deliver_imperial_medium_non_persistent_from_npc.stf
 
−
 
−
'''Rebel Faction Terminals:'''
 
−
 
−
 
−
* mission_deliver_rebel_easy.stf
 
−
* mission_deliver_rebel_medium.stf
 
−
* mission_deliver_rebel_hard.stf
 
−
 
−
 
−
'''Rebel Faction Mission Giving NPCs'''
 
−
 
−
 
−
* mission_deliver_rebel_easy_non_persistent_from_npc.stf
 
−
* mission_deliver_rebel_medium_non_persistent_from_npc.stf
 
−
* mission_deliver_rebel_hard_non_persistent_from_npc.stf
 
  
  
Line 136: Line 125:
  
  
−
* mission_deliver_neutral_easy.stf
+
* /mission/mission_deliver_neutral_easy.stf
−
* mission_deliver_neutral_medium.stf
+
* /mission/mission_deliver_neutral_medium.stf
−
* mission_deliver_neutral_hard.stf
+
* /mission/mission_deliver_neutral_hard.stf
  
  
Line 147: Line 136:
 
== Analysis of Mission Datapad Details ==
 
== Analysis of Mission Datapad Details ==
  
−
* [[media:CraftingMission10.jpg|Crafting Mission in datapad]]
+
* [[media:DeliveryMission6.jpg|Delivery Mission in datapad]]
  
 
== Analysis of Mission Details ==
 
== Analysis of Mission Details ==
Line 165: Line 154:
 
'''Item'''
 
'''Item'''
  
−
The item detail lists the item that is needed to complete the mission. A player may turn in that particular item to the destination npc once it has been crafted. The item that is requested to be made is randomized for each mission.
 
  
−
Note: The source of the item doesnt matter. A player can craft an item from a previous mission, abort the mission and keep the item and turn the item in for credit on a new mission.
+
Note: This  no longer has a function. Delivery missions at one point were intended to deliver a physical item between the pick up npc and the destination point however this was scrapped some time after launch. A number of mission files still contain the old information for these mission types however.
 +
 
 +
Presumably the way this worked was that The item detail lists the item that is needed to complete the mission. A player may turn in that particular item to the destination npc once it has been picked up.
 +
 
  
  
Line 175: Line 166:
 
'''Start'''
 
'''Start'''
  
−
This is the coordinate of the starting npc that will upload the Item schematic to the player as well as give them components necessary to build it. Starting npcs are always commoners randomly selected from the commoner node points within the town that the mission terminal belongs to. Commoner nodes are spawn points where commoner npcs are found. The server chooses randomly which point will be used as a starting point within the selected town. Starting locations are always begun on the same planet as the mission giver. If a player acquires a crafting mission within a player city then the start location will be one of the following fixed locations (depending on which planet the player is on):
+
This is the coordinate of the starting npc that will update the player's waypoint coordinates to the destination point. Starting npcs are always commoners randomly selected from the commoner node points within the town that the mission terminal belongs to. Commoner nodes are spawn points where commoner npcs are found. The server chooses randomly which point will be used as a starting point within the selected town. Starting locations are always begun on the same planet as the mission giver. If a player acquires a delivery mission within a player city then the start location will be one of the following fixed locations (depending on which planet the player is on):
  
 
* mos entha
 
* mos entha
Line 184: Line 175:
 
* coronet
 
* coronet
 
* nym's outpost
 
* nym's outpost
−
 
−
 
−
 
−
Players receive one of 5 schematics when they interact with the starting npc:
 
−
 
−
* [[Attunement Grid (Schematic)|Attunement Grid]]
 
−
* [[Current Alternator (Schematic)|Current Alternator]]
 
−
* [[Feedback Controller (Schematic)|Feedback Controller]]
 
−
* [[Output Governor (Schematic)|Output Governor]]
 
−
* [[Output Regulator (Schematic)|Output Regulator]]
 
−
 
−
Note: Players keep the item's schematic so long as they still have the mission. If the player completes the mission or it is aborted, then the schematic is removed from the player's datapad.
 
  
  
Line 204: Line 183:
 
'''Destination'''
 
'''Destination'''
  
−
This is the coordinate of the npc that the player is to take the completed Item to in order to receive credit for the mission. Destination locations for crafting missions are always in a different city than where the start location originates and are always on the planet where the mission giver is. Destination targets are always commoners randomly selected from the commoner node points within a town. Commoner nodes are spawn points where commoner npcs are found. The server chooses randomly which point will be used as a destination point within the selected town.
+
This is the coordinate of the npc that the player is to go to in order to receive credit for the mission. Destination locations for delivery missions are randomly selected between towns to select npc nodes to choose from. Destinations can be any planet and town that has commoner npc nodes. Destination targets are always commoners randomly selected from the commoner node points within a town. Commoner nodes are spawn points where commoner npcs are found. The server chooses randomly which point will be used as a destination point within the selected town.
  
  
 
'''Creator'''
 
'''Creator'''
  
−
The creator of the mission is always the name of the destination location npc.
+
The creator of the mission is randomly generated, unless its a mission giving npc then the mission takes the name of the npc that gave it.
  
  
 
'''Reward'''
 
'''Reward'''
  
−
This is the payout to the player in credits for successfully completing the mission. Reward is only given out if the player turns in the item to the destination npc by dragging and dropping the item on top of it. Mission payout reward formula is currently unknown.
+
This is the payout to the player in credits for successfully completing the mission. Reward is only given out if the player interacts with the destination npc by using the converse radial options. Mission payout reward formula is currently unknown.
  
  
 
'''Difficulty'''
 
'''Difficulty'''
  
−
Crafting missions are always difficulty 1.
+
Note: Difficulty rating on missions seems to be random between 1-3 for some reason without any discernable causes. I believe we should stream line this to reflect how the mission mechanics work.
 +
 
 +
A proposal is this:
 +
 
 +
Mission difficulty ratings rank from 1-3 where mission ranking 1 refers to same city missions, mission ranking 2 refers to locations on the same planet but different city, and rank 3 missions refer to off world missions.
  
 
<br><br>
 
<br><br>
  
−
== Crafting Mission STF Analysis ==
+
== Mission Terminal Delivery Mission STF Analysis ==
  
−
The following is an example taken from the mission_npc_crafting_neutral_easy file for crafting missions. An overview for how to properly read and interpret the stf file will be included further below.
+
The following is an example taken from the mission_deliver_neutral_easy.stf file for delivery missions. An overview for how to properly read and interpret the stf file will be included further below.
  
  
  
−
m10d One of my clients is headed for Iskallon and wants to commission a custom sonic weapon. This rifle will need a specialized amplification chamber. I've got the specs for it right here, but I don't have the time to assemble all the parts. If you think you can lend a hand, I'd reward your service. Pick up the components from my supplier.
 
  
−
m10p Iskallon is a water world, I believe. Makes sense. These sonic weapons are much more effective underwater. Here are the parts. When you're finished assembling the part deliver it to the customer. Good luck with it.
+
m10d -
  
−
m10r Excellent work, citizen. I think this will aid my mission rather well. Tell the engineer I'll deliver a status report when I get back.
+
My new solo recording of kloo-horn pieces, including an all-new rendition of the classic "Soaring Banthas at Sunset," is finished. But I need someone to hand-deliver it to my sound engineer. I don't trust HoloNet compression routines, you know, they're lossy algorithms that ruin the tone. I'm kind of distracted by a personal crisis, so I really need these tracks taken quick. Be a friend, huh? You'll love the guys at the mastering joint, they're smooth.
  
−
m10s Sounds like you did a fine job. I've deposited your fee, and I think you'll find it quite generous. I hope you look me up in the future if you need work.
+
m10f -
 +
 
 +
mission\mission_datadisk.iff
 +
 
 +
m10l -
 +
 
 +
Datadisc
 +
 
 +
m10o
 +
 
 +
m10p -
 +
 
 +
If you lose this disc, mister "artiste" is going to have a fit. I don't know why he doesn't just transmit the stupid thing. Like compression would make his stupid bleatings sound worse!
 +
 
 +
m10r -
 +
 
 +
Hey, thanks. That is a good thing, delivering these gonzo sounds. A good thing. -- Uh, sorry, was I saying something? Never mind. Take care, okay? I'll go check out the vibes on this. Thanks.
 +
 
 +
m10s -
 +
 
 +
Thanks, buddy. This recording is going to blow your mind, it's the best kloo-horn material ever, I swear. My girlfriend says I'm a genius, and she used to write for the music rags, so she should know.
 +
 
 +
m10t -
 +
 
 +
Solo Kloo-Horn Recording!
  
−
m10t Sonic Weapons Are Loud
+
 
 +
 
 +
 
 +
 
 +
Notes:
  
  
Line 247: Line 257:
  
  
−
m10p - This is the response given by the npc that the player picks up the components and schematics from. This is issued once the player has successfully conversed and interacted with it.
+
m10f No longer in use. This is the path to the object that was to be used for a player to pick up from the npc and that was to be delivered to the destination point and dropped or given to the npc there.
  
−
m10r - This is the response given by the npc that the player delivers the finished requested item to. This is issued once the player has dropped the item onto the npc.
+
m10l This is the name that was to be assigned to the object to be delivered.
 +
 
 +
m10o This is the mission creator's name. The mission creator name is randomly created unless given by an npc. If an npc gives the mission then the creator becomes the name of the npc.
 +
 
 +
m10p - This is the response given by the npc that the player starts the mission from. This is issued once the player has successfully conversed and interacted with it.
 +
 
 +
m10r - This is the response given by the npc that the player reaches the deliery point and interacts with the npc.  
  
 
m10s - This response is not used in game, but was probably intended as a response given by a mission giving npc once the player finished that particular assignment and came back to it for another mission.
 
m10s - This response is not used in game, but was probably intended as a response given by a mission giving npc once the player finished that particular assignment and came back to it for another mission.
  
 
m10t - This is the mission title as seen on the terminal or on the mission details once the mission has been accepted by the player.
 
m10t - This is the mission title as seen on the terminal or on the mission details once the mission has been accepted by the player.
 +
  
 
<br><br>
 
<br><br>
−
== Step by Step Progression of a Crafting Mission ==
+
 
 +
== Mission NPC Delivery Mission STF Analysis ==
 +
 
 +
 
 +
The following is an example taken from mission_deliver_neutral_easy_non_persistent_from_npc.stf file for mission npc delivery missions. An overview for how to properly read and interpret the stf file will be included further below.
 +
 
 +
 
 +
'''m10d'''
 +
 
 +
My employer sells antiques to interested buyers. One such collector has paid the proper fee to view my employer's wares. Could you pick up an encrypted catalog and deliver it? The collector will know how to retrieve the data.
 +
 
 +
'''m10f'''
 +
 
 +
mission\mission_datadisk.iff
 +
 
 +
'''m10l'''
 +
 
 +
Datadisc
 +
 
 +
'''m10o'''
 +
 
 +
'''m10p'''
 +
 
 +
Nothing is free, pal.  If you want to look, you gotta pay the fee too. Actually, you probably can't afford it. Deliver this quick, though, and you might be on your way to earning enough.
 +
 
 +
'''m10r'''
 +
 
 +
The catalog at last! I've waited a long time for this. The possibility of Sith artifacts! Can you imagine?
 +
 
 +
'''m10s'''
 +
 
 +
By the way, the contents of our catalog are confidential. Please respect our privacy.
 +
 
 +
'''m10t'''
 +
 
 +
Antiques Catalog
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
Notes:
 +
 
 +
m10d - This is the mission description displayed in mission terminals or on the mission if a player examines the mission. This is also given as npc dialogue when a player receives the mission from a mission giving npc.
 +
 
 +
 
 +
m10f No longer in use. This is the path to the object that was to be used for a player to pick up from the npc and that was to be delivered to the destination point and dropped or given to the npc there.
 +
 
 +
m10l This is the name that was to be assigned to the object to be delivered.
 +
 
 +
m10o This is the mission creator's name. The mission creator name is the name of the npc that gave the mission to the player
 +
 
 +
m10p - This is the response given by the npc that the player starts the mission from. This is issued once the player has successfully conversed and interacted with it.
 +
 
 +
m10r - This is the response given by the npc that the player reaches the delivery point and interacts with the npc.
 +
 
 +
m10s - Response given by a mission giving npc once the player finished that particular assignment and came back to it to collect their reward.
 +
 
 +
m10t - This is the mission title as seen on the terminal or on the mission details once the mission has been accepted by the player.
 +
 
 +
== Step by Step Progression of a Delivery Mission ==
  
  
−
* Player uses artisan mission terminal and [[media:CraftingMission3.jpg|obtains a crafting mission]]
+
* Player uses Mission Terminal and [[media:DeliveryMission5.jpg|obtains a delivery mission]]
  
−
* Schematic & component pick up location npc [[media:CraftingMission4.jpg|waypoint is generated]]
+
* OR Player interacts with a mission giving npc and obtains a delivery mission
  
−
* Player interacts with pick up npc to [[media:CraftingMission5.jpg|obtain schematic and components]]
+
* Mission delivery pickup starting location npc [[media:DeliveryMission1.jpg|waypoint is generated]]
  
−
* Mission waypoint is updated to coordinates of [[media:CraftingMission7.jpg|destination npc]]
+
* Player interacts with pick up npc to [[media:DeliveryMission2.jpg|obtain delivery point coordinates]]
  
−
* Player crafts requested item using the [[media:CraftingMission6.jpg|acquired schematic]]
+
* Mission waypoint is updated to coordinates of [[media:DeliveryMission3.jpg|destination npc]]
  
−
* Player takes item to destination npc and drops it onto it to [[media:CraftingMission9.jpg|complete mission]]
+
* Player interacts with destination point npc to [[media:DeliveryMission4.jpg|complete the mission]]
  
 
==Source References==
 
==Source References==

Latest revision as of 04:16, 12 August 2009


Emblem-important.png
 This article or section needs proper wiki formatting.



Game Mechanics - Mechanics Category

SWGANH Wiki is a repository of Star Wars Galaxies Developer information. This site is only meant to be used by SWGANH Developer team.


Navigation

Auction
Banking
Combat
Crafting
Pets & Mounts
General Shared Messages
Dungeons
Galactic Civil War
Games
Healing
Jump to light speed
Logout event
Items and objects
Force Sensitive/Jedi
Player Interactions
Player Structures
Player Cities
Quests/Missions
Resources
Skills
Stats & Stat Migration
Travel
Tutorials
Unknown
Using Innate Species Ability
Waypoint / Datapad

Description

Template (Game Messages)

Related Tags

25% This document has been partially completed.

Mechanics This document is about game mechanics.

System Messages


Dialogue Responses

Game Mechanics

Delivery missions are missions that the player can take that require them to retrieve a message from the mission giver and then deliver that to another npc. Delivery missions may be picked up from the Delivery tab on Mission Terminals or from mission giving npcs. Delivery missions have two stages:

  • Acquiring the message
  • Delivering the message


When the player picks up the mission from the terminal they are given a waypoint to the mission giver's cordinates. The player then goes to this npc, uses the converse radial menu with it and then the npc will update the player's waypoint to the delivery point location. Both the mission giver and the delivery target are considered delivery mission targets.

Delivery mission targets are npcs that are selected to be part of the delivery missions either as the initial quest starter or as the delivery target. All delivery missions utilize "commoner" spawns which are fixed npcs around every town. The mission objective selects a random commoner to be the npc the player uses to begin the quest and then another commoner is selected out of the commoner node for a particular town to act as the npc that the player must deliver the object to. Delivery mission points always begin in the city that the player picks up the mission from unless that player is using a player city mission terminal.

If a player acquires a crafting mission within a player city then the start location will use commoner npc spawn nodes in one of the following fixed locations (depending on which planet the player is on):

  • mos entha
  • keren
  • mining outpost - dantooine
  • dearic
  • restuss
  • coronet
  • nym's outpost


Commoner npcs follow the same ruleset as filler npcs except that only commoner style npcs are selected for spawning.


For more information about npc spawning behavior see: Decorative NPCS


For a listing of commoner spawn see: Commoner NPC Locations


The destination point for delivery missions can be any one of three types:

  • Delivery point within the same city as the mission giver
  • Delivery point on the same planet but different city
  • Delivery point on a different planet and randomly selected city

Once the delivery point has been reached then the player uses the converse radial option again and the mission will be flagged as completed and the player rewarded.


Note: Players who interact with commoner npcs without a mission or without a mission that links to that particular npc will receive a randomly selected statement from the npc informing them that they have no business with the player.




Delivery Mission STFs

The following is a list of stfs that contain mission terminal delivery mission data:


Mission Terminals & Non GCW Mission Giving NPCs:


  • /mission/mission_deliver_neutral_easy.stf
  • /mission/mission_deliver_neutral_medium.stf
  • /mission/mission_deliver_neutral_hard.stf


General Use

  • /mission/mission_generic.stf

Analysis of Mission Datapad Details

Analysis of Mission Details

There are a number of important bits of information to know about a mission which are viewable through the mission details on the mission terminal or on the mission itself in the player's datapad.

The parts of a crafting mission details are:

  • Item
  • Start
  • Destination
  • Creator
  • Reward
  • Difficulty


Item


Note: This no longer has a function. Delivery missions at one point were intended to deliver a physical item between the pick up npc and the destination point however this was scrapped some time after launch. A number of mission files still contain the old information for these mission types however.

Presumably the way this worked was that The item detail lists the item that is needed to complete the mission. A player may turn in that particular item to the destination npc once it has been picked up.




Start

This is the coordinate of the starting npc that will update the player's waypoint coordinates to the destination point. Starting npcs are always commoners randomly selected from the commoner node points within the town that the mission terminal belongs to. Commoner nodes are spawn points where commoner npcs are found. The server chooses randomly which point will be used as a starting point within the selected town. Starting locations are always begun on the same planet as the mission giver. If a player acquires a delivery mission within a player city then the start location will be one of the following fixed locations (depending on which planet the player is on):

  • mos entha
  • keren
  • mining outpost - dantooine
  • dearic
  • restuss
  • coronet
  • nym's outpost




Destination

This is the coordinate of the npc that the player is to go to in order to receive credit for the mission. Destination locations for delivery missions are randomly selected between towns to select npc nodes to choose from. Destinations can be any planet and town that has commoner npc nodes. Destination targets are always commoners randomly selected from the commoner node points within a town. Commoner nodes are spawn points where commoner npcs are found. The server chooses randomly which point will be used as a destination point within the selected town.


Creator

The creator of the mission is randomly generated, unless its a mission giving npc then the mission takes the name of the npc that gave it.


Reward

This is the payout to the player in credits for successfully completing the mission. Reward is only given out if the player interacts with the destination npc by using the converse radial options. Mission payout reward formula is currently unknown.


Difficulty

Note: Difficulty rating on missions seems to be random between 1-3 for some reason without any discernable causes. I believe we should stream line this to reflect how the mission mechanics work.

A proposal is this:

Mission difficulty ratings rank from 1-3 where mission ranking 1 refers to same city missions, mission ranking 2 refers to locations on the same planet but different city, and rank 3 missions refer to off world missions.



Mission Terminal Delivery Mission STF Analysis

The following is an example taken from the mission_deliver_neutral_easy.stf file for delivery missions. An overview for how to properly read and interpret the stf file will be included further below.



m10d -

My new solo recording of kloo-horn pieces, including an all-new rendition of the classic "Soaring Banthas at Sunset," is finished. But I need someone to hand-deliver it to my sound engineer. I don't trust HoloNet compression routines, you know, they're lossy algorithms that ruin the tone. I'm kind of distracted by a personal crisis, so I really need these tracks taken quick. Be a friend, huh? You'll love the guys at the mastering joint, they're smooth.

m10f -

mission\mission_datadisk.iff

m10l -

Datadisc

m10o

m10p -

If you lose this disc, mister "artiste" is going to have a fit. I don't know why he doesn't just transmit the stupid thing. Like compression would make his stupid bleatings sound worse!

m10r -

Hey, thanks. That is a good thing, delivering these gonzo sounds. A good thing. -- Uh, sorry, was I saying something? Never mind. Take care, okay? I'll go check out the vibes on this. Thanks.

m10s -

Thanks, buddy. This recording is going to blow your mind, it's the best kloo-horn material ever, I swear. My girlfriend says I'm a genius, and she used to write for the music rags, so she should know.

m10t -

Solo Kloo-Horn Recording!



Notes:



Notes:

m10d - This is the mission description displayed in mission terminals or on the mission if a player examines the mission. This is also given as npc dialogue when a player receives the mission from a mission giving npc.


m10f No longer in use. This is the path to the object that was to be used for a player to pick up from the npc and that was to be delivered to the destination point and dropped or given to the npc there.

m10l This is the name that was to be assigned to the object to be delivered.

m10o This is the mission creator's name. The mission creator name is randomly created unless given by an npc. If an npc gives the mission then the creator becomes the name of the npc.

m10p - This is the response given by the npc that the player starts the mission from. This is issued once the player has successfully conversed and interacted with it.

m10r - This is the response given by the npc that the player reaches the deliery point and interacts with the npc.

m10s - This response is not used in game, but was probably intended as a response given by a mission giving npc once the player finished that particular assignment and came back to it for another mission.

m10t - This is the mission title as seen on the terminal or on the mission details once the mission has been accepted by the player.




Mission NPC Delivery Mission STF Analysis

The following is an example taken from mission_deliver_neutral_easy_non_persistent_from_npc.stf file for mission npc delivery missions. An overview for how to properly read and interpret the stf file will be included further below.


m10d

My employer sells antiques to interested buyers. One such collector has paid the proper fee to view my employer's wares. Could you pick up an encrypted catalog and deliver it? The collector will know how to retrieve the data.

m10f

mission\mission_datadisk.iff

m10l

Datadisc

m10o

m10p

Nothing is free, pal. If you want to look, you gotta pay the fee too. Actually, you probably can't afford it. Deliver this quick, though, and you might be on your way to earning enough.

m10r

The catalog at last! I've waited a long time for this. The possibility of Sith artifacts! Can you imagine?

m10s

By the way, the contents of our catalog are confidential. Please respect our privacy.

m10t

Antiques Catalog




Notes:

m10d - This is the mission description displayed in mission terminals or on the mission if a player examines the mission. This is also given as npc dialogue when a player receives the mission from a mission giving npc.


m10f No longer in use. This is the path to the object that was to be used for a player to pick up from the npc and that was to be delivered to the destination point and dropped or given to the npc there.

m10l This is the name that was to be assigned to the object to be delivered.

m10o This is the mission creator's name. The mission creator name is the name of the npc that gave the mission to the player

m10p - This is the response given by the npc that the player starts the mission from. This is issued once the player has successfully conversed and interacted with it.

m10r - This is the response given by the npc that the player reaches the delivery point and interacts with the npc.

m10s - Response given by a mission giving npc once the player finished that particular assignment and came back to it to collect their reward.

m10t - This is the mission title as seen on the terminal or on the mission details once the mission has been accepted by the player.

Step by Step Progression of a Delivery Mission

  • OR Player interacts with a mission giving npc and obtains a delivery mission

Source References

Source Source in Context
Retrieved from "https://wiki.swganh.org/index.php?title=Delivery_Missions_(Game_Mechanics)&oldid=58099"