I would like to suggest that the Scrying Sensor conjured from [Scrying] and [Greater Scrying] should receive a reusable blink ability similar to Ki-Step.
My reasoning is that it is a floating magical sensor, but is currently stopped by things like small fences, rivers, and the general pathing map. Since it cannot interact with *anything* (which is reasonable), this means that the sensor can't actually look anywhere that the player cannot walk to from where they spent a minute summoning it. A closed gate or a jump-node is impassable for the little sensor.
A short range blink, restricted to line-of-sight, would allow the sensor to be a bit more flexible and maneuverable in floating through the map looking at things.
Scrying Improvement suggestions
Moderators: Moderator, Quality Control, Developer, DM
- Kitunenotsume
- Posts: 631
- Joined: Sun May 17, 2020 10:57 pm
- Location: UTC -7
Scrying Improvement suggestions
I play a baker. Sometimes she provides counseling or treatment.
Ask about our Breadflower daily special to save five coppers off a purchase of five pastries.
She seems unusually interested in cursed items.
She has also been seeking a variety of gems and stones.
Ask about our Breadflower daily special to save five coppers off a purchase of five pastries.
She seems unusually interested in cursed items.
She has also been seeking a variety of gems and stones.
- Kitunenotsume
- Posts: 631
- Joined: Sun May 17, 2020 10:57 pm
- Location: UTC -7
Re: Scrying Improvement suggestions
After a bit more playing around with these spells, I have further suggestions to make, regarding their use and how they could be made a bit more satisfying to use.
1) Blink, as above.
2) Improve the duration
Currently they last 30 sec/CL (Normal) and minute/CL (Greater). This is in accordance with P&P, but as we have noted in other spells, this isn't P&P. Twenty minutes of scrying in P&P is a bit more powerful than the same in NWN2 due to speed of conversation limitations. Given the delays and how long RP can take, I've often found myself using two or three castings just to receive perhaps 20 lines of dialog from a group conversation, as RP can fairly often occur at less than one line per minute. Given the one-minute cast time and re-travel time of the sensor, this can mean a 10-15% downtime every 20 lines.
[edit] This might get resolved if the two spells receive their proper durations. Currently Greater Scrying does not last as long as other minute/level spells, and Scrying lasts only half that.
3) Fix use with voice-throw/tells/player-scry
Because the Scrying Sensor is scripted as a familiar, there are definite issues with dialog. I have noticed that any voice-throw (languages) while possessing the sensor are always emitted from the sensor, regardless of if I have my main character targeted. While processing the Sensor, it is also impossible to use /tells (with a dialog claiming that you can't because familiar) or the Player Scry utility, which is reasonable given differences in character IDs but in order to send or reply to any requires un-possessing the Sensor - which then needs to run all the way back to the caster in order to be re-controlled, in many circumstances.
4) It can cast spells?!?!? It really shouldn't.
Because it's scripted as a familiar, it can cast self and touch spells. While I think it's amusing that I can basically use it as a remote immune-to-everything buff-puff or remote spell-taser, I highly doubt that is the intention.
5) Clarity on how identifying a sensor works.
The [Scrying] and [Greater Scrying] spells say that the caster is identified by anyone who can see the sensor making a Spellcraft check that beats the DC of the spell. Meanwhile, the spell [Detect Scrying] says that the Scrying character gets to make a will save VS spells first, effectively meaning that Detect Scrying uses a 4th level spell to give the target (scrying char) a reasonable shot at being unidentified while without the spell they will almost certainly be identified.
1) Blink, as above.
2) Improve the duration
Currently they last 30 sec/CL (Normal) and minute/CL (Greater). This is in accordance with P&P, but as we have noted in other spells, this isn't P&P. Twenty minutes of scrying in P&P is a bit more powerful than the same in NWN2 due to speed of conversation limitations. Given the delays and how long RP can take, I've often found myself using two or three castings just to receive perhaps 20 lines of dialog from a group conversation, as RP can fairly often occur at less than one line per minute. Given the one-minute cast time and re-travel time of the sensor, this can mean a 10-15% downtime every 20 lines.
[edit] This might get resolved if the two spells receive their proper durations. Currently Greater Scrying does not last as long as other minute/level spells, and Scrying lasts only half that.
3) Fix use with voice-throw/tells/player-scry
Because the Scrying Sensor is scripted as a familiar, there are definite issues with dialog. I have noticed that any voice-throw (languages) while possessing the sensor are always emitted from the sensor, regardless of if I have my main character targeted. While processing the Sensor, it is also impossible to use /tells (with a dialog claiming that you can't because familiar) or the Player Scry utility, which is reasonable given differences in character IDs but in order to send or reply to any requires un-possessing the Sensor - which then needs to run all the way back to the caster in order to be re-controlled, in many circumstances.
4) It can cast spells?!?!? It really shouldn't.
Because it's scripted as a familiar, it can cast self and touch spells. While I think it's amusing that I can basically use it as a remote immune-to-everything buff-puff or remote spell-taser, I highly doubt that is the intention.
5) Clarity on how identifying a sensor works.
The [Scrying] and [Greater Scrying] spells say that the caster is identified by anyone who can see the sensor making a Spellcraft check that beats the DC of the spell. Meanwhile, the spell [Detect Scrying] says that the Scrying character gets to make a will save VS spells first, effectively meaning that Detect Scrying uses a 4th level spell to give the target (scrying char) a reasonable shot at being unidentified while without the spell they will almost certainly be identified.
Scrying wrote:Regardless of the saving throws, if a creature in close proximity is able to see the sensor it performs a spellcraft check against the spell's DC to identify the caster. If succesfull, both parties are informed and the eavesdropping party will have auto-consented to PvP. Due to its magical nature, a scrying sensor cannot be seen with Blind Sight.
Detect Scrying wrote:When a scrying attempt is detected the scrying entity must immediately roll a will savingthrow vs spells. If this is failed the identity of the scryer immediately becomes known to the caster, derived from the target's magical mark on the scrying sensor. The saving throw is d20 + the caster's spellcraft skill vs the spell save DC of the scryer.
I play a baker. Sometimes she provides counseling or treatment.
Ask about our Breadflower daily special to save five coppers off a purchase of five pastries.
She seems unusually interested in cursed items.
She has also been seeking a variety of gems and stones.
Ask about our Breadflower daily special to save five coppers off a purchase of five pastries.
She seems unusually interested in cursed items.
She has also been seeking a variety of gems and stones.
- Valefort
- Retired Admin
- Posts: 9779
- Joined: Thu Apr 28, 2011 5:07 pm
- Location: France, GMT +2
Re: Scrying Improvement suggestions
1, 4 and 5 should work next update.
Mealir Ostirel - Incorrigible swashbuckler
- Kitunenotsume
- Posts: 631
- Joined: Sun May 17, 2020 10:57 pm
- Location: UTC -7
Re: Scrying Improvement suggestions
Wonderful, thank you! #3 was also implemented when the Familiar chat update was introduced, so thats almost everything!
[Ref To:Link] I've sent you a PM with my duration experiments confirming the current unlisted duration reduction.
Given that it's being technically-defamiliarized, is there any likelihood the con damage on destruction could be addressed?
[Ref To:Link] I've sent you a PM with my duration experiments confirming the current unlisted duration reduction.
Given that it's being technically-defamiliarized, is there any likelihood the con damage on destruction could be addressed?
Last edited by Kitunenotsume on Thu Apr 14, 2022 6:04 pm, edited 1 time in total.
I play a baker. Sometimes she provides counseling or treatment.
Ask about our Breadflower daily special to save five coppers off a purchase of five pastries.
She seems unusually interested in cursed items.
She has also been seeking a variety of gems and stones.
Ask about our Breadflower daily special to save five coppers off a purchase of five pastries.
She seems unusually interested in cursed items.
She has also been seeking a variety of gems and stones.
- Valefort
- Retired Admin
- Posts: 9779
- Joined: Thu Apr 28, 2011 5:07 pm
- Location: France, GMT +2
Re: Scrying Improvement suggestions
I noticed the thread but it is still a familiar technically so I'm not sure how to work around the CON loss, a restoration effect would work but would also be more than it should be.
Mealir Ostirel - Incorrigible swashbuckler
- Kitunenotsume
- Posts: 631
- Joined: Sun May 17, 2020 10:57 pm
- Location: UTC -7
Re: Scrying Improvement suggestions
I'm going to build off this thread with my observed interactions with Scrying since the update and all the changes is now in.
Please note - while I can play around with Scrying, my character is not a DC-caster nor dedicated diviner, I just have the spells available to test with. As such, some concerns may not be applicable to someone capable of getting stratospheric DCs, but should overall be reflective of a generic median caster.
My current testing results:
A) Seems to work, Party members do not recall sensor.
B) See Invisibility still detects the sensor, as does True Sight. I had some Ghosts in Fields of the Dead actually attack and kill the sensor. That said, with Improved Invisibility, my sensor can now uselessly attack allies without being revealed.
C) Seems to be working, Testing assistants reported no detection cues unless Detect Scrying was active. However, only scrying existence is confirmed, unless See Invisibility of some form is active, at which point identifying the originating caster is possible (and practically guaranteed, because Spellcraft VS Save DC).
D) Entirely unreliable - I have had a Cow save vs 9th level scrying (theoretical minimum DC 10+9+4=23), followed by letting my sensor hang out just fine. I've also had my scrying sensor be fine near players until they activated Detect Scrying (which instantly kicked my sensor home). It also seems like the scrying roll is unique per cast, not per server-reset (one cast might work on a target, next might not, next may work again)
E+F) The increase in radius and increase in save-forcing targets dramatically reduces how mobile the sensor is, as the sensor will be unable to pass by most NPCs with combat stats (and some that don't) due to the sheer distance required to cross. This has severely curtailed the utility of the spell to scout in dungeons as Arcane Eye might be used. The caster must also require that all characters (PC and NPC) within Local-Say range (Including through walls) fail the save on the current cast (equivalent to requiring every target fail the save on a Meteor Storm for anyone to be affected). As such, the following are valid counters to Scrying:
Further observations appreciated by anyone inclined to aid in testing.
I may have more to add once I've had a few more days of comparing the current interactions to their former states.
Wiki pages for Scrying, G.Scrying, and Detect.Scrying updated to reflect current states.
Please note - while I can play around with Scrying, my character is not a DC-caster nor dedicated diviner, I just have the spells available to test with. As such, some concerns may not be applicable to someone capable of getting stratospheric DCs, but should overall be reflective of a generic median caster.
Letters added for reference.
- Scrying sensor should now correctly bypass rolls for party members.
- See Invis spells no longer spot the sensor for scrying. Warlock crawling eye can still be seen with see invis as it's a physical object.
- Saving against the spell recalls the sensor but does not on its own allow the subject to know they were being scried on or to determine who sent the sensor. Detect Scrying will now be the only way to detect scrying and trace a scrying sensor back to its source.
- A single target gets one save per reset against a single caster's scrying sensor. If you pass the save, any further attempts at scrying near you will automatically fail. If you fail the save, you can no longer make saves against that caster's scrying sensors until the next server reset.
- Save radius increased to match Local-Say radius. [Confirmed in Discord]
- Many ambient NPCs now force saves that didn't previously [Confirmed via extensive testing]
My current testing results:
A) Seems to work, Party members do not recall sensor.
B) See Invisibility still detects the sensor, as does True Sight. I had some Ghosts in Fields of the Dead actually attack and kill the sensor. That said, with Improved Invisibility, my sensor can now uselessly attack allies without being revealed.
C) Seems to be working, Testing assistants reported no detection cues unless Detect Scrying was active. However, only scrying existence is confirmed, unless See Invisibility of some form is active, at which point identifying the originating caster is possible (and practically guaranteed, because Spellcraft VS Save DC).
D) Entirely unreliable - I have had a Cow save vs 9th level scrying (theoretical minimum DC 10+9+4=23), followed by letting my sensor hang out just fine. I've also had my scrying sensor be fine near players until they activated Detect Scrying (which instantly kicked my sensor home). It also seems like the scrying roll is unique per cast, not per server-reset (one cast might work on a target, next might not, next may work again)
E+F) The increase in radius and increase in save-forcing targets dramatically reduces how mobile the sensor is, as the sensor will be unable to pass by most NPCs with combat stats (and some that don't) due to the sheer distance required to cross. This has severely curtailed the utility of the spell to scout in dungeons as Arcane Eye might be used. The caster must also require that all characters (PC and NPC) within Local-Say range (Including through walls) fail the save on the current cast (equivalent to requiring every target fail the save on a Meteor Storm for anyone to be affected). As such, the following are valid counters to Scrying:
- Having an active Nondetection
- Having high Will saves
- Standing near someone with High Saves or Nondetection
- Standing near any guard NPC
- standing near a hostile mob (such as being in combat)
- standing near a summoned creature (Your own or someone elses)
- standing in a group (as long as one person passes, you are all covered!)
- Standing near a Cow, in once instance. (Evidently touched by Zanniej)
- standing beyond anyone with the above, relative to the caster (my sensor is currently unable to cross the Wrym's Crossing Bridge without skillful use of Blink)
- sitting someone near the caster so the Scrying Sensor remains on permanent timeout being recalled to said caster.
- any AoE spell used nearby (Storm of Vengence, Wall of Fire, any straight damage. it's only got 10 HP, has no resistance to any damage, and deals 2 Con Drain to the caster on death!)
- Detect Scrying Radius is ~30% larger than Local-say radius, and will begin forcing saves at that range.
- Blink works! it's pretty neat, and the only way of getting a sensor out of range if someone is near the caster.
- My sensor can still cast spells. Due to the current limitations, that means pretty much only party-targets and ground targets (Raise dead is apparently castable from Scrying Sensor, but is potentially recalled as soon as it works if the raised target succeeds the save)
- Durations are still very incorrect - which combined with the very long cast time (interrupted by party-joins and other events) and current impotence is even more painful.
- Spell descriptions for Scrying/G.Scrying/Detect.Scrying have been unchanged to reflect current updates.
- Sensor can still only be controlled when near the caster (within Local-Say range) and then piloted out. It thus requires a path to the intended destination, with Local-Say clearance on both sides that do not contain anyone who have or may pass the current Save (a separate requirement from everyone at the destination failing the save).
Scrying DCs are still not shown on cast (they disappeared during the February updates)((Fixed!)), nor are any save rolls shown to either party (so no indicator if the spell worked, only if it failed).- When the caster is near a detecting target, both are spammed by combat log entries every round until the Scrying Sensor is far enough away to stop being recalled, or just unsummoned.
- The sensor feedback log indicates that the Scrying caster fails a save against the detecting target upon recall, for any reason. In practice, the target would have succeeded on their save against the DC of the caster.
- The spell is valid for detecting hidden characters within Local-Say range, due to the coding, along with reporting one hidden individual every 6 seconds.
- Provide the Scrying Sensor with Low-Light/Darkvision if the caster possesses those senses (Doubly useful in that Darkvision is Local-Say radius and thus an indicator for moving around characters without potential recall)
- Increase the take-control radius of Familiars to area-wide (This would also allow Clairaudience/Clairvoyance to be fitted to P&P)
- permit or require targetting a single target as the Scrying focus that is the primary Save-or-fail roll (could be quite tricky to implement)
- Reduce the Save radius back to prior distances unless the bystander is affected by Mindblank/Nondetection/Detect Scrying.
- Increase the save DC, either flat, Vs NPCs, or if nearby a willing 'anchor' target (such as a party member who acts as a Scrying target)
- Give the sensor plot invulnerability (reduced to but not below 0 HP) and unsummon on death; OR make it invulnerable, depending on sensor inspiration.
- Script unsummon of sensor on expiration, instead of deleting the summon and retaining in-party.
- Automatically include Blink on the Scrying Sensor's action-bar, or as a right-click creature ability.
Hidden: show
I may have more to add once I've had a few more days of comparing the current interactions to their former states.
Wiki pages for Scrying, G.Scrying, and Detect.Scrying updated to reflect current states.
I play a baker. Sometimes she provides counseling or treatment.
Ask about our Breadflower daily special to save five coppers off a purchase of five pastries.
She seems unusually interested in cursed items.
She has also been seeking a variety of gems and stones.
Ask about our Breadflower daily special to save five coppers off a purchase of five pastries.
She seems unusually interested in cursed items.
She has also been seeking a variety of gems and stones.