Jump to content

mccrispy

Members
  • Posts

    708
  • Joined

  • Last visited

Everything posted by mccrispy

  1. I was playing Quest mode on Normal difficulty and got the Scenario Power "Giants difficulty +D4". I would Encounter an Ogrekin and the D4 for difficulty would roll, then the D4 for Ogrekin power, the OK would reskin and then auto-defeat and a "Close Location?" prompt would appear. I didn't spot a correlation between the difficulty roll and the OK power result, all the OK were auto-defeated. BTW, the Villain was Barl Breakbones (who still took three Checks to defeat). It was like playing 1.1.4 all over again!
  2. As you might suspect, I'm here to post "me too" and "+1" on this bug. I'd also point out that killing the game does bring you back to the choice between Continue/Heal, but it doesn't matter which you choose, the game will still hang. I don't know whether you can avoid the initial hang by always choosing Continue rather than heal when Kyra defeats Undead, but certainly once you've triggered the problem you are stuck until (I suspect) you delete your game.sav.
  3. When they say that the game hangs, that's what they mean: it hangs, there are no game elements that respond to input. You can't drag anything anywhere, not cards zoom, no buttons do anything other than click. The. Game. Hangs.
  4. Hmmm... TBH, I thought it was +2, but it might have been +1, which would be good 'cos then the modifiers are being done correctly in the first check. However, it's clear that something is badly wrong in the second check! As a result of this issue I've started taking a screenie of the "During this Scenario" screen for every Legendary Scenario I do. It takes only seconds and I have something to refer to if I need it.
  5. This appears to be part of a wider problem because I've had it with Justice Ironbriar. Looks like it might be a problem with any Villain that Summons.
  6. I updated to 1.1.4.1 and played one scenario to level my 5 Quest characters that were missing Feats. With 1.1.4 these characters would level, then enter the post-scenario rewards to gain multiple Feats and there would be a progression break. With 1.1.4.1 I was able to successfully award both feats (either 2 x Power or 1 x Power & 1 x Card). As all my Quest characters are higher than 31, I can't test your issue. However, if you're still stuck and the patch hasn't fixed it I think that you'll probably have to deleted your game.sav file (I do hope you are on Android, 'cos apparently it's pretty near impossible with iOS 8 or later). I've posted a toolkit that I use to resolve progression breaks. It includes instructions for deleting the game.sav file for the game: http://forums.obsidian.net/topic/89650-bug-when-replacing-card-from-hand-with-card-from-discard/
  7. See my report http://forums.obsidian.net/topic/89702-1141-progression-break-with-justice-ironbriar/?do=findComment&comment=1850988
  8. I don't understand: I met JI in 1.1.4.1 and this problem didn't happen. So something that was changed in 1.1.4.1 caused this. I didn't think the Erylium problem was a post 1.1.4.1 issue.
  9. Device: BlueStacks emulator OS: Android 5.1 PACG build: 1.1.4.1 Pass & Play: OFF Permadeath: OFF Mode: Quest Party Members: Lini, Valeros, Ezren, Seelah, Kyra Turn Order: per party Scenario: ? Difficulty: Heroic Wildcards: Driving Rain; Scenario: bury a card on discard Location: Deeper Dungeions Trigger: Seelah encounters Justice Ironbriar Excellent! So excited to be able to play Quest again and finally get my Feats awarded for the characters with missing Feats. So imagine my disappointment when on my very first play on 1.1.4.1 I get a Progression Break. Not only that but it's one of the really nasty ones that can't be fixed with a VRT and the Menu button launches the menu but none of the buttons work - so I'll have to kill the App and delete the game.sav! Here's what happened. Ezra had moved to Seelah's location to deal with Explosive Runes on his previous turn. At the end of her turn Seelah used Crusade to discover JI. On his next turn, Ezra returned to the Academy to try to rip through it leaving Seelah to deal with JI on her own reckoning she should be "man enough". Seelah Encounters JI, because she's alone (nobody loves a smug Paladin) JI rolls a D4 and gets a 2. Then the random monster is summoned, which is Diseased Rats. Seelah defeats the Rats with a Glaive of Shock (no reroll). Now, instead of being given a crack at the Villain, a second random monster spawns with the card semi-transparently overlaid on JI's card! The second monster is a Ghoul, which she also defeats using the Glaive and her "discard top card" power. All well and good, now she should get a go at JI this time. Nope! Seelah is now presented with her Explore/End Turn options, but JI is still on screen. Seelah's crusade reveals JI to be the top card of her location deck and the game progresses to Kyra's turn. JI is now show as active on Kyra's turn and now I have a progression break. UPDATE Killing the App and relaunching took me back to Kyra's turn and JI had been cleared up so he doesn't show in Kyra's location. Of course, because of the Examine bug that was introduced some time back, I can't see whether JI is still top of Seelah's location until it's Seelah's turn. Here's some screenies to show what happened - in sequence. I've also included my game.sav IronbarProgressionBreak.zip
  10. It's harder to workaround this on iOS than on Android, but this thread has a list of workarounds you can try http://forums.obsidian.net/topic/89650-bug-when-replacing-card-from-hand-with-card-from-discard/?hl=hammer&do=findComment&comment=1850190
  11. I had a Story Mode a set of 6 experienced characters that I specifically built a party with to run through on Legendary mode. They had all previously completed to the end of AP3. When I completed a Scenario on Legendary the display in the Scenario chooser showed the three ticks against each such scenario. But, I had to delete the party (by deleting the game.sav file) because of a bug that completely blocked progress (yes, completely). Now, when I recreate that party the Scenario selector looks like this: Note that the Normal level completion shows a tick, Heroic a star and Legendary shows "blank". Previously these were all ticks When I look at a Character in "Manage Party" the character shows as Completed for the Scenario, but I'm a little confused about the icons shown: I assume that the ticks beside each Scenario indicate completion of the Scenario, but what do the padlocks mean on each AP? Can somebody explain how Completion (including Heroic/Legendary) is tracked per Character/Party/Scenario and if there's some UI documentation for all this can somebody point me to it? Thanks very much!
  12. This has been widely reported since around October 4. It appears to be a result of the patch 1.1.4 "fix" to retrospectively award Feats that were missed due to a previous bug that didn't award Feats to characters unless they defeated the Scenario in which they gained enough experience to be awarded the Feat. So a bug in the fix to a bug. Sweet. There is no workaround for this one (though the Devs have said that they are working on a fix - but no ETA), the only solution is to delete the game.sav file for the scenario that triggered the problem. Of course if you do this you will lose the progress for all the characters - they will be reset to the state that they were before you started the Scenario. You will then have to avoid using those characters in any party until the Devs provide a fix. I have 5 Quest characters that are currently in this state - unplayable until a fix (the other 7 are all level capped, so I cannot play Quest mode unless I start new characters).
  13. There are a number of very similar "progression breaks" relating to discarding, burying or recharging cards (though I've not seen it with drawing a card). You could try the suggestions in this thread: http://forums.obsidian.net/topic/89650-bug-when-replacing-card-from-hand-with-card-from-discard/?hl=hammer&do=findComment&comment=1850190
  14. I was reporting what the Devs say in http://forums.obsidian.net/topic/89435-blessing-of-gorum-did-not-add-2-dice-on-melee-check/?do=findComment&comment=1847903 I haven't fully quantified it myself but there are a number of effects that affect specialised Blessings. Here are my observations: ​The automatic skill selector often (always on D4/D6 checks?) picks the wrong (single die) skill when you add a skill-related Blessing to a check. This can be fixed by using the skill selector to pick the skill that does give two dice ​Blessings that give two dice to specific checks still work even on D4/D6 skills (e.g. Abadar and Norberger) ​Gorum never gives 2D4 or 2D6 for Melee skill checks (I haven't confirmed this for other Blessings with D4/D6 checks but this may be masked by (1)) I think that the "convoluted logic" is an attempt to help by picking the better average value check, but they have inverted the logic test by accident. I haven't exhaustively tested it, but that's my suspicion (and anyway, it was reported internally by OBS so I'm assuming they have all the detail and I'm not going to waste my time)
  15. Yeah, the location where you drop cards can be critical - sometimes it's even fussy when I'm sorting out cards at the end of a scenario!
  16. Aha! Of course that's not listed on the active effects, but that makes the calculation: Gogmurt 10, AtT +6, Driving Rain +2, Goblin Fortress +2, Discarded "Thorns" -2 for a total modifier of +6 = Gogmurt, 18 still not 17! but maybe we're getting closer. Though the second example is clearly wrong (at least in terms of active effects)
  17. Device: BlueStacks emulator OS: Android 5.1 PACG build: 1.1.4 Pass & Play: OFF Permadeath: OFF Mode: Story Party Members: Amiri, Sajan, Kyra, Merisiel, Ezren, Seelah Turn Order: per party Scenario: 2.2 Difficulty: Legendary Wildcards: Full Packs, Retaliation, Crow Bait Location: Wooden Bridge Trigger: Sajan Encounters Rogors Craesby The title says all I need to say really. Sajan encountered RC and no dice were offered to roll! Ezren added in an Orb and Incendiary Cloud, still... no dice. I messed with the Skill Selector, did a VRT, exited to Main Menu, exited the game completely all to no effect. Clearly I'm going to have to Forfeit. Which I will do after I've captured the Saved Games folder and posted it here. SajanNoDiceVSRogorsCraesby.zip
  18. OK, here's my toolkit of bigger hammers (in the order that I try them) Vault round-trip (hit the settings button, hit the Vault button, hit the Back button when you're in Vault) Kill the App (this may, or may not work/be possible on IOS, I'm on Android) Forfeit the Scenario (hit settings, hit forfeit) - you'll miss out on any gold bonus, but will at least keep any Boons Delete the appropriate game.sav file* (this may/may not be possible on iOS, I am an Android user) Clear Cache for Play/Store/PACG Clear Data for Play/Store/PACG * these files are (on Android) located at Android/Data/net.obisidian.pacg1/files/PACG1_SAVE_GAMES/slotX, where X is 99 for Quest, 98 for Tutorial and 01-09 for Story mode (date stamp should identify the file. NOTE: steps more serious than step 3 ​will result in lost data​ including, but not limited to your current progress on the scenario in question. Hammers bigger than a size 4 hammer ​may result in lost data beyond the current scenario​ depending on the state of sync at the time. ​arse-covering disclaimer: I am not an OBS employee, neither am I an Android guru, or indeed an oracle of all things PACG. These steps are ones that I have developed through trial and error, based on what limited understanding I have gained about how the game does "stuff". Use this toolkit under your own cognisance.
  19. Do you mean that the Lock disappears, or that the character itself disappears (as though you had been able to delete it)?
  20. Here's a fun one with 6 Characters on Legendary. I had to take a lot of risks attempting to fail Combat Checks against Zombie Henchmen in order to keep the Modifier down - while also avoiding taking too much damage. Pretty hard when you have both Kyra *and* Seelah in the party! You really don't want a Zombie Horde to turn up with a party of 6 with this Scenario setup. Of course it did! The Zombie Henchmen that Summoned with the Villain (CZ) were waaaaaaaay tougher than he was - like by about 100%. We won though (helped by a rare good roll on a found Holy Candle and finding two Healing Potions). But I have to say that I didn't think we'd make it when I say the Scenario introduction screen.
  21. Hardly relevant here as the dice have no effect on the Check Difficulty
  22. I love the irony of banishing a Villain to close a Location! But I feel your pain!
  23. Yeah, note that Ethics Gradient says "most reliable" not "guaranteed". I've had a number of attempts to play the same sets of characters (not the same scenario, that would be ridiculously risky even though it should in theory work) and it's never reliably worked. I've lost experience and even levels. Personally I wouldn't recommend it without some serious experimentation on stuff you don't care about and with plentiful backups of data (not sure how/if you can do that on iOS)
  24. There seems to be a couple of issues with the post-scenario rewards screen at the moment. The Devs know about them, and have provided a workaround, but the description of the workaround is a little vague and I'm waiting for them to clarify. It's also unclear whether it's a universal workaround or whether it only works for the level 39 Role selection. Please see http://forums.obsidian.net/topic/89601-stuck-in-role-selection-screen-with-seelah-and-sajan/ but also note: http://forums.obsidian.net/topic/89420-quest-mode-level-up-glitch/ http://forums.obsidian.net/topic/89551-stuck-in-victory-screen-with-all-characters-dead/ http://forums.obsidian.net/topic/89417-cant-select-role/ http://forums.obsidian.net/topic/89301-bug-role-unlock-power-feat-unlock/ http://forums.obsidian.net/topic/89445-141-quest-catch-up-on-rewards-of-feats-hits-progression-break/ And that's just the ones where the helpful title gives me an idea what the issue might be. Some just have an unhelpful title like "[bUG]".
  25. As Hannibal_PPJV says: your first port of call should be a VRT (vault round-trip) this fixes all sorts of UI-related issues. After that there is an escalation of workarounds that I regularly use. If the VRT doesn't work, let me know and I'll post the escalation (which ultimately ends with applying a hammer to your device with extreme force and vowing never to play the game again )
×
×
  • Create New...