mccrispy

Quest saved to the Cloud as of 1.0.3.7 IIRC. But recovering would require making sure the App is completely shut down (maybe even logging out of Play Now or Play Centre(?)), backing up the PACG Saved Games folder and then deleting it. After a device restart, login to Play Now and launch the game. You should have a restored game. Or course if your messed up game is saved to the cloud, this won't work as restoring damaged data never helps! Deleting the temporary save (in Slot_99 I believe, but doing quote me ), might help. Some guidance from the Devs in this regard would be *very* useful and much appreciated!

Hmmm... Limit of one item per check? That'll be it. I don't think that's ever come up before for me!

A fix to stop it happening, but not - it appears - a fix to repair characters that have missed out because of the bug. Unless somebody *knows* different (rather than has an opinion or guesses/hopes)

Seriously? OMG this would be the third time that I've had to restart Kyra and Seelah from scratch (and they are level 22 at the moment!). I had a patch reinstall mean that I lost my Quest characters, I had the locked Quest character bug and now this! All of these issue purely due to the App, rather than anything I've done. Great. Oh, and I have a problem with Quest mode across devices - characters seem to get out of sync (but not all characters), so now I've realised it, I daren't use multiple devices for the same character.

I suspect that your two devices aren't fully in sync and/or that not all your local content is saved to the cloud. I have a similar problem with my setup. In my case i know that there are issues with my login, they are not related to my use of an emulator but some oddity in my account or my Google play account - despite always being "logged in", my PFID often reads "user not yet logged in" instead of showing my PFID. I suspect that this means that sometimes content is saved locally rather than in the cloud and that this content is never synched/realigned with the cloud content.

Heh heh! *Finally* we catch a break with a bug in our favour! Doesn't compensate for all the missing level rewards, but I'm going to make sure I milk it until it goes away :D

This in no way affects the gameplay. Pediatron just cannot use said "frippery" for his game, everything else appears to run fine. And by fine, I mean as good as anyone else's game. Oh well, at least the Devs are taking it seriously!

Device: Hudl 2 OS: Android 5.1 PACG build: 1.0.3.8 Pass & Play: OFF Permadeath: OFF Mode: Quest Party Members: Kyra, Seelah, Sajan Turn Order: per party Scenario: ? Difficulty: Legendary Wildcards: Blood in the Sand, Retaliation (scenario: 1 poison damage on defeating Undead) Location: Farmhouse Trigger: defeat Ghoul using deathbane light crossbow Defeated the Ghoul and Blood in the Sand triggered and Sajan - as usual - took 1 damage. I discarded 1 card and then the discard 1 card dialogue appeared, so I assumed it was the scenario effect. Discarded again and then back came the damage dialogue. This repeated on a loop until i ran out of cards, at which point the Cancel and progress buttons were displayed and - after a pause - the game crashed. I didn't see an active effect indicated during all this. I still haven't figured a way to break out of this loop.

Device: Hudl 2 OS: Android 5.1 PACG build: 1.0.3.8 Pass & Play: OFF Permadeath: OFF Mode: Quest Party Members: Kyra, Seelah, Sajan Turn Order: per party Scenario: ? Difficulty: Legendary Wildcards: Blood in the Sand, Retaliation (scenario: 1 poison damage on defeating Undead) Location: Farmhouse Trigger: fail to acquire Potion of Hiding Kyra and Sajan were at Farmhouse when Kyra encountered the PoH. She failed to acquire it (surprise! but who cares?) Then the "discard 1 card" dialogue pops up. But why?

I'm not sure what's going on with the BoC. I was pretty sure that it had been working normally since patch 1.0.3.8, but... Device: AMIDuOS OS: Android 5.1 PACG build: 1.0.3.8 Pass & Play: OFF Permadeath: OFF Mode: Quest Party Members: Seelah, Kyra, Sajan Turn Order: per party Scenario: ? Difficulty: Legendary Wildcards: Driving Rain, Full Packs Location: Deeper Dungeons Trigger: Brooch of Shielding Repro Info: Sajan Encounters Zombie Minion; Amulet Frozen Fists, Favour of Irori gets 12/13 and so takes 1 damage, for which the BoC fails to offer the Recharge option.

