Blacklisting



Are you tired of seeing sims walking around with silly outfits and hats or wearing boots with their swimwear? Then you might want to consider blacklisting these items, so the game can select a CAS-part (hair, hair with accessory, make up, top, bottom, outfit, shoes, accessory) from the selection you do want a sim to wear. Of course, this doesn't help mismatching outfits but it can give you some relief from seeing sims with a bucket on their head as an everyday hair-CAS-part. This will also hide the CAS-part in your games CAS-engine.

This tutorial for blacklisting is written with Dresser in mind but all instructions can be applied to the MasterController InvalidParts tuning. Dresser tuning files can be found at Dresser Phase Five Tuning, MasterController tuning files at MasterController Phase Six Tuning.

Warning

anchor: [[Blacklisting#Maximum Amount]]

Due to the vast amount of CAS-parts (EA-packs, Store Content, Custom Content) within the game, players are unable to blacklist (hide) a large amount of these CAS-parts with an Invalid_Tuning mod or Valid_Tuning mod (CAS-parts you would like to use).
The maximum amount of lines you can insert in this mod is approximately 30,000 (you'll need a text editor to view the amount of lines used, preferably NotePad++). Going over this amount will prevent the mod from loading properly and it will be unable to hide any previously selected CAS-parts in the games CAS engine.


Easy CASP Editor


To divide the load within the game, you may also want to consider using this tool, Easy CASP Editor by Kuree which used to be hosted at Simlogical. It can hide most CAS-parts that came with EA packs and also Custom Content that you've installed as Sims3Packs. This tool has several options, which are:
  1. CAS-parts are shown as thumbnails and are organized by EA packs and Installed Custom Content (Sims3Packs).
  2. Re-categorize any CAS-part that a Sim may use in a certain category or multiple categories (everyday, formal, swimwear, sleepwear, athletic, career or outerwear).
  3. Which CAS-parts may be used on a Sim when they age up to their next Agegroup.
  4. Hide certain CAS-parts within the games CAS-engine.

Information on how to use this tool properly for blacklisting CAS-parts (3 & 4) is available here.

Note
  • If you wish to divide the load, start hiding items with the Easy CASP Editor first. These items are usually CAS-parts from EA-packs and Installed Custom Content (Sims3Packs). When you are done, you're now able to see the StoreContent (sims3packs) which you could not hide using the Easy CASP Editor. Use the InvalidParts method to block these items.
  • If you are using both methods of blacklisting through Easy CASP and InvalidParts (Dresser / MasterController), make sure that a CAS-part (instance) isn't used in both. If it is, those packages will conflict and cancel each other out, making all CAS-parts available again within the games CAS-engine.


Blacklisting Manual



The following guide requires some knowledge in text editing, namely, how to select (copy) a piece of text from one document and add (paste) it into another. If you feel uncomfortable with this procedure, I would advise that you follow another guide on this wiki which has been created specifically not to edit the blacklist document. It can be found here.

The negative side of this, is that it is easy to go over the maximum number of 30,000 lines. If you have under 800 CAS-parts, in MC>Settings>CAS>Blacklist, then you are safe to use this method. To be sure, open your blacklist export document in NotePad++ and see how many lines have been used, before importing it into the InvalidParts Tuning mod.


1. What do I NEED to create a Dresser (or MasterController) blacklist?
anchor: [[Blacklisting#What Do I Need]]

To edit the NRaas_Dresser_InvalidParts.package or NRaas_MasterController_InvalidParts.package you will need a Package Editor (S3PE) and a Text Editor (NotePad++) which you can set S3PE to use (Nraas Packer doesn't have this function).

Note: Notepad++ is not the same as windows-based Notepad, it will give you more options than its predecessor!

1.1. Download and install the following and set them up:

  1. S3PE (on installment, link the tool to all *.package files, when asked).
  2. NotePad++ (on installment, NOT required to link the tool to all *.txt files, when asked).
  3. Dresser_InvalidParts.package (place this on your desktop temporarily).

1.2. To enable NotePad++ within S3PE:

  1. Open S3PE.
  2. Select from the menu> Settings> External Program..
  3. Tick-in the check "Use an external text editor".
  4. Use browse to find the executable file NotePad++.exe on your system (i.e. on Win 8 its C:\Program Files (x86)\Notepad++\notepad++.exe).
  5. Click OK.
  6. Select from the menu> Settings> Save Settings.
  7. Exit S3PE.

1.3 Test NotePad++ availability in S3PE:

  • Double click on Dresser_InvalidParts.package it should open with S3PE.
    • If it doesn't open with S3PE you will need to set this up manually so S3PE is used to open *.package files as standard (if you haven't already when you installed this tool). Right click on any *.package file> open with... tick in the check box "Use this program as standard" and find S3PE in your install directory.
  • On the left side you'll see 2 lines (1 without a Name), click where it says Nraas.Dresser.InvalidParts so it's highlighted and on the right side you'll see the content.
  • Select from the menu> Resource> Text Editor.
  • This will import the content for that line from S3PE into NotePad++ and will make the content editable. You'll also be able to see directly how many lines are used (15). At this point it's too early to do anything with it, so just close NotePad++ and close S3PE. If any program ask to submit changes, click on "No".

Back To Top

2. Collecting CAS-parts to block.

anchor: [[Blacklisting#Collecting CAS-parts]]

The easiest way to collect the CAS-parts is by running your game in Window-mode and having your Sims 3 user-directory open in a Windows Explorer window so you are able to instantly switch from your game to Windows Explorer.

2.1 Find the item to block

First step is to find out WHAT to block.

  • Go into CAS, and RIGHT-CLICK the item you don't want a Sim to wear (Example 1.1). It will show the CAS details for the item and also create a ScriptError file in your Sims 3 user-directory (Example 1.2).


Example 1:

1 CAS R-Click on Part (2).jpg

2.2: Find the INSTANCE, GROUP and CATEGORIES.

Now that you have a scripterror file for that Sim or CAS-part, you can open this in Notepad (or Notepad++), see example 1.2.
Copy these lines into a SEPARATE Notepad document.

  • Example 2:
    • Instance: 0xA52EE3BCC14AF29E
    • Group: 0x00000000
    • Categories: Everyday,Career

Note: Under categories you'll see in which CAS-category the CAS-part is available, if you just want to block one category of that instance, delete the other categories from the list. In section 6 we will expand on this in more detail.

2.3: Converting into readable code

Instance, group and categories are known as XML nodes. For the game to be able to read the codes after these XML nodes, it requires to be wrapped with these XML Nodes.

From 2.2 we will continue with example 2. Wrapping the code with XML Nodes looks like this:
  • Example 3.
    • Instance 0xA52EE3BCC14AF29E Instance
    • Group 0x00000000 Group
    • Categories Everyday,Career Categories

The game can't read such notation and will require some operators over the XML Nodes to make it readable by the game. For conveniences purposes it looks like this:
  • < ...> = start reading code
  • </...>= code ends here

  • Note with "..." the XML nodes as mentioned in above Example 3.

To make these XML nodes readable by the game it, should look like this:
  • Example 4.
    • <Instance>0xA52EE3BCC14AF29E</Instance>
    • <Group>0x00000000</Group>
    • <Categories>Everyday,Career</Categories>

  • Note: No spaces between the XML nodes and the code.

2.4: Adding References!


With just some codes to go by there is no way to identify what you're trying to block. You can add above the readable code some references to what they are by placing these commands on top of it.

  • To make sure this reference will not interfere with the game you will need to add these operators in between the reference "...":
    • <!-- ... -->

Basing it on 2.3, example 4:
  • Example 5:
    • <!-- long hair covers eyes -->
    • <Instance>0xA52EE3BCC14AF29E</Instance>
    • <Group>0x00000000</Group>
    • <Categories>Everyday,Career</Categories>

  • Note: Useful if you ever want to unblock it, but isn't highly necessary to add and this subsection can be skipped.

2.5: Finalizing the readable code.

To be able to let the game know what to do with these XML Nodes, it will need a Parser. "Parsers" are added as a wrapped container above and under the XML nodes that are used to block a CAS-part. In this case the Parser command is "InvalidParts" (without the quotes).

To make it readable for the game, the same operators as in 2.3. are needed. Further altering of example 5 within subsection 2.4, will have this as a result
  • Example 6:
    • <InvalidParts>
    • <!-- long hair covers eyes -->
    • <Instance>0xA52EE3BCC14AF29E</Instance>
    • <Group>0x00000000</Group>
    • <Categories>All</Categories>
    • </InvalidParts>

  • Thus ends here this section on collecting a CAS-part.

Back To Top

3. Editing the Nraas_Dresser_InvalidParts.package

anchor: [[Blacklisting#Editing in S3PE]]

In 1.3 we showed you how to open a package and make a line editable in NotePad++. Lets start repeating this process and do some updating on a package. The reason we say updating is that the actual editing is done in a _XML tag (left line in S3PE) with the help of a text editor, in this case NotePad++.

3.1: A Repetitive Action of 1.3:

  • 1) Double click on Dresser_InvalidParts.package - it should open with S3PE.
  • 2) Click where it says Nraas.Dresser.InvalidParts with tag _XML so it's highlighted and on the right side you'll see the content.
  • 3) Select from the menu> Resource> Text Editor.


Once opened, you'll see in NotePad++:
  1. <?xml version="1.0" encoding="utf-8"?>
  2. <base>
  3. <InvalidParts>
  4. <!-- This is the default set, do not alter or remove it -->
  5. <BodyType></BodyType>
  6. <Instance></Instance>
  7. <Group></Group>
  8. <Age>AgeMask</Age>
  9. <Gender>GenderMask</Gender>
  10. <Species>SpeciesMask</Species>
  11. <Categories>All</Categories>
  12. <Extended></Extended>
  13. <WorldTypes></WorldTypes>
  14. </InvalidParts>
  15. </base>



This is the default template of the InvalidParts Tuning mod which is required to run the mod properly. DO NOT DELETE!!

3.2: Editing in NotePad++:

Go to your document where you've collected the CAS-parts as in subsection 2.5 example 6 and copy (CTRL+C) the entire content. Go back to NotePad++ and set your cursor on line 15 in front of </base> and paste (CTRL+V) your items in NotePad++. The end result should look like this:

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <base>
  3. <InvalidParts>
  4. <!-- This is the default set, do not alter or remove it -->
  5. <BodyType></BodyType>
  6. <Instance></Instance>
  7. <Group></Group>
  8. <Age>AgeMask</Age>
  9. <Gender>GenderMask</Gender>
  10. <Species>SpeciesMask</Species>
  11. <Categories>All</Categories>
  12. <Extended></Extended>
  13. <WorldTypes></WorldTypes>
  14. </InvalidParts>
  15. <InvalidParts>
  16. <!-- long hair covers eyes -->
  17. <Instance>0xA52EE3BCC14AF29E</Instance>
  18. <Group>0x00000000</Group>
  19. <Categories>All</Categories>
  20. </InvalidParts>
  21. </base>

Always make sure </base> is on the end of these commands.

When done, save NotePad++ and Exit. S3PE will then inform you that the "Resource has been updated. Commit Changes?", press "YES". S3PE will make a new updated line of Nraas.Dresser.InvalidParts with tag _XML and strike through the old one. Save S3PE, you'll see that the strike through line will be erased and then exit S3PE.

Back To Top

4. Enabling the Nraas_Dresser_InvalidParts.package in your game.

anchor: [[Blacklisting#Enabling Blacklist]]

Once you've saved your Nraas_Dresser_InvalidParts.package (as explained at the end of section 3 above), move this file from your Desktop to your Sims 3 userdirectory "Mods\Packages" folder, clear your caches and start the game.

After you've loaded your game, click on the CityHall or a Computer then: NRaas> Dresser> Check Outfits> "Run Invalid and Accessories Check Now" and/or "Run Invalid and Accessories Check Service Now". This will remove all items you've listed from the all Residents and/or Service Sims.

Note:
If you've made a Nraas_MasterController_InvalidParts.package, you'll need to enable Dresser to use this package by clicking on CityHall/Computer> Nraas> Dresser> Check Outfit> Use MasterController Blacklist> set to True.

Back To Top

5. Updating the Nraas_Dresser_InvalidParts.package.

anchor: [[Blacklisting#Updating Blacklist]]

Whenever you find some CAS-parts that you do not wish to be used by any Sim. Start again with 2. Collecting Items and when your list is complete:
  • Open NRaas_Dresser_InvalidParts.package with S3PE located in your Sims 3 user directory within "Mods\Packages" folder.
  • Select the line Nraas.Dresser.InvalidParts with TAG "_XML".
  • Once highlighted, select from the menu> Resource> Text Editor.
  • Set your cursor on the last line of command in front of </base>.
  • Copy (CTRL+C) and paste (CTRL+V) the new items you want to block.
  • Always make sure the file ends with </base> on the end.

Back To Top


6. Additonal Blacklist Options.


This section requires a little more knowledge with text editing and requires you learned the basic that been handled in previous section 2, 3, and 4.


6.1: Having multiple CAS-parts to block:


If you have multiple CAS-parts to block, handle both cases separately as instructed within 2.2 through 2.5.

For example:
1. CAS-Part, hair
2. CAS-Part, accessory small earings
<InvalidParts>
<!-- long hair covers eyes -->
<Instance>0xA52EE3BCC14AF29E</Instance>
<Group>0x00000000</Group>
<Categories>Everyday,Career</Categories>
</InvalidParts>
<InvalidParts>
<!-- small ugly earrings -->
<Instance>0xDF870AAA1C92BBCC</Instance>
<Group>0x00000000</Group>
<Categories>Everyday,Formalwear,Sleepwear,Swimwear,Athletic,Outerwear</Categories>
</InvalidParts>

Once done, combine both separate logs into one.

This is how it looks when its merged:
  1. <InvalidParts>
  2. <!-- long hair covers eyes -->
  3. <Instance>0xA52EE3BCC14AF29E</Instance>
  4. <Group>0x00000000</Group>
  5. <Categories>All</Categories>
  6. </InvalidParts>
  7. <InvalidParts>
  8. <!-- small ugly earrings -->
  9. <Instance>0xDF870AAA1C92BBCC</Instance>
  10. <Group>0x00000000</Group>
  11. <Categories>All</Categories>
  12. </InvalidParts>

Proceed with section 3. to add this log within your InvalidParts tuning mod.

6.2: Shorten up the Categories:


If you are sure that you don't want the CAS-part at all and within categories there are multiple items chosen, replace all individual categories with one word "ALL". This is how it should look like, examples taken from 6.1:
1. CAS-Part, hair
2. CAS-Part, accessory small earings
<InvalidParts>
<!-- long hair covers eyes -->
<Instance>0xA52EE3BCC14AF29E</Instance>
<Group>0x00000000</Group>
<Categories>All</Categories>
</InvalidParts>
<InvalidParts>
<!-- small ugly earrings -->
<Instance>0xDF870AAA1C92BBCC</Instance>
<Group>0x00000000</Group>
<Categories>All</Categories>
</InvalidParts>


6.3: I do want to use these items for certain categories:


If it's only for a certain category you wish to block these CAS-parts, remove the categories you want the CAS-part for. Say, you only want them blocked for Sleepwear and Career usage. Then those examples should look like this, examples taken from 6.1:
1. CAS-Part, hair
2. CAS-Part, accessory small earings
<InvalidParts>
<!-- long hair covers eyes -->
<Instance>0xA52EE3BCC14AF29E</Instance>
<Group>0x00000000</Group>
<Categories>Career</Categories>
</InvalidParts>
<InvalidParts>
<!-- small ugly earrings -->
<Instance>0xDF870AAA1C92BBCC</Instance>
<Group>0x00000000</Group>
<Categories>Sleepwear</Categories>
</InvalidParts>

6.4: Adding more, Age-groups:


If you just want to block a CAS-part for a certain Age-Group that is allowed for multiple Ages, you can add "<Age>whatever age</Age>" to block. This will mean that the CAS-part will be available for those Ages not mentioned here. This is how it should look, based on Example 1 (want only Adult blocked) and Example 2 (want to block YoungAdult, Adult and Elder), examples taken from 6.1:

1. CAS-Part, hair
2. CAS-Part, accessory small earings
<InvalidParts>
<!-- long hair covers eyes -->
<Instance>0xA52EE3BCC14AF29E</Instance>
<Age>Adult</Age>
<Group>0x00000000</Group>
<Categories>Everyday,Career</Categories>
</InvalidParts>
<InvalidParts>
<!-- small ugly earrings -->
<Instance>0xDF870AAA1C92BBCC</Instance>
<Age>YoungAdult, Adult, Elder</Age>
<Group>0x00000000</Group>
<Categories>Everyday,Formalwear,Sleepwear,Swimwear,Athletic,Outerwear</Categories>
</InvalidParts>
  • Example 1.
    • What this says is that the item is blocked for Adults in the category Career, but can be picked by any YoungAdults.

  • Example 2.
    • What this says is that the item is blocked for YoungAdults, Adults and Elders in the category Sleepwear, but can be picked by any Teens in category Sleepwear.


6.5: Just want Males to be able to wear a CAS-part:


Some CAS-parts are coded to be used by both genders (unisex), which sometimes doesn't look well on one of the genders. This one isn't included in these examples but imagine Example 2 has UNISEX gender allowed, to block either of these genders you'll need to add <Gender>Male / Female / GenderMask (for both)</Gender>. Within them, say those earrings don't look good on females, so let's block the gender Female:
Example 2.
<InvalidParts>
<!-- small ugly earrings -->
<Instance>0xDF870AAA1C92BBCC</Instance>
<Age>YoungAdult, Adult, Elder</Age>
<Gender>Female</Gender>
<Group>0x00000000</Group>
<Categories>Sleepwear</Categories>
</InvalidParts>

What this says is that the item is blocked for Female within the ages YoungAdults, Adults and Elders in the category Sleepwear, but can be picked by any Teens in category Sleepwear and Males in any categories.

Note:
Using more and more XML nodes will increase the lines usage, which is the reason why we started off with compact mode, which guarantees the usage of as few lines as possible within this mod.