Jump to content

Sylvanta

Members
  • Posts

    149
  • Joined

  • Last visited

Everything posted by Sylvanta

  1. Strange. We're looking into it!
  2. If so, under iOS, the game will officially run on only the iPad Air 2 and iPad Pro. As such, I'd highly recommend ensuring it will run without issue on 1 GB iPads. If so, under iOS, the game will officially run on only the iPad Air 2 and iPad Pro. As such, I'd highly recommend ensuring it will run without issue on 1 GB iPads. I am running on an iPad 4th generation and have not experienced the game crashing at all. It may be a combination of cpu and ram leading to the performance issues. Ebee tried my iPad and remarked that it was smoother and crisper than the tablet she was playing on (before her husband got her a new one). According to wikipedia (man I hate saying those words) the iPad 4th generation has the following specs: The device has an Apple A6X SoC which comprises a 32-bit Apple Swift dual-core CPU running at 1.4 GHz and a quad-core PowerVR SGX554MP4 GPU, 1 GB of RAM. A good thing about Apple devices is they almost all run the same type of GPU. Android, on the other hand, has several different ones. If you get a build not optimized for your Android GPU, performance issues can be a problem. We've hopefully addressed this with the Beta 2 build. (I would quite happily be wrong about my initial statement regarding 1GB RAM devices - I want as many people as possible to be able to play the game! ) It was that forced discard, that I was not doing. Many thanks! It was not too easy find. In most cases this game does give graphical hint that you can do something. Some graphical clue like site and character powers have would be nice, or then the discard mode should be forced each round before ending the turn. I'll pass this on and we'll see what we can do. We've tried to avoid prompting every turn as we thought it'd be annoying, but it should definately be more obvious somehow. I agree! Known bug - I'll get that added to the list of known issues.
  3. Greeting and Salutations! I know a number of you had some performance issues with the Beta 1 build. As you download Beta 2 and start playing, I'd like to hear feedback on the performance. Has it improved? Is it the same? Worse? (hopefully improvements all around!) When you respond, if you can provide your device make and model (and model # if you can find it) so we can keep track. I expect performance improvements with this build, but only you folks can say for certain! Note: (Android Only) If you have issues loading Beta 2 in the sense that you get stuck on the "powered by Unity" loading screen, this is a different issue. Device information, however, is especially helpful here as well! Feel free to throw such issues into this thread, but please clarify that it's the issue with getting stuck on the loading screen.
  4. iOS updates are now available as of 9:45am pst. Whats the make and model of your Android (Model # is most helpful)? There's a few possibilities, the most likely requires knowledge of your device.
  5. That's a bug! It's a holdover from an earlier time long, long ago where we didn't quite understand the turn order... we've since figured that out (as much as you can anything in this game ) but that got overlooked. Hmm.... appears I have some fun to watch. Edit: Perhaps I'm just tired and missing something - but I didn't see any fun. Perhaps I am in need of further clarifications.
  6. The Blessing issue is known and should be fixed in the update. In Poison Pill, for the harder difficulties (Heroic and Legendary) we removed the bonus to ally acquisition. Always check the text! Thanks!
  7. I'm glad to hear you're enjoying it despite the bugs! The leveling rate is a known bug - we definitely don't intend for you to hit level 5 after a single scenario. Your first suggestion kind of leads into my response to the second. For the second, you should be able to create "new" versions of existing characters (its why we have the nickname feature, afterall). So if you don't want your level 5 Merisiel to be in a starter group, but want that character, you can trade her out. This also (flipping over to suggestion 1) allows you to play multiple versions of the same character with completely different skills and card setup. So while it's not quite what you're looking for, we do provide a means for it. Thanks for the screenshots! We'll check into the issues there. Quest mode should be functional, but we'd seen issues internally where you couldn't always start the scenario. There was definitely an issue in the initial build where it looked nonfunctional as there was a lot of missing text. This should be resolved in the update.
  8. Fixed in the update!
  9. Feel free to send it off to me.
  10. Goblin Warchanter is... well, to put it nicely, a problem child. I don't think the updated text made it to the original beta build, but we have modified it from a Before You Act check to a restriction that only comes into play if you attempt to use a card it restricts. So, how it should play, as an example: - Valeros encounters the Warchanter. It's combat, because he hasn't tried to use any weapons yet. - He reveals a weapon, and now is prompted to roll the wisdom, since the Warchanter restricts weapons and spells with attack trait. - He fails (not his strong suit, afterall) and can't play his weapon. - Harsk jumps into the fold to help by discarding a Crossbow from another location. The Warchanter power correctly applies here vs Harsk - he has to roll Wisdom and pass to play his crossbow. That part with Harsk - other characters aiding the check with restricted cards - is the main source of our problems with this card. It's definitely not super obvious how it works, especially for any experienced players that are familiar with it being a Before You Act check. It's weird, and something we're still trying to figure out how to communicate well, without being extremely annoying. I've heard a few reports on Warchanter breaking the game - we're working on it! As far as the missing characters, this is a known issue that should be resolved in the next build. In the meantime, we've granted you gold that should cover the cost of lost characters.
  11. Warchanter is a problematic Goblin. His check is for any character that plays a weapon (including Harsk discarding a crossbow). This rule has created a unique set of issues for us. The current resolution is to change it from a Before you Act, to what essentially amounts to "when you try to use" check. I'm not sure the text update made it into that build, but it'll be in future builds. So, for now, you don't perform the roll until you try to use a weapon or spell with the attack trait. Did you fail the check vs Erylium? We had a recent issue where if you failed the combat check and subsequent wisdom check, you'd encounter a progression break. It seems like devices with 1GB RAM aren't quite able to handle this game in extended playsessions. We'll keep an eye on that, but realistically I'd expect our official support be for greater than 1GB RAM. To keep that authentic Pathfinder ACG experience alive! It is also why the dice are blue! The first thing I did when I bought the physical game was to go out and buy some new D4s that I could actually read- whenever I take D4-1 damage (or anything else requiring a D4 in the digital game) I have absolutely no idea what's going on +1 to the "readable dice, please!" "Authenticity to the physical game" isn't justification enough for a die that is more difficult to read, imo. I'll throw in a suggestion to replace it with top scoring die. Soldier adds D4 to a melee check only, not a Strength check - as Merisiel doesn't have Melee, she would roll D4 if using Melee, + another D4 for the soldier, so this would be correct. But you should still be able to switch back to using Strength if you cancel it. As strength is not melee, as MightyJim notes, you correctly had 2d4. To change the check back, you'd need to open the skill check panel (black tab with the check value) and select the check type desired. That panel is on our list of things to make more clear that it exists.
  12. Sounds like a bug! I'll look into it.
  13. I've submitted a bug for just that. Since we allow both play by drag and play by interacting with buttons, we should be consistent across the board with the option to do either.
  14. When the game tells you to login to your google account - are you attempting real money purchases? Gold and Season pass are real money only, and this being a dev build they're locked out. Any purchase made with gold should work. I'm seeing some of the weirdness you guys are reporting, predominately when restarting the app, however. On the problem devices, did you ever manage to login/was the account created on it?
  15. The first part is definitely an issue with a corrupted save file. I'm reasonably certain the weird UI issue is related. We're looking into it.
  16. We're looking into this. I haven't been able to reproduce it internally, and others have had no problems purchasing the adventure decks. Where are you guys accessing the store? Is it the same from all access points? (Main screen, Adventure Screen, Within a game, etc) Edit: Managed to get a repro on it. Thanks for the feedback!
  17. Valid points! We strive to make things as clear as possible, and obviously we've not done so well here. I'll pass it on and see what we can do to better clarify this scenario.
  18. I have a bug in for this I submitted recently. I believe in consistency and having contextual buttons everywhere!
  19. I don't know what it'll take either... but I'll pass it on!
  20. I think the best you can offer is just feedback on the experience. Despite being WIP, does it seem like it'll be fun? What do you like/not like about it? Is it something you think you'd partake in for release? As far as bugs, just a heads up on whatever shenanigans occur is great. That being said, we have a known issue where you'll be told in the Tutorial sometimes.
  21. Closing an Empty location comes at a specific place in the turn order - immediately after exploration and before ending the Turn. Kyra can't use her power here after attempting to close as she is officially no longer in her explore phase. (Per the Wrath rulebook, page 9 (Coming after Explore and before End of Turn): "Close a Location: If your character is at a location that has no cards remaining and has not been closed, you may make one attempt to close it at this time). So, not a bug, but, I concede that it's not clear that it's not a bug. Sneak BYA invisible Dice: Known issue internally. Already fixed for the next build. Token of Remembrance not having recharge on card: Something I've wondered myself. Its on the list, though! Runaway Scout: This is an extremely rare issue that we've been trying to track down for a while. If you run into it again and can provide more information about previous explores/the previous turn, it would help us tremendously! Swallowtail Festival's power is specifically for "start of your turn". It's implemented that way in part to help remind you that you can use it, but only before you do anything else. Kyra's power, on the other hand, isn't strictly "start of turn", but simply "before exploration". Theoretically, you could start at another location, use cape of escape to move to the Swallowtail Festival, and you wouldn't be able to use the location power. However, if you were on Kyra and used the cape of escape to move, you could then heal at the new location provided she hadn't explored at the previous one. Losing a turn: I concur. It is entirely too subtle right now. Cancelling actions: Cancelling only affecting the targeted character is actually a recent change. This is the case due to problems with the Warchanter (a very problematic goblin, he is). Its not to say we won't find another solution, but for now this is what best works with Warchanter shenanigans. Game Breaker: Definitely a code issue and not a connectivity issue. Thanks for the feedback! We'll definitely get to work on this list.
  22. Hey folks! Whenever you run across a bug, as a general rule of thumb, the more information you can provide us, the better. As the experienced Pathfinder players well know - this is a very complicated game, and that complication can cause many a strange bug. That being said, if you can provide as much of the following information (when relevant!) when you run into an issue, QA will be forever grateful to you. Gameplay Is pass & play on? Is permadeath on? Tutorial, Story Mode, or Quest Mode? (If not quest mode, did you recently enter it?) Characters in Party Location of each character Turn Order Scenario & Scenario Difficulty. If on non-normal difficulties, which wildcard powers are in play? What card was encountered when the issue occurred? (Or check, or card just played, etc) Did the issue occur on the first explore or a subsequent explore? If subsequent, what card did you last encounter? What was it's resolution? (IE, you just encountered an enchanter and failed the check, and on an additional explore you ran into a blessing of the gods but didn't auto acquire it) Did other characters aid the check? What did they use to aid it? Was the encounter a Horde? (Skeleton Horde, Goblin Raid, Zombie Nest, Zombie Horde, Garrison Location Power w/ multiple characters, Henchmen encounter in Black Fang w/ multiple characters) Also, if possible, provide a screenshot! Often a screenshot itself will tell us much of this information, but there are so many things that can cause a given issue, that it's better to err on the side of more information than less. Thanks to everyone for all the feedback submitted so far!
      • 3
      • Like
  23. We're looking into it. Thanks for the info!
  24. Fun fact - you actually remain logged in (or should) each time you restart the game. It's just not obvious with the welcome screen appearing each time. Don't worry! We have bugs in for that, and you shouldn't be prompted on each login in the future.
×
×
  • Create New...