Jump to content

Welcome to Obsidian Forum Community
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. If you already have an account, login here - otherwise create an account for free today!

Bleeding check difficulty and other fun buggys ;-)

  • Please log in to reply
1 reply to this topic




  • Members
  • 2317 posts
  • Deadfire Backer
  • Fig Backer
I heard this From another players and desided to redo it.

The problem. When game event for example villain increase its own difficulty, the difficulty leaks to other checks. In this example Seoni meets Justin Ironbear alone and there Are some temporary closing checks as well as one summoned enemy. Also very nice example of well known Sealah future seing bug ;-)

Have a good Ride!

First Seoni meets Justin, and Justin rolls 2 with his D4 to increase his own difficulty

second Sealah tries temporary close her location. It should be Divine 6 but instead it is Divine 8
Why? Because Justin difficulty modifiers bleeds to closing check.

Next Justing summoned Goblin cutpurse and the wisdom 6 is visdom 8 instead... Same bleeding effect...
And so on to all checks, but...

Last poor Justing fight without his +2 difficultu modifier
And lose his fight...

And They lived happily there after... Or did They?

Justing come back later and and summons a boar. Seelah try to make wisdom check and use her power and well known fortuneteller bug strikes again and Seelah get some spanking ;-)
10 damage From wisdom check failure that converted to be combat check via fortuneteller power and boost by Justin like before.

Hilarious ;-)

Summasummarum, some difficulty check modifiers affect in all the wrong places!

Edited by Hannibal_PJV, 05 May 2016 - 12:35 AM.

Aarik D

Aarik D

    Community Manager

  • Developers
  • 3235 posts
  • Black Isle Bastard!

Hey Hannibal!


Thanks for investigating this issue for us! I'll put in a bug and look into it further. 


Thanks a bunch!

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users