Jump to content

Poulscath

Supporter
  • Posts

    41
  • Joined

  • Last visited

Posts posted by Poulscath

  1. I'm curious as to why you're doing NMM support for Morrowind first though.

    They will both be up at the same time if I am correct. Oblivion has been in the front forever and if these sites are put up any seconds apart, you can expect Oblivion to be first. But they should both be up within the same day at the most, if I am reading correctly. Now if you are talking about TESNexus before other Nexus sites, it might not be first. Who knows?

    Actually, I was wondering why the web sites had to wait for the Nexus Mod Manager (NMM) to support Morrowind first, not which web site would be first.

     

    Edit: Chopped excessive quoting.

  2. We are currently working on getting Morrowind support in to NMM, at which point we are going to separate TESNexus and have Morrowind Nexus and Oblivion Nexus. TESNexus will cease to exist, but will redirect to Oblivion Nexus. Until then, things will remain the same.

    Excellent, thank you :)

     

    I'm curious as to why you're doing NMM support for Morrowind first though.

  3. None of the developers are legally obliged to add any type of warning before the scan.

    How do you know that?

    Basically:

    Get some bloody self-control! The only thing keeping you from stopping the scan is your own lack of willpower. Grow up, seriously.

    The problem isn't stopping the scan, it's that it shouldn't even start without asking. :wallbash:

     

    As for me, I prevented the scan by the simple method of uninstalling NMM and using Wrye Bash instead so I'll not be following this thread any more.

     

    Edit: saw this right as I posted

    If NMM is illegal in your country, don't use it.

    Those people aren't concerned that it's illegal to use but rather that it's doing something illegal. Quite different.
  4. On sale again for £5 for today (another 23 hours from this post time) at GamersGate again.

     

     

    They really should list the names of the expansions they include in the NWN Complete one, instead of just "3 expansions" for NWN2. I would want to know that it includes Mysteries of Westgate, the only expansion I don't have. I guess that it does, since the graphic behind the title shows the MoW cover art.

    I got it last sale and it included the following (looking at my CD key list):

     

    Neverwinter Nights

    NWN: Shadows of Undrentide

    NWN: Hordes of the Underdark

     

    Neverwinter Nights 2

    NWN 2: Mask of the Betrayer

    NWN 2: Storm of Zehir

    NWN 2: Mysteries of Westgate

     

    Edit: Formatting fail & reflink

  5. What makes it awkward is that it's inconsistent. Every other supported game series has either a site per series or a site per game. Only TES has a mixed setup with one game on its own and the other two mixed together.

     

    Note that I'm not criticising the Nexus for this, it was undoubtedly the right decision at the time but may be worth revisiting due to changed circumstances (Skyrims release and aren't IGN reducing support for the fan sites like PES?)

  6. Can anyone tell me if the ears from this picture are available anywhere? I've searched but can't find anything.

     

    They look like they might be from the Ren's Strangers race.

    Hmm, they're apparently called "Kikaimegami's long elf ears" but I can't find a trace of that anywhere. Google has failed me :(

  7. Sorry to necro this thread but I just ran into this problem and might have found a workaround.

     

    I triggered it after accidentally uninstalling Frostcrag while switching from Reborn to AFK.

     

    After that, the Frostcrag doors all have the test bruma name whenever I build a bashed patch with CBash. If I switch to a Python Bashed Patch, the bug disappears and the correct names show. This is with default settings on both patches.

     

    This is with Wrye Bash 295.2, CBash 0.5.3

     

    So if you're having this problem, try a Python patch to see if that fixes it :biggrin:

     

    Edit: Turns out this is the C.Name bug listed here. Use the python patch until it's fixed.

×
×
  • Create New...