Player Resource Consortium

 

Author Topic: Ultimate ranger  (Read 4585 times)

0 Members and 1 Guest are viewing this topic.

April 03, 2012, 06:27:57 PM
  • Adept
  • *
  • Posts: 5
  • Karma: +0/-0
  • New Member
    • View Profile

I was not able to take hide in plain sight feat at level 11. It would just reset my level up. I had to mess with leto to get that feat ???.

Just telling you cause it was a bit annoying bug.


April 04, 2012, 12:56:49 AM
Reply #1
  • Associate
  • ***
  • Posts: 228
  • Karma: +2/-0
    • View Profile

I was not able to take hide in plain sight feat at level 11. It would just reset my level up. I had to mess with leto to get that feat ???.

Just telling you cause it was a bit annoying bug.

I have played ultimate ranger builds several times and always been able to take hide in plain sight, though it is possible that changes in recent versions could have caused a problem.

If I might suggest a different possibility, though, I have noticed that ultimate ranger is tricky if you aren't thinking about what you are doing very carefully on level up.  That's because you can select anything an ultimate ranger could take at any level, regardless of what you are supposed to get at that level.  In other words, you could accidentally select favored enemy when it isn't the right level, or (in the case of level 11), two special abilities when you are supposed to be taking one special ability and one bonus feat.  (I used to make that kind of mistake all the time!)  That situation will cause you to re-level.  The manual makes the distinction clear, so when I play ultimate ranger, I always have a copy of the manual page close at hand, just in case.


April 04, 2012, 01:37:36 PM
Reply #2
  • Hero Member
  • *****
  • Posts: 1439
  • Karma: +27/-0
  • Gender: Male
    • View Profile

I was not able to take hide in plain sight feat at level 11. It would just reset my level up. I had to mess with leto to get that feat ???.

Just telling you cause it was a bit annoying bug.
I modified HiPS for UR class recently, but I forgot to update the constant. Easy to fix, but still a bug. Thanks for reporting.
Fix in attachment.