+1 to this I recently hit level 20 with 3 Quest characters. I can't remember whether I won or lost the scenario, but it's happened on two separate occasions: the first, a party of Seelah, Kyra and Sajan completed a Legendary Quest where Seelah and Kyra hit lvl 20; the reward screen popped up to let me know that they had got a reward and Sajan hadn't; I hit the Continue button (I ​think​ that I used Sajan's button) and no rewards were offered. The second occasion, Sajan got his lvl 20 and the same thing happened - no reward offered after having pressed the Continue button. This is incredibly irritating when it happens on thelevels that are multiples of 5 (I couldn't care less about the other levels as I have yet to gain a useful card as a reward, but missing out on actual character levelling up stuff is totally unacceptable).

Ah, I thought you only got the chance to close immediately and at the start of your turn (if there are no cards). Must reread the rules!

Then why don't I see this dialogue for acquiring a Blessing any other time? None of the text on the Blessing alluded to such an option and nothing in my possession provided such an option. There were two buttons on the screen and they looked somewhat hinkey (the layout was odd), one for Check, the other for Bury. Never seen it before, not seen it since. Can't see how it's "expected".

Yes, I know *what* happens and how it all works. The point that I was making was that it isn't exactly intuitive.

Device: Hudl 2 OS: Android 5.1 PACG build: 1.0.3.8 Pass & Play: OFF Permadeath: OFF Mode: Quest Party Members: Sajan, Kyra, Seelah Turn Order: as party Scenario: ? Difficulty: Heroic Wildcards: Arrow Traps (Scenario: defeat Goblin; 2D4 tougher) Location: Waterfront Trigger: Seelah closed location, with no cards left in hand All the characters were at the Waterfront. Seelah closed the location, but there was no "discard 1 card" dialogue because she had an empty hand. However, the blue progress arrow was visible in the shading that indicates an off-turn character has an action. Flipping to Sajan, I can see all his cards are highlighted, but there's no dialogue explaining why and there's no Current Effect indicated over on the Location panel. Flipping to Kyra, none of her cards are highlighted. I discovered that dragging the cards to discard doesn't work - you end up with a progression break. The only way forward is to tap the card to discard and then hit the "Discard" button. By which I mean that a card dragged to discard on Sajan's screen doesn't trigger Kyra's screen for discarding! Boy, is this messed up!

Device: Hudl 2 OS: Android 5.1 PACG build: 1.0.3.8 Pass & Play: OFF Permadeath: OFF Mode: Quest Party Members: Sajan, Kyra, Seelah Turn Order: as party Scenario: ? Difficulty: Heroic Wildcards: Arrow Traps (Scenario: defeat Goblin; 2D4 extra difficulty) Location: Waterfront Trigger: Sajan defeats (Large) Chest with Thieves Tools OK, this was weird! Sajan defeated the Chest and a D4 was presented, so I rolled it (it wasn't presented in the "game's roll" graphic and I flicked it at the edge of the screen in the normal way - and it went in the direction I flicked it). For the first time in I literally cannot remember, it came up "4" (who ever​ gets four Boons from a Chest, like ever​?). I was then immediately presented with another D4 to roll and this one came up as a 1. So I guess the first die was the Arrow Traps die, in which case why was I allowed to roll it (I should say that the UI was​ a little laggy at this point). But man, rolling 4 weapons and then "forcing a re-roll" which comes up 1 is a real bummer. I really miss the graphic for a die being rolled by the game, it really made it clear whose die was being rolled. Is it only me, or do D4s seem to roll a disproportionate number of 1s at Hero level and above? Does the difficulty level also tweak the die rolls?

If I quit the game mid-scenario (BTW, I appreciate the change of button label to "Main Menu" instead of "Quit Game") and then exit the game, why when I relaunch the App does "Continue" take me to the party selection for Story mode instead of my paused Quest? This isn't "Continue" where you left off (the most common expectation), it's "Continue Story".

Device: Hudl 2 OS: Android 5.1 PACG build: 1.0.3.8 Pass & Play: OFF Permadeath: OFF Mode: Quest Party Members: Sajan, Kyra, Seelah Turn Order: as party Scenario: ? Difficulty: Heroic Wildcards: Retaliation (Scenario: defeat Goblin; 1 Fire damage) Location: Shrine to Lamashtu Trigger: Failed Ambush, Encounter Bunyip When the Bunyip spawned, the Wisdom roll was displayed as a D8-1. However, the game completely locked up. No Vault round-trip, nothing. Killing the game worked and I was able to relaunch the App and hit the Quest button to be brought back to where I left off. ​The Wisdom check was now displayed as D8-2!

Device: Hudl 2 OS: Android 5.1 PACG build: 1.0.3.8 Pass & Play: OFF Permadeath: OFF Mode: Quest Party Members: Sajan, Kyra, Seelah Turn Order: as party Scenario: ? Difficulty: Heroic Wildcards: Retaliation (Scenario: defeat Goblin; 1 Fire damage) Location: Farmhouse Trigger: Goblin Raider/Close Location Repro Info: Kyra moved from her closed location (unsure which it was) to Farmhouse with Sajan because after Sajan's turn, Goblin Raider was last card at location. She defeated the GR and was offered Close Location. Failed to defeat the Goblin Warchanter and took 1 Fire. Was then offered Close Location for the second time and defeated the Werewolf to close the location

Device: Hudl 2 OS: Android 5.1 PACG build: 1.0.3.8 Pass & Play: OFF Permadeath: OFF Mode: Quest Party Members: Sajan, Kyra, Seelah Turn Order: as party Scenario: ? Difficulty: Heroic Wildcards: Night Approaches (Scenario: acquire a Spell or Blessing, bury a card Location: Wooden Bridge Trigger: encounter Bounty of Norgorber Sajan encountered the Bounty and was immediately presented with a Check button and a Bury button. He chose Bury and automatically acquired the Bounty, after which the Scenario power triggered and he had to bury a card. There's nothing that I can see that required the initial Check/Bury dialogue.

Device: Hudl 2 OS: Android 5.1 PACG build: 1.0.3.8 Pass & Play: OFF Permadeath: OFF Mode: Quest Party Members: Sajan, Kyra, Seelah Turn Order: per party Scenario: who knows? if the Devs thought this was important for Quest bugs, they should have made it accessible ​Location: Guard Tower Difficulty: Heroic Wildcards: Retaliation (Scenario: Crow Bait - though it could have been the other way around) Trigger: Encounter Kyra encounters Erylium, summons Wrathful Sinspawn for Seelah So Seelah should be dealing with the WS, then Kyra will deal with Erylium. Or that's the idea. However, after Seelah passes the Wisdom check from the WS, combat returns to Kyra for her to defeat the WS. Surely, Seelah should have fought the WS after she passed the Wisdom check as it's Seelah who is encountering the WS?

Just one more reason to hate on the Enchantress. Close to being my most hated character (after that D4-rolling Scout, who always​ rolls 4s, whereas I always roll 1s - healing, chests, whatever, it's a 1).

And my point is that users shouldn't have to access the file system of their device to effect such a roll back (ignoring the fact that that the bug shouldn't exist, requiring a workaround).

Well, it is as I predicted: the introduction of non-gameplay "frippery" has introduced bugs that affect gameplay. We really need a robust platform to build on rather than a bunch of shiny toys that pretend to add value. I do wish that Obsidian would refocus their energies onto stuff that will be of long-term benefit, not short-term distraction.

If we just accept the situation without complaint we are telling Obsidian that it is OK to release defective code because the players will just work around it. I want to encourage Obsidian to release robust, self-recovering code that has mechanisms that obviate the need for low- level intervention and system access (such as a simple, character-level "roll-back"). These things aren't difficult, they just requires a change in mindset from Obsidian and a more robust response from those of us who contribute to the profitability their Company.