Difference between revisions of "Using Arakyd Probe Droids (Game Mechanics)"

From SWGANH Wiki
Jump to: navigation, search
(Game Mechanics)
(Formulas)
 
(5 intermediate revisions by the same user not shown)
Line 35: Line 35:
  
 
== System Messages ==
 
== System Messages ==
 +
 +
* [[Arakyd Probe Droid Usage (Game Messages)|Arakyd Probe Droid Usage]]
  
 
== Radial Menus ==
 
== Radial Menus ==
Line 66: Line 68:
  
 
Once the player receives the planet and original coordinate update, the probe droid will cease giving updates on the target's location.
 
Once the player receives the planet and original coordinate update, the probe droid will cease giving updates on the target's location.
 +
 +
 +
== Formulas ==
 +
 +
 +
'''Encountering Random Event'''
 +
 +
Chance of encountering random event = 100 x ( ( 1 - ( ( droid precision modifier / 100 ) / 1.5 ) )
 +
 +
Note: There is always a 5% chance of encountering an event or not encountering one regardless of modifiers.
 +
 +
 +
 +
 +
 +
'''Mark Spawn Diameter'''
 +
 +
No known formula exists for how to determine the diameter of mark spawn points but I propose the following:
 +
 +
 +
Spawn diameter = 550 - ( 500 x ( tracking droid effectiveness modifier / 100 ) )
 +
 +
Every point of tracking droid effectiveness should lower the diameter of the mark spawn range around the waypoint. For example by default, a mark can spawn anywhere within 500 meters of the waypoint once the player has stopped the mark movement process. With a tracking droid effectiveness modifier of +50, the mark can only spawn within a diameter of 250 meters of the waypoint. At + 100 tracking effectiveness, the mark can only spawn within 50 meters of the waypoint.
  
 
==Source References==
 
==Source References==

Latest revision as of 04:30, 12 September 2009




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.


Description

Template (Game Messages)

Related Tags

25% This document has been partially completed.

Mechanics This document is about game mechanics.

Completion Guide -

  • 0% - No substantive information available on game feature
  • 25% - page has been started but not completed
  • 50% - page is as complete as possible with the currently available information but probably needs more research done on the subject matter
  • 75% - page is probably complete but needs to be reviewed for accuracy of the page content and to make sure that no information is missing about the game feature
  • 100% - page has been reviewed and compared against enough sources to the extent that there is reasonable confidence that the game feature is completely documented.

System Messages

Radial Menus


Game Mechanics

Arakyd probe droids are used to create the initial waypoint coordinate for the bounty hunter player who is working on interplanetary bounty missions (Investigation I through master bounty hunter). Arakyd probe droids may be used by a bounty hunter who has acquired the Droid Find ability (Investigation 1). With the droid find ability, players get a new option when examining arakyd probe droid controllers in their inventory. Only one arakyd probe droid can be active at any time.


Arakyd probe droid controllers have one usable option: Find Bounty Target.


To use an arakyd droid controller to summon an arakyd droid, the player must first acquire a biological signature from the appropriate spynet operative, exit a town's municipal range and then use the Probe Droid Command radial menu and then choose the Find Bounty Target radial option. This will initiate a 20 second countdown sequence that will launch the probe droid down into the ground from the atmosphere when it reaches 0. When the probe droid landing sequence is complete, the droid will be spawned anywhere within a 128 meter diameter from the player. The player must then go to the droid, open up its radial menu and issue the Transmit Biological Signature. The droid will then acknowledge the action and then begin its take off sequence.

Following the droid taking off, a check is made in 30 seconds to determine if the droid will encounter one of six random events that will destroy it and force the player to summon another. This check is made against the player's droid precision modifier. A higher modifier will reduce the risk of this event occuring. If the player passes this check then the player will receive a report first listing which planet the mark has been spotted on. The droid will also add a waypoint to the player's datapad with the last known coordinates for the mark. The time it takes before the droid sends the player this information is based on the player's Droid Speed modifiers.

Droid speed modifiers are given out at each level of the investigation tree and at master bounty hunter. The times noted at each level of bounty hunter are as follows:


7:00 minutes at Investigation 1
4:00 minutes at Investigation 2
2:00 minutes at Investigation 3
1:30 at Master


Once the player receives the planet and original coordinate update, the probe droid will cease giving updates on the target's location.


Formulas

Encountering Random Event

Chance of encountering random event = 100 x ( ( 1 - ( ( droid precision modifier / 100 ) / 1.5 ) )

Note: There is always a 5% chance of encountering an event or not encountering one regardless of modifiers.



Mark Spawn Diameter

No known formula exists for how to determine the diameter of mark spawn points but I propose the following:


Spawn diameter = 550 - ( 500 x ( tracking droid effectiveness modifier / 100 ) )

Every point of tracking droid effectiveness should lower the diameter of the mark spawn range around the waypoint. For example by default, a mark can spawn anywhere within 500 meters of the waypoint once the player has stopped the mark movement process. With a tracking droid effectiveness modifier of +50, the mark can only spawn within a diameter of 250 meters of the waypoint. At + 100 tracking effectiveness, the mark can only spawn within 50 meters of the waypoint.

Source References

Source Source in Context