are there any conflicts with other already installed package files??

do i need to delete them all? now that i can chage everithing with this tool.

A possible conflict depends on what plugins do you add to the mod project.
The export function generates packages only with xmls concerning the plugins you selected.

In a future upgrade, I will add a conflict checker.



Actually, the program source-code is very simple and small using Postal-API. I spent no more than a couple of nights programming and generating plugins. :p

This is.... amazing! o_o I'm assuming it's a core modder, because I know little to nothing about modding, so I should... not download it with awesomemod? XD Or is this something for modders to use, to make pretty mods for us un-modders?

The thing I"m confused about... I mean I understand how it works, but can we also use it to adjust custom stuff that we've downloaded?

Maybe I just skipped past it, i dunno, but is there a plugin that alters the probability of finding certain metals, gems, insects, or maybe somethin that modifies how many would be in a certain spawn point? thanks in advance

This looks like the best tool ever... quite unfortunate that us Mac users are left out...

It seems to work on Mac too, just run SimCustomizer.jar instead of SimCustomizer.exe

No. The program starts with all standard game values, but you can use your mods with other custom content (as long as they don't conflict). Conflict detection will be implemented in next version.


No. You can save several mod projects. Just have to be careful to not install mods from different projects that use same plugins.


Yep. As it was written in Java, it should work on Mac, Linux, Solaris, etc... Just run the jar file (The exe is just a wrapper to verify if Java is instaled)

This tool is designed to perform "XML Tuning" modifications. It is working with the Electronic Arts\The Sims 3\Game\Bin\GamePlay\GameplayData.package file, which is where all the relatively safe tuning parameters for the game live.

With that preamble:

• The mods you make with this tool are *not* core mods, so they won't conflict with core mods such as AwesomeMod
• The mods you make with this tool *might indeed* conflict with other mods that have been posted here on ModTheSims! It all depends on which specific resource you have modded.

The upside to this program (its ease of use) is also its downside. It hides the actual resource ID, showing you only the resource *name*. The resource IDs look like this: 0xdfd048952e802db0.

If you inspect various mods using a tool like S3PE, you'll see that they contain only the resource IDs. It's easy to figure out whether a given mod you just downloaded will conflict with any of the mods you already use by opening them all in S3PE and noting the resource IDs for each resource in the mod. If any two mods you want to use have the same resource ID in them, you will have a conflict between them. In this case you either have to pick which one you prefer or figure out what each mod does in the conflicting resource, and then make your own mod that incorporates the things that both of the mods do to that resource.

Another potential downside is that this app might be displaying the various "deprecated tunings" in each resource but not highlighting them in any way. So you might think you're changing a current tuning when in fact you're changing a deprecated tuning. (Maybe the app author is just outright hiding the deprecated tuning values, but I can't tell from the supplied screenshot.) If you rely on a change to a deprecated tuning, one of two things will happen: A) nothing at all, or B) in some future patch your mod will stop working correctly because the underlying logic that uses the deprecated value was finally changed/removed. BTW "deprecated" in the programming sense means "do not use this value any more--it might work for now but we're planning on removing it eventually".

-------

A tool that would be incredibly useful to the *user* community would be one that can trawl every subdirectory in your Mods\Packages folder, open each .package file and write the resource IDs used in each package file to a text file output (or screen output/report/etc). Even better if the program can automatically highlight any conflicting resources that it finds in all the mod files that it opens and tell you exactly with .package files have the conflicting resources.

Such a tool would make it very easy for all users to tell whether that shiny new mod they'd like to download and install will bork their game or not. Right now, only the folks who are actually comfortable using S3PE (namely, the modders) can suss out potential mod conflicts.