Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="Ruin Explorer" data-source="post: 9191633" data-attributes="member: 18">If that's the case, you might want to avoid generalizations that don't mention this is merely your experience.The reality is that a lot of timed events can in fact be kicked off without you noticing, because as noted, proximity to the place where the events occur is usually the trigger, and you often don't have to be very close - sometimes not even within sight of it - to trigger the timer. You only saw this with Grymforge, but it's very easy for similar things to occur with a lot of other events. With Grymforge I don't think the timer does usually start just on zone-in (if it does, it's very generous, and I don't think it's very generous), but like I said, a lot of these can trigger without you actually having gone particularly nearby. Adding to the problem are apparent bugs - some people had issues where, for example, Waukeen's Rest triggered when they'd barely left the Nautiloid. That specific one seems to be fixed but I couldn't say for sure, and Grymforge may have some similar issue where for some players, it just kicks off.As a general point I broadly agree that the easiest way to deal with them is to Long Rest before exploring any new area. This has the unfortunate side-effect, however, of making the game terminally easy on Normal, and not particularly hard on Tactician, because if you're continually/frequently Long Rest'd, you can really blast through stuff.Hopefully Larian keep working on this - by the time they get to any enhanced edition or whatever maybe they can make it so none of this stuff triggers without a clear addition to your quest journal. The quest journal remains probably the weakest part of the BG3 package.</blockquote>

Verification