Difference between revisions of "Delivery Missions (Game Mechanics)"
(→Delivery Mission STF Analysis) |
(→Delivery Mission STF Analysis) |
||
Line 233: | Line 233: | ||
− | m10d - | + | 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. | |
− | m10l - Datadisc | + | m10f - |
+ | |||
+ | mission\mission_datadisk.iff | ||
+ | |||
+ | m10l - | ||
+ | |||
+ | Datadisc | ||
m10o | 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! | + | 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! | |
Revision as of 17:09, 8 August 2009
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.
|
Game MechanicsDelivery 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 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):
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:
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.
Delivery Mission STFsThe following is a list of stfs that contain mission terminal delivery mission data: Imperial Faction Terminals:
Imperial Faction Mission Giving NPCs
Rebel Faction Terminals:
Analysis of Mission Datapad DetailsAnalysis of Mission DetailsThere 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:
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.
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):
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.
The creator of the mission is always the name of the starting location npc or mission giving npc.
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.
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.
Delivery Mission STF AnalysisThe 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.
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:
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.
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. 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.
Step by Step Progression of a Crafting Mission
Source References
|