Range on clairsentience

[unclevlad]

HD Build 20180726

 

I'm playing around with Clairsentience.  

 

#1:  Sight group, 360 degree arc, x2 range.  25 base points, yes.  So it reports 500m range.  

#2:  Add 0 End.  Range reported:  740m.  Hmm.

#3:  Add MegaScale, 1m = 1 km.  

 

Clairsentience (Sight Group), x2 Range (1,240m), Increased Arc Of Perception (360 Degrees), Reduced Endurance (0 END; +1/2), MegaScale (1m = 1 km; +1) (75 Active Points)

 

Clairsentience appears to allow both the x2 Range and MegaScale to be in effect at the same time, so I think that's legal, but...from Range, 6E1 129:

 

Quote

Standard Range is commonly used for Attack Powers and the like. A Power with Standard Range has a maximum Range equal to 10 meters times the Character Points spent on the base Power (in other words, don’t count Adders or Advantages). A Blast 10d6 (base cost of 50 Character Points, final cost of 50 Active Points) has a Range of 500m; a Blast 10d6, Armor Piercing (base cost of 50 Character Points, final cost of 62 Active Points) also has a Range of 500m.

 

Well, here, it's allowing the Reduced End to increase the range.  And what feels REALLY weird is that MegaScale is being allowed to increase the range.  

 

The 360 perception is shown as an 'adder'...but the summary table on 6E1 179 suggests it's not supposed to be, and that probably it's just an issue with the nomenclature in HD.  Senses are a mess from a code perspective.  But the others...that's odd.  

 

I noticed this because I was having a hard time trying to determine what does, and what does not, contribute to the Base Points to derive the basic range, before any tweaks.  

 

 

[Simon]

The problem was in the displayed value, rather than the more generic range value calculation (meaning: it was limited solely to Clairsentience). 

 

There's a new update posted which should address the issue.

[unclevlad]

That seemed likely.  Thanks!  

[unclevlad]

Downloaded, copied JAR file over to its network home, kicked it off.  It loaded up the clairvoyant, but with this:

 

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jruby.ext.posix.util.FieldAccess (file:/H:/HD6.jar) to field java.io.FileDescriptor.handle
WARNING: Please consider reporting this to the maintainers of org.jruby.ext.posix.util.FieldAccess
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

 

Doesn't seem to have caused a problem, as it loaded.  H: is a mapped drive (Windows 10) to my NAS, because browsing networks with Java can be *painfully* slow on a WIndows network.

 

And it's reporting x2 Range is 400m, which means yeah, everything's adders and not counting, which was how I read the RAW.  

[Simon]

yeah, the warnings on startup have been there for a year or so -- they're just in the trace.log file and don't cause any issues.  Part of the print to PDF functionality -- since I'm not likely to be updating jruby, it's not going to be an issue.