I think I nerfed a paladin stronghold quest.... possible spoiler

Remove all ads!

I'm doing the part of the paladin stronghold quest where you are to protect Tyrianna from assassins and deliver her to her uncle (or whatever). At one point, she comes downstairs and tells you that she saw someone outside her window. The assassins come in and I kill all of them before one manages to get upstairs (which I was pretty proud of myself over, but anyway).

I started to go upstairs to make sure that she was safe but about the same time the party started to go upstairs, the game triggered a cut-scene. It never did load the scene though -- what it did was show me at the top of the stairs (Tyrianna's room), her standing at the other end of the room. No mouse activity; non-responsive to keyboard commands; no side panels; in short, reboot and reload.

Fortunately there was an autosave; unfortunately it saved the "triggered" cut-scene sequence. I can interact with Tyrianna now but all she says is "go downstairs and see if there are any more". I know her uncle is supposed to spawn but for 2 hours (realtime; not gametime) nothing happened -- other than everyone complaining about doing nothing.

As I see it, here are my options:

- delete the game entirely and start over (not thrilled about that option)
- head over to Radiant Heart and take my chances (not thrilled about that option either)
- figure out the variable to spawn her uncle and adjust it to where he shows up and I can move on with life.

I've completed the paladin stronghold quests more times than I care to count and never had any problem; well, other than never being allowed to rest in the stronghold, but that's a whole other topic.

I'm rambling. Any assistance would be greatly appreciated.

 

I think the Sorcerer's Place patch has a solution to this, although I don't know if it will work now that you have already initiated the bug..

Maybe you should also keep a little more savegames than just an autosave.

I don't know the variable for the guy to arrive, but maybe you can just spawn him. I don't know the guy's name, but I'm sure you can look it up in Shadow Keeper.
Then type:
CLUAConsole:CreateCreature("thatguysid")
and he should spawn. I don't know if you could talk to him then or anything, but it's worth the try.

If this doesn't work, maybe you could e-mail the maker of the SP patch about the variable (unless someone else here knows it of course).

 

The regular save that I have goes back about 4 game days so loading that, while an option, is still not one I relish.

I don't think this necessarily qualifies as a bug. My games are all unmodded and unpatched and up until last night, my paladins have never had any problems completing this part of their stronghold quest.

As I recall, her uncle's name is Hurgis and I thought about just spawning him like that but wasn't certain if there was something other than that console command that might affect the global variables.

 

As far as I know there are three things that trigger globals:
1. Normal in-game stuff (but this will only happen once)
2. ShadowKeeper or another editor (if there are any)
3. CLUAConsole.

And I think it is a bug. I think this happens if you leave the area while a global is being triggered. In this case: the global for that guy spawning is triggered, but since the game delays somewhat, he isn't immediately spawned. When you leave the area, he can't be spawned in the previous area (I think) and when you come back, the game thinks everything went as it should have.

I thought you only had an autosave, since you said that you would have to start all over again (I think).

And what's wrong with using the console? You aren't cheating if you spawn a guy that should've be there in the first place.

 

Believe me - I am a BIG user (and occasionally abuser) of the console when I need to correct things that go wrong. What my concern is is that since this is part of a quest, there might more to it than just spawning the guy.

Anyway, I can give it a shot and see what happens. Can't screw it up any more than it already is, I suppose.