Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Guide:Early Silver Sword: Difference between revisions

From bg3.wiki
Raelin (talk | contribs)
Edit for consistency.
No edit summary
 
(2 intermediate revisions by one other user not shown)
Line 11: Line 11:


== The Challenge ==  
== The Challenge ==  
The primary obstacles to stealing the silver sword are Kith'rak Voss's [[Saving Throw]]s, [[Armour Class]] and, with more recent patches to the game, the high probability he will appear equipped with a [[Githyanki Crossbow]] instead of the sword.  
The primary obstacles to stealing the silver sword are Kith'rak Voss' [[Saving Throw]]s, [[Armour Class]] and, with more recent patches to the game, the high probability he will appear equipped with a [[Githyanki Crossbow]] instead of the sword.  


If Voss appears with a crossbow instead of his Silver Sword, the first challenge becomes getting him to equip the sword (so he may then be separated from it). A salient issue here is that Voss is normally programmed to fly away instantly when engaged in combat by any of the following entities:
If Voss appears with a crossbow instead of his Silver Sword, the first challenge becomes getting him to equip the sword (so he may then be separated from it). A salient issue here is that Voss is normally programmed to fly away instantly when engaged in combat by any of the following entities:
Line 17: Line 17:
* Summons of the PC or his/her companions
* Summons of the PC or his/her companions
* Familiars and other allies affiliated with the party
* Familiars and other allies affiliated with the party
However if Kith'rak Voss is immediately engaged in combat, by an entity in or near melee range that meets none of these definitions, he will equip his Silver Sword to fight this opponent. To date, the only known entity that meets this requirement is the [[Spectator]] that is freed as a result of throwing the {{SmRarityItem| Iron Flask}} (and acquiring the Flask is a task all by itself). This is because the Spectator from the Iron Flask is an independent entity, hostile to everyone and not under the influence of the party. Should the Flask be used, it is advisable to throw it from the bridge, out of sight of the gith gathered below, so party members are not immediately drawn into the conflict. Be sure to have it land close enough to Voss so he starts melee combat with the Spectator as soon as his [[initiative]] allows.  
However, if Kith'rak Voss is immediately engaged in combat, by an entity in or near melee range that meets none of these definitions, he will equip his Silver Sword to fight this opponent. To date, the only known entity that meets this requirement is the [[Spectator]] that is freed as a result of throwing the {{SmRarityItem| Iron Flask}} (and acquiring the Flask is a task all by itself). This is because the Spectator from the Iron Flask is an independent entity, hostile to everyone and not under the influence of the party. Should the Flask be used, it is advisable to throw it from the bridge, out of sight of the gith gathered below, so party members are not immediately drawn into the conflict. Be sure to have it land close enough to Voss so he starts melee combat with the Spectator as soon as his [[initiative]] allows.  


Once the Spectator is freed, you will have to act quickly. After taking (up to 3) swings at the Spectator, Voss may turn [[Invisible_(Condition)|invisible]] soon after, greatly reducing the chances of success with any of the steps listed below. Regardless of the outcome, whether or how he fights, once the Spectator is defeated, Voss will still leave.
Once the Spectator is freed, you will have to act quickly. After taking (up to 3) swings at the Spectator, Voss may turn [[Invisible_(Condition)|invisible]] soon after, greatly reducing the chances of success with any of the steps listed below. Regardless of the outcome, whether or how he fights, once the Spectator is defeated, Voss will still leave.
Line 75: Line 75:
== Consequences ==
== Consequences ==
* Once the sword is dropped, the party will still have a fight on its hands with the remainder of the githyanki patrol, so make sure their builds haven't been too narrowly skewed towards boosting the odds. Once they emerge victorious, they can pick the sword up off the ground and throw it on [[Lae'zel]] (or others who are disguised as Githyanki) for outrageous boosts that are typically gated behind many, many more ability checks, boss battles, and many hours of raw gameplay (and also some specific narrative paths).
* Once the sword is dropped, the party will still have a fight on its hands with the remainder of the githyanki patrol, so make sure their builds haven't been too narrowly skewed towards boosting the odds. Once they emerge victorious, they can pick the sword up off the ground and throw it on [[Lae'zel]] (or others who are disguised as Githyanki) for outrageous boosts that are typically gated behind many, many more ability checks, boss battles, and many hours of raw gameplay (and also some specific narrative paths).
* Be aware that acquiring the Silver Sword of the Astral Plane so much earlier than intended in the story-line may have impact on the game with unintended consequences. For example, early acquisition of this weapon will trigger some dialogue with Lae'zel that was intended for the Act 3 (yet  this has no material impact on the game). On the other hand, if you've read this far, with no significant problems reported (aside from the developer's repeated efforts with patches trying to stop this early acquisition) why not give it a go? After all: a challenge is a challenge...   
* Be aware that acquiring the Silver Sword of the Astral Plane so much earlier than intended in the story-line may have impact on the game with unintended consequences. For example, early acquisition of this weapon will trigger some dialogue with Lae'zel that was intended for the Act 3 (this appears to have no material impact on the game). On the other hand, if you've read this far, with no significant problems reported (aside from the developer's repeated efforts with patches trying to stop this early acquisition) why not give it a go? After all: a challenge is a challenge...   
[[Category:Guides]]
[[Category:Guides]]