Hannibal_PJV

Check out that you Are Connected to the google play or game Center. http://forums.obsidian.net/topic/88500-updated-103-trouble-logging-in-here-is-a-workaround/ Or if this not loggin error (it sure does sound like it) try this http://forums.obsidian.net/topic/89757-purchasing-validation-error/ Live ninjas online!

A lot of exception and tweaks to normal rules... yep... nightmare to program.

Who would not like We goblings

True! The mummys mask is definitely more easier to swallow than Wrath was/is. I personally like wrath, but I like desperate games and don't mind of losing, dying horribly, got eaten alive etc... Most normal people say: "Can we play something else? I would like to win even sometimes..."

Strange. I personally have not run this particular problem and rnd has worked as it should have... could that be platform depended? I have met a countless of bugs during the time I have been playing this game, but newer bad randomization or sufling compared to real tabletop version. The nearest thing has been when die roll has caused a bug to happen, like 2d4 in the past with some enemies, but even that was not bad random roll, it was just normal game crushing bug.

Also if the dev can not reproduce the problem, it requires very exact description of the bug, so that They have a slim change to make it happen in their own tests. It is allmost impossible to fix something that does not ever happen... there has been some special cases Also in these forums when some bugs vere impossible to reproduce by dev team. In those cases the save file is essentially important along the situation where, when, how the bug happens. There Are so Many different devices around that it is impossible to test them all. But, yeah this is not as fast as we can hope, but only few of the team of 10 actually make the code, so all fixes takes a lot of time. It seems that after patch it take one month to two to fix the new bug and then some weeks to make new scenarios and other content and the start new cycle. With this small team, I don't think that we can Expect much more speed to these. Same people make new content, read these forums for the new bugs and fix them, test the fix and so on... time consuming task indeed!

When people post their own experiences about one particular bug it is much easier to handle if the whole threath handles only one bug. It is Also easier to other players found the right bug, if you can easily see what bug is handled in the discussion. So one bug per one discussion threath is easiest way to go.

I supose that it depends a lot of how well this game sells. If there is no Profit, why make more games that don't give Profit to makers. If the Rice of the rune lord is huge selling success, why not print more money? So it is all about dollars. The dev team is definitely interested in making new content to the game. But is the company willing to put more effort to it depends on the profit that the game bring to the company. Now it is too early to tell. The first game is not ready, The multiplatform is not ready, Steam version is not ready. So a lot has to be done before we can see if this game is success or not it big scale. I definitely hope that this game sells well, so that I can see more content. But next year will tell a lot about how that is folding out.

Nice! I have heard only one another case where player did get monster card to his deck. It was a while ago, so definitely not this update. Patrig would be happy to consume this unsuspedted "boon" There Are several heroes who can use monsters in their deck so maybe this has something to do with them? Who knows... but nice reward in anyway!

A dropbox link? That was really interesting bug I would definily like to see that picture. Would be hilarious to show it to friends in the next Gaming session!

It is delicate timing issue. There is from time to time discussion about this in the Paizo Pages too. It all depends what things you have to do before the winning condition is registered and what would happen after the winning condition is registered. For example closing the location power is before the winning condition, so if location forses you to draw a card from the playing deck, it happens before the winning condition happens. But for example resetting your hand is after that. So not easy to keep exact timing right. But temporary closing definitely happens before the winning condition is registered, so anything that should happen when temporary closing happens before you go to check if you did win or not. When in doupt in these matters we normally ask from the mighty Hawkmoon

Nsr and Ethiccs Gradient Are right in this. Too Many items during the same check.

If you have to draw a card from the blessing deck and you can not, you lose the game. So this sound like it should be. Same as if you for some reason have to draw a card from your deck and can not, you are dead.

Interesting... didn't catch that. So it behave like some barriers that stays at the top of the location...

Roger. Then it definitely Sounds a bug.

Did you check out how Many Nightbelly boas you did have in your deck? In here comes the Flood, there can be up to 3 boas in the same location. Ofcourse it is possible that the same card was actually in the top of the deck after sufling. Has happened Many time in the real tabletop version too.

Did you also check scenario power? It Also is different at different difficulty levels.

The turn order change is old problem. Not sure though if it has caused card loss before.

"It is better burn in the hell than case away" Those cumulative trickers Sounds familiar from previous scenarios... so a old bug In the new incarnation.

Everything is a quite lot...

I Also have found this one of the easiest in the legendary... ofcourse you need some serious charisma power in here!

End the year with big Gobling bang! That would be super neat!

Hmmm... sound similar than some cases before. Try to clear the game cache. Close google play and restart the google play and start the app from there. There should be old pinned? threath about this same problem.

The Apple store sometimes do it. I have encountered the same problem with another apps too, so its is some problem with iOs.