Difference between revisions of "Talk:Bethesda Tutorial Radiant Quests"

From the CreationKit Wiki
Jump to navigation Jump to search
imported>Lmstearn
imported>Lmstearn
Line 65: Line 65:
To avoid the solitary "Sorry, Not right now" a workaround might be to:
To avoid the solitary "Sorry, Not right now" a workaround might be to:


*Use "optional". Another location should be chosen. When the alias is "None" for any alternatives, implement another "failsafe" topic (should we reconsider ReachwindEyrie01?), then refill the alias with
*Use "optional". Implement another "failsafe" topic (should we reconsider ReachwindEyrie01?), then refill the alias with
     Alias_ThiefLocation.Clear
     Alias_ThiefLocation.Clear (just in case)
     Alias_ThiefLocation.ForceLocationTo(Some_"failsafe"_location)
     Alias_ThiefLocation.ForceLocationTo(Some_"failsafe"_location)



Revision as of 16:45, 7 February 2015

Alias_ThiefLocation.GetReference().AddToMap() is giving me problems: claiming that 'GetReference' doesn't exist, etc. I've configured ThiefLocation as shown and for whatever reason, it won't work. Any info on what I'm doing wrong? --Roarian 22:45, 11 February 2012 (EST)

Found what was wrong with the existing explanation and fixed it to the best of my ability. --Roarian 00:39, 12 February 2012 (EST)

Engine Bug regarding the Map

Get the radiant quest to kill the thief at Bthalft and return to Mixwater Mill via clicking "M" on the quest objective. The quest arrow on Mixwater Mill shows up all fine and dandy, but the mill icon to facilitate fast travel never pops up. Travel to another location e.g Broken Limb Camp, and the Mill icon returns. The bug might not be replicated at higher resolutions (mine was 1366 X 768)--Lmstearn (talk) 2015-02-04T06:31:57 (EST)

Dirty Thief is still at Reachwind Eyrie

Even though Reachwind Eyrie is not a radiant location anymore, the Dirty Thief (albeit disabled) is still there. This may not be of concern to all perfectionists, but placed him in a corner of MixwatermillWorkershouse anyway.--Lmstearn (talk) 2015-02-06T00:11:27 (EST)

"But That is Left as an Exercise for the Reader" -Hold Locations

--Spoiler Alert--

  • Create 9 location aliases for the Holds for the specific locations:
   EastmarchHoldLocation
   FalkreathHoldLocation
   HaafingarHoldLocation
   HjaalmarchHoldLocation
   PaleHoldLocation
   ReachHoldLocation
   RiftHoldLocationHoldLocation
   WhiterunHoldLocation
   WinterholdHoldLocation
  • Reorder the Quest Alias list thus:
   ThiefLocation
   LocationMarker
   Thief
   Bendu
   Amulet
   Gilfre
   All the hold aliases
  • Go to Dialogue Views and add a condition in the Topic info for GSQ01MeetingBenduYes, "Oh Thank you so much...":
   Function Name: GetIsEditorLocAlias
   Fill the alias with the name supplied for the EastmarchHoldLocation (mine was EastmarchHold)
   Run on Quest Alias, and choose the LocationMarker for the Alias.
  • Change the middle part of the info response to something like: "It's been taken to a place somewhere in the Hold of Eastmarch." and change the recorded wav file accordingly.


  • Right click on the white topic info box and select copy. Do this 8 times, the new topic boxes may require resizing and re-positioning during the copy.


  • For each Hold: Fill the condition alias with the appropriate Hold, change the info response, and make a new recording.--Lmstearn (talk) 2015-02-06T05:50:34 (EST)

Some ThiefLocation Aliases not Filling

This happens in perhaps as much as 1 in 3 game loads. But here we are using a game save that's more than halfway to completion. Some of the radiant locations have already been reserved by other quests. In an attempt to get an idea of what they are, trying something like

   Location myThiefLocation = Alias_ThiefLocation.GetLocation()
   Debug.MessageBox(myThiefLocation)

in the Stage 0 fragment. Unfortunately this will fail as scripts will not run until all aliases are filled.

There is also the possibility of some loctypeBanditCamp locations not belonging to a given Hold either due to error or USKP corrections. Each member of the suspect subset of the 31 locations (less with Bosses) must then be tested individually.

To avoid the solitary "Sorry, Not right now" a workaround might be to:

  • Use "optional". Implement another "failsafe" topic (should we reconsider ReachwindEyrie01?), then refill the alias with
   Alias_ThiefLocation.Clear (just in case)
   Alias_ThiefLocation.ForceLocationTo(Some_"failsafe"_location)
  • Complete the current quest (can we suppress the quest complete message?) and use "failsafe" locations in a duplicate quest. Of course, a script that has the facility to duplicate any such number of quests in-game would be fabulous.
  • Ideally these locations are best reserved at the onset of a new game. New game, anyone? :P --Lmstearn (talk) 2015-02-06T16:54:26 (EST)
Tested for locations in the Eastmarch area and found that StonyCreekCave met the criteria for a radiant location, but would not fill. Turns out it was explored in game for the Finn's Lute Quest and had not reached the 10-30 day respawn threshold. So the question for posterity being: Is there a radiant dungeon "available" flag that can be used in conditions? No.--Lmstearn (talk) 2015-02-07T08:06:50 (EST)