Aller au contenu

Photo

Tavorick Estate - Second Wave of Enemies Won't Trigger


  • Veuillez vous connecter pour répondre
5 réponses à ce sujet

#1
Leematon

Leematon
  • Members
  • 119 messages
I've reached the part of the game where Lord Tavorick is sent upstairs for protection while you build barracades and fight demons downstairs. I've fought off the first wave of fire mephits, but after defeating them, I cannot seem to progress any further. What triggers off the next wave of enemies? I've tried speaking to the various guards, but all I get is generic 'above their head' dialogue. I've also tried resting upstairs but that doesn't work either. Please help.

#2
kevL

kevL
  • Members
  • 4 061 messages
Are you familiar with DebugMode 1 console commands?

`
DebugMode 1
rs ga_start_convo("20_ballard", "20_ballard_interlude1", 0, 0, 1, 1)
DebugMode 0
`


no guarantee ... but hang around Ballard, controlling your main PC with no target, and try it

#3
Leematon

Leematon
  • Members
  • 119 messages
Thanks kevL, you're a star. That worked wonders.

I'd be interested to know what caused the glitch in the first place. I've tried loading from an earlier save to see if the problem happens againPosted Image.

#4
kevL

kevL
  • Members
  • 4 061 messages
what happens is that those first mephits are scripted to a Group, and when they're all died there's a function that's supposed to fire into a conversation automatically. Unfortunately, evidence (and experience) indicates GroupOnDeathBeginConversation( ) is neither robust nor reliable ..

my suggestion to anyone contemplating this, is use GroupOnDeathExecuteCustomScript instead


50/50 :)

#5
Leematon

Leematon
  • Members
  • 119 messages

kevL wrote...

what happens is that those first mephits are scripted to a Group, and when they're all died there's a function that's supposed to fire into a conversation automatically. Unfortunately, evidence (and experience) indicates GroupOnDeathBeginConversation( ) is neither robust nor reliable ..

my suggestion to anyone contemplating this, is use GroupOnDeathExecuteCustomScript instead


50/50 :)


Which begs the question, 'Why was this not addressed in a patch?'. Seems to me to be a general issue with GroupOnDeathBeginConversation, rather than an isolated problem in the Tavorick Estate.

#6
kevL

kevL
  • Members
  • 4 061 messages
lawsuit. About, what, 2 yr. ago?

The bigwigs decided they didn't like each other anymore, and so although there was a bunch of patch-stuff already in the pipes the Great Western Lawyers' Association [tm] said, "Well, we can't have that now, can we." So, what we're dealing with here is ...


Buford T Justice !