Author Topic: Emptying the standard palette  (Read 465 times)

Legacy_Rubies

  • Hero Member
  • *****
  • Posts: 508
  • Karma: +0/-0
Emptying the standard palette
« on: July 11, 2012, 07:27:41 pm »


               Probably quite an odd question but I recall something about palette editing - I just can't find any mention of it at the moment.

I'm trying to totally empty the standard vNWN palette of items - any time a DM spawns one of the vanilla NWN items it crashes everyone in-game (we've cleared out like nearly all of the baseitems.2da, so everything except bows, torches and some other things are pretty much a no-no), which you'd think we would've gotten over by now, but it still happens from time to time and it's incredibly annoying.

Does anyone know how to go about clearing the standard palette out, or should I re-add those lines with some sort of invalid item instead?
               
               

               
            

Legacy_henesua

  • Hero Member
  • *****
  • Posts: 6519
  • Karma: +0/-0
Emptying the standard palette
« Reply #1 on: July 11, 2012, 09:30:01 pm »


               Why not replace the standard palette items with useful resources?
               
               

               


                     Modifié par henesua, 11 juillet 2012 - 08:30 .
                     
                  


            

Legacy_Rubies

  • Hero Member
  • *****
  • Posts: 508
  • Karma: +0/-0
Emptying the standard palette
« Reply #2 on: July 11, 2012, 09:44:27 pm »


               It seemed really excessive to replace every item/trap/etc entry for the sake of avoiding crashes, or adding a heck of a lot of fallback models that didn't really do anything; unless that isn't what you meant. I suppose this is the kind of thing I should've done before filling the custom palette - hopefully they're slightly interchangeable so I can convert it to a standard palette. Does modifying the .itp files accomplish this fairly easily?
               
               

               
            

Legacy_OldTimeRadio

  • Hero Member
  • *****
  • Posts: 2307
  • Karma: +0/-0
Emptying the standard palette
« Reply #3 on: July 11, 2012, 09:51:50 pm »


               Rubies, might this be some...help...sort of?
               
               

               
            

Legacy_Rubies

  • Hero Member
  • *****
  • Posts: 508
  • Karma: +0/-0
Emptying the standard palette
« Reply #4 on: July 11, 2012, 10:06:50 pm »


               That'll be really helpful once I manage to clear out the vNWN palette; thanks! '<img'>
               
               

               
            

Legacy_henesua

  • Hero Member
  • *****
  • Posts: 6519
  • Karma: +0/-0
Emptying the standard palette
« Reply #5 on: July 11, 2012, 10:52:30 pm »


               I mention that because it is something I am doing now. Just as appears to be the case with you, the standard palette is useless to me.

Any item that you are not spawning from the palette can be given a resref that overwrites the standard asset and thrown in a HAK.

The method that Pstemarie discovered (in the link above) is the way to do it if you only want the asset to show in the standard palette. Otherwise the blueprint will show up in both palettes which might be the best way to handle it if you are using existing custom resources to replace standard ones. The reason being that if those palette items disappear from the custom palette you might confuse your building team.

Anyway, let us know how you solve this.
               
               

               
            

Legacy_Rubies

  • Hero Member
  • *****
  • Posts: 508
  • Karma: +0/-0
Emptying the standard palette
« Reply #6 on: July 11, 2012, 11:08:27 pm »


               Turns out the solution was really simple and I'm just silly. '<img'>

-Exported the itempalstd.itp file with NWNExplorer to my Override folder
-Dropped it into TLKEdit
-Under MAIN ->
  • -> LIST -> [0-6] -> deleted the LISTs here
    -Standard item palette is completely clean for armour, and can be easily repeated for the rest

    Going to follow Pstemarie's method for having something show up in the standard palette and see if it's fine, tomorrow (because bed beckons)! Might have to restore the LIST classes and just empty them out, but I haven't had a chance to see yet.

               
               

               
            

Legacy_henesua

  • Hero Member
  • *****
  • Posts: 6519
  • Karma: +0/-0
Emptying the standard palette
« Reply #7 on: October 28, 2012, 01:13:59 am »


                Rubies,You were on the right track. I've been adding my file references to the standard palette while deleting the Bioware resources. This is the way to do it, rather than renaming your custom resources to override the Bioware resources.
However - any resources that you only want to show up in the standard palette should be:
  • Add the resref to an entry in the customized standard palette file. (itempalstd.itp)
  • Add the resource's name to your custom TLK file
  • Add the name as a STRREF to the same entry in the customized standard palette.
  • Extract the blueprint and edit in a GFF editor so that the Palette ID is 255 according to Pstemarie's discovery
  • Put the blueprint in a HAK
  • Associate the HAK with your module
Now that I am creating my crafting system, I realized I needed to rewroke items in Arnheim. Moving a ton of stuff to the standard palette.... Tedious but once done I'll be much more comfortable with a team of builders working on Arnheim.
               
               

               
            

Legacy_henesua

  • Hero Member
  • *****
  • Posts: 6519
  • Karma: +0/-0
Emptying the standard palette
« Reply #8 on: October 29, 2012, 01:15:36 am »


                I found a way to quicly populate the standard item palette with all the items in your custom palette:

Step 1: edit the custom palette to how you like it.
Step 2: open the temp0 folder in nwn/module while your module is open
Step 3: copy itempalcus.itp from temp0 to your desktop
Step 4: rename itempalcus.itp to itempalstd.itp
Step 5: import the new itempalstd.itp to a HAK associated with your module. (I do this when the module is closed)
Step 6: rebuild your module including the palettes.

I didn't think this would work. BUT it seems to. In truth what I actually did was copy the LIST nodes into the standard palette that I wanted, and was amazed that all the CEXO strings displayed properly in the standard palette. We didn't need to use STRREF and a TLK to identify all of the blueprint names. Saves a lot of time to do it this way (unbless you have an international group of builders on your module that don't all speak the same language... but thats unlikely)
               
               

               


                     Modifié par henesua, 29 octobre 2012 - 01:17 .
                     
                  


            

Legacy_OldTimeRadio

  • Hero Member
  • *****
  • Posts: 2307
  • Karma: +0/-0
Emptying the standard palette
« Reply #9 on: October 31, 2012, 11:54:04 pm »


               This is powerful stuff, Heneusa.  A huge "Thank you!" for posting those steps!
               
               

               
            

Legacy_henesua

  • Hero Member
  • *****
  • Posts: 6519
  • Karma: +0/-0
Emptying the standard palette
« Reply #10 on: November 01, 2012, 12:01:29 am »


               No problem. I am certainly taking advantage of this. Hopefully my mod will be more userfriendly for builders and dms to help me!