Aller au contenu

Photo

Coran and Wyverns


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

#1
Chaotic Clown

Chaotic Clown
  • Members
  • 23 messages
I recruited Coran on the first Cloakwood map.   I went straight to work on locating the wyverns cave and killing all the wyverns within.   I also cut down a handful more wyverns between travels as they set upon us in the Cloakwood.   I made avenues to the Temple (east of Beregost) where Kelddath Ormlyr (Mayor of Beregost) rewarded the group for slaying the foul wyverns upon which he removed a wyvern head and was forth coming with 2,000 gold.   I then sold all remaining wyvern heads to Officer Vai at the Jovial Juggler.

But just now while we were hunting Siren's and Felsh Golem's along the coast, Coran made a comment about needing to leave us to go and hunt Wyverns.   Is this normal?   I received no journel entry nor any comment from Coran upon killing the wyverns nor upon turning the head(s) in for reward.   Have I encountered a glitch?   And will Coran leave?

My install (if it helps) went as such.

1) Installed Baldur's Gate
2) Installed Tales of the Sword Coast
3) Patched Tales of the Sword Coast (official)
4) Installed BG1 Fix Pack
5) Installed Tales of the Sword Coast Game Text Update
6) Installed BG1 Unfinished Business

Perhaps I am jumping the gun and this is simply a quirk in Coran's long-tem dialogue.   But if it's not then I am hoping there is something I can do to correct this error.

I have just this night settled my party for the forseeable.   And Coran is a huge part of those plans.   It would be horrible to lose him.

#2
Chaotic Clown

Chaotic Clown
  • Members
  • 23 messages
Coran joined our group on Day 35, Hour 23.   That is the date and time of the journel entry signifying Coran's desire to hunt wyverns.

His comment came on day Day 48, Hour 21.   At the time of the comment Coran was outside the Flesh Golem cave located on the coast just south of Candlekeep.   He was idle for a time, as were the entire party save for Tigar (my fighter) who was going toe to toe with one Flesh Golem after another.   Tigar, who has a base AC -6, was buffed with Barkskin, Bless, Boots of Speed and a potion of Absorbtion to undertake this task!

I then travelled and rested for a period to move time forward.   I reached Day 53, Hour 13.   At this time, while leaving the game unpaused for a long period, Coran did not act out of the ordinary in the slightest.   He had neither a disgruntled comment nor a departing message.   And that is 18 days after that first journal entry.   I have saw the figure of 16 days thrown about as the time-frame associated with Coran and his wyvern quest.   I am not sure if that holds true but I figured I'd use it as a measuring stick, just incase it does ring true.

I'm thinking, or rather hoping that Coran's comment was one of exasperation at standing idle while there be wyverns out there to hunt.

I would rather not take it for granted, though.   So any fix would be welcome.   It would be my back-up plan to execute on the save just before Coran walks, should that occur.

#3
Son of Imoen

Son of Imoen
  • Members
  • 521 messages
this bug is encountered before. There's a CLUA Console command to let Coran know the wyverns are dead: SetGlobal("SPRITE_IS_DEADX#CoranWyvern","GLOBAL",1)

To open the CLUA Console, first close the game, open Baldur.ini with Notepad or another text editor, save and exit.

Start the game and once in the game, press CTRL+TAB to open the CLUAConsole, then enter above code.

Hope I got it right, don't have BG 1 at hand now.

#4
Chaotic Clown

Chaotic Clown
  • Members
  • 23 messages
I finally found my way to the Baldur.ini file.   The .ini did not show as part of the file.   I instead located it via the notepad icon with a little cog sprite that accompanied the file name Baldur - once there (thanks to notepad) I entered Cheats=1 directly beneath [Game Options].

I then started up Baldur's Gate and loaded my save game.   Once there I entered exactly...

CLUAConsole:SetGlobal("SPRITE_IS_DEADX#CoranWyvern","GLOBAL",1)

... while in game.   I am not sure what is supposed to occur, if anything.   But Coran offered no response to acknowledge that the wyvern was dead and his quest thus complete, nor was there any entry to the journal.   Perhaps this is exactly what should occur if this is a cheat to simply have Coran accept that the wyvern is dead, and act as if the quest never was.   And if that does the job and has Coran never mention wyverns again, nor leave the party, then it is heaven sent.

My thanks to you, friend.

I then quit out of the game and opened up the Baldur.ini file once more.   At the bottom it read as such:

[Lua Edit]
String0=CLUAConsole:SetGlobal("SPRITE_IS_DEADX#CoranWyvern","GLOBAL",1)
String1=
String2=
String3=
String4=
String5=
String6=
String7=
String8=
String9=

