File information

Last updated

Original upload

Created by

TheLadyVulcan

Uploaded by

TheLadyVulcan

Virus scan

Safe to use

8 comments

  1. Batniel
    Batniel
    • member
    • 1 kudos
    Is it safe to assume from the location of the quest that the new update to TR broke it?
    1. TheLadyVulcan
      TheLadyVulcan
      • premium
      • 19 kudos
      Very likely! Possibly some other bits too. Once I have some time between life stuff I'll update my mods to work with the latest TR release.
  2. arachnidzpr7
    arachnidzpr7
    • premium
    • 2 kudos
    Neat mod. Love quest mods that have dialogue choices and reactivity. it works flawlessly too. Kudos!
    1. TheLadyVulcan
      TheLadyVulcan
      • premium
      • 19 kudos
      Thank you!
  3. EPIPHANESXLR
    EPIPHANESXLR
    • member
    • 6 kudos
    Safe to merge?
    1. TheLadyVulcan
      TheLadyVulcan
      • premium
      • 19 kudos
      Do you mean if it's safe to install to an ongoing playthrough? If so, then yes it should be safe. It's largely self contained and only the exterior part (as seen in the screenshots) might cause conflicts, but only if another mod makes changes to the location. It has also been cleaned by TESAME, so should be good to go!
    2. EPIPHANESXLR
      EPIPHANESXLR
      • member
      • 6 kudos
      Thanks for the reply. Also the sword inside the tomb to me looks like a green exlacamation mark but ive installed all the files. In nifskope the sword looks okay. Just me or anyone else?
    3. TheLadyVulcan
      TheLadyVulcan
      • premium
      • 19 kudos
      No problem!

      As for the exclamation mark thank you for reporting it! I've had a look and I suspect it's that I've packaged the nif incorrectly. It should be under Meshes/TLV/w/chitin_othral.nif.

      I'll get a fixed version up soon. For now creating a new folder called w under Meshes/TLV and placing the nif in there should fix it.

      EDIT: My apologies I had a brain fart, I previously said Textures/TLV when I meant Meshes/TLV in this post. I have now published v1.2.1 which should fix the exclamation mark.