I then deleted the entry for String0= so it read as the others do.   Presumably reversing the command as if it never occured?

I may play on without this fix until such a time as I need to implement it.   Why?   To see if Coran ever repeats his desires to leave the group to pursue hunting wyverns.   And more so, to see if he actually does hand in his resignation and depart.   I save regularly enough.   So I should be able to counter-act his potential departure with minimal back-tracking, if needs must.

Out of interest, if anyone cares about such a minor detail.   What should Coran say upon the death of these wyverns, if anything?   And is there a journel entry to verify the quest has been completed?   I remember when I completed Safana's quest there was a dialogue box to click "continue" and or "end dialouge" to progress.   It is very minor but, it gives a sense of closure.   I dislike loose ends.   The vial of mysterious liquid (that contaminates iron) was one such loose end that I was thrilled to see tied up and chalked off with the Unfinished Business mod.   It's a shame then that Coran's quest, at least for me, is broken.   It takes away from the experience to have a something remain forever incomplete.

Is Coran and the Wyverns a common mishap?   Does it occur accross the board or, for example, will the addition of Tutu (for future playthroughs) help resolve such instances?

#5
Son of Imoen

Son of Imoen
  • Members
  • 521 messages
I did a search for 'Coran wyvern leaving bug' on Google. As I couldn't reproduce the same handy finds I got yesterday, I'll post the finds that are relevant for you:
http://forums.gibber...showtopic=18104
http://forums.gibber...showtopic=17044
http://forums.pocket....html#msg319181

As you can see, the wyvern quest being bugged is quite common.

Changing the global variable does not trigger a response from Coran. It's only an acknowledgement for the game engine that the quest is finished and no further action is needed. As such, it's a workaround, not a solution.

To make you even more experienced in debugging Baldur's Gate, I'd like to point to the usefulness of Gatekeeper (http://www.mud-master.com/gatekeeper/). It (and it's BG2 counterpart Shadowkeeper), allow you to change information stored in savegames. It can be used for cheating, but a more popular use is just to resolve bugs: the Global variables, such as the one mentioned above, can be found on a tab inside the program Gatekeeper, if you open your latest (or any other) savegame. What you did with the CLUAConsole, can also be achieved this way, as well as being able to check what it's value is.

I'm sorry I don't know an actual solution with Coran actually making dialogue how he is pleased. My memory is vague as how he should react. I often got no reaction at all from him, if I remember well (it's not without a reason UB included Coran and the wyverns in it's mod, it was already broken in the original game itself).

Modifié par Son of Imoen, 09 août 2011 - 09:16 .


#6
Chaotic Clown

Chaotic Clown
  • Members
  • 23 messages
Thanks for taking the time to help out by looking into all of this for me.   It's much appreciated.

All things considered I believe that the console command is the safest bet, in regard to the simplest of solutions with the least disruption to my plans on this playthrough.   I am not going to be running another character (game) alongside this one, and I am aiming to complete this playthrough before importing my character into Baldur's Gate 2.   I'd rather knock it on the head here and now, and relax in the knowledge that Coran will not be going anywhere.   Especially not after I killed those quest related wyverns (which are marked unique) and turned the head(s) in for reward, as recognised by the Mayor of Beregost.

I downloaded Gate Keeper, by the way.   I'm not sure how to use it to adjust these sort of quest related variables.   But it looks good for character editing.   I put 10 points into Stealth for Imoen prior to making the decision that she would not use stealth what-so-ever and would instead dual to an Illusionist once her traps and locks were high enough.   I don't consider it to be bending the rules too much to redistribute those 10 points accordingly.   Good times!

Thanks, friend!

#7
Gate70

Gate70
  • Members
  • 3 208 messages
Gatekeeper doesn't show global variables; Swordcoastkeeper does.

#8
Son of Imoen

Son of Imoen
  • Members
  • 521 messages
Sorry for the misinformation. I wrongly asumed it did, but I haven't used Gatekeeper for years. Only my first playthrough was vanilla BG1, but because of that experience (with the inventory and lack of NPC banters mostly) I became Tutu-addicted and so have only used Swordkeeper since.

#9
Gate70

Gate70
  • Members
  • 3 208 messages
I enjoyed the vanilla game from launch so hit all the bugs of the original until they got patched. TotSC was a game-breaker and I was lucky/stubborn enough to complete it but the more I tried the harder it got to have a game that would finish. The patches made a huge difference but Shadowkeeper then SwordCoastKeeper helped understand what was going wrong. Gatekeeper felt more like a cheat utility in comparison as the variables were the essential bit.

Tutu and BGT are both amazing achievements in my opinion, refining the original concept to include some hindsight.