WilliamImm

OT: Through I much prefer things based off of Ruby code, whch I feel are even more clean and easier than Python stuff. Ruby's pretty damn easy to base a DSL on - like a installation wizard. Through, then again, I'm biased because I am very much in love with Ruby in general and how it feels to write.

The bit of code you singled out is actually autoselection code ripped from my EBQO FOMOD installer. In that, if Requiem was installed, the patch for it would be automatically selected, no frills. In this case, actually, it may be a little redudant. The intention is to select the Requiem option if Requiem is installed, and select the non-Requiem option if it isn't - I've used a similiar statagey for my Disease Descriptions FOMOD installer when regarding RN&D, and in there, it does work fine (at least with the external/NCC installer).

Here's my updated version. Now with more BAIN friendliness and less duplicated code in the installer! In fact, z92 would have a much easier job on his hands considering that nearly all of the directory names are the same as they were in the BAIN installer originally (didn't have to rename much, too)

Actually, I learned ConditionalFileInstalls exactly from that guide, and you are actually using it in a limited fashion in the current FOMOD. It's one of the most powerful tools at your disposal for FOMOD writing, and it's a complete shame not many people use it to the full potential.

Hmm... I can see many improvements can be made, notably by making the structure BAIN friendly, and also using the ConditionalFileInstalls feature of NMM installers to reduce duplicate code. I'll come up with something with those changes pretty soon.

The Unofficial DLC patches notably use the approach z92 and I have been describing by packaging the translations into the BSA. Book Covers Skyrim also does the same thing regarding localizations. And we should be doing the same as those two mods.

Alternatively, there's Option 3: Same as Option 1, but all language options are installed, and there's no need to select the language. Nearly all mods that use the string translation feature install all the available translations by default, and I feel SGD should too. Techangel, you seem to be making the clutter "issue" more of a deal than it actually is. It isn't really an issue at all, as I've never seen someone complain about the so-called "clutter". If it bothers you that much, it's less effort to pack the string files into BSAs than to make the installer more complicated.

Yes, that's a very likely scenario: Mod makers will likely switch between English and their native language, using English to make mods and their native language to actually play the game, and possibly do translations for their language. And if a STRING file is missing for the respective language, the game will crash on startup. Basically, install all the relevant STRING files for Soul Gems Differ. If you are too concerned about it cluttering up the Strings directory, pack the String files into a BSA.

Really, just install all the relevant String files. If clutter bothers you that much, pack them into a BSA, and you don't have to selectivly install the ones for the language. Installing all is much, much better than installing selectivly. This avoids the game from crashing if, say, you decide to switch languages mid-playthrough. Yes, that scenario is unlikely, but not improbable.

It's easier to just install all the string files. Whatever language the game itself is using, the Soul Gems Differ ESP will use.

...It wasn't one of the ones Arthmoor recomended for doing translations. Along with TES5Edit, he recommended either StrEdit or TESVTranslator instead for localized string editing. StrEdit is more minimalistic than TESVTranslator, but I'd recommend you try both and see which one works best for you.

@SRB - you change the localization using TES5edit, and copy the text from the different language plugins of SGD into Notepad++ or similiar temporally until you set the localization approiatly and add the text back. @z92 To delocalize a plugin, right click on the plugin and select Other->Localization->Delocalize. Localize Plugin sets up a plugin to use the STRING translation system. When a plugin is localized, you do not need to change the name of it, just save it and the new localization strings. To actually rename a plugin, Wrye Bash is recommended to do so.

Discussion thread: Enchanting Candle Meshes Improved by LeanWolf Wiki Link Recommended on the Static Mesh Improvement Mod page, and made by the same author as the recently accepted Better Shaped Weapons. A mesh replacer for the enchanting table that dramatically improves the look of the candles on top. It works with existing enchanting table retextures, including the Jecelredued one and the one STEP currently uses. Must be installed after Ruins Clutter Improved. I think this is a nice improvement akin to SMIM for the enchanting table, no? Accepted for STEP 2.2.9 Core.

Uh, didn't realize that. In that case, you need to copy the text from the foreign language plugin before you switch the localization. In my earlier step-by-step guide, switch steps 5 and 6, effectively.

Not all the plugins should be localized, just copy the localized text. To do so, right click the relevant text, select Edit, and copy the resulting text over to a temporary text document. All the relevant strings for the text will appear in /Data/Strings, or in /Strings. They will remain there no matter what language you set for TES5Edit's localization.

Except it is. I see Other->Localization->Language->Japanese in my version of TES5Edit (3.0.31). And for the translations, load the relevant localized SGD plugin as well, copy any modified text over to a text file, then in the main, String localized file, just paste the relevant string where it goes.However, there is indeeed no Japanese localized STRING file installed with my game. I supect it's only there when you select the Japanese version of the game. Try changing the language of the game temporally to Japanese and look for the Japanese STRING files for the vanilla game. Once that's done, you can switch the game back to English.And, as for object bounds for the filled soul gems, I'd just keep the SGD bounds, not sure why Requiem changes them in the first place.

Nope. However, it's fairly simple to do localization using only TES5Edit: 1. Open the plugin you want to localize. 2. Right click on the plugin's entry, then select Other->Localization->Localize Plugin 3. When it prompts you to, save the plugin. 4. Open up the plugin again in TES5Edit - it should still come up with the text it had before (if the localization conversion worked) 5. Right click anywhere in TES5Edit, then select Other->Localization->Language->the language you want to translate to. 6. Add the relevant translations (source the relevant SGD language plugins for reference) 7. After adding the relevant translations, save and make sure all files (including strings) are ticked. 8. Repeat 4-7 for each language. 9. Repeat for each plugin.

You do not need to use the Merge Plugins script, but I would recommend that after each language change and translation that you save the modified ESP afterwards.

Agh, must have been somewhat asleep. Hard Times does change the soul gem records directly, but only to add a drop sound and add a "linked to" record for each gem (which SGD already does). Everything else is the same as Requiem. So, basically, just make the Requiem compatible version.I actually did correctly state which plugin does the vendor changes (Requiem itself), but I guess that's been lost in the shuffle.

Yes, it should be a standalone plugin that doesn't depend on any other SGD ESPs, but on Requiem. As I've pointed out before, the Hard Times unofficial extension needs its own patch because it makes more changes to the soul gem records than Requiem does, so do not neglect that.

Read this guide. It's for FNVEdit, but nearly all of the editing instructions apply to TES5Edit equally well. By this point, you should be able to understand my instructions.And for completeness, for the Requiem version, even in records that Requiem doesn't modify, copy those to the SGD Requiem ESP because I'd imagine only that ESP wil be used in-game.

3. Create an override using the Requiem record as a base - save to "Soul Gems Differ - Requiem.esp"4. Merge the few changes from Soul Gems Differ into the new ESP. 5. Save, and repeat from the top, but use Hard Times, and save the file as "Soul Gems Differ - Requiem Hard Times.esp" 6. After that, repeat for the different ESP varieties.

As for the Requiem patch, just drag and drop the relevant changes over from Requiem to the respective Soul Gems Differ ESP. For the keywords, make sure you drag and drop the catagory (right above where the first keyword will be), since Requiem intentionally removes the VendorSoulGem keyword from Black Soul Gems in order to add it's own special vendor keyword to it. And as for localization, TES5Edit also covers that. In the right click menu, go to Other/Localization/Localize Plugin firstly. Then you can merge the text for each language while in TES5Edit (just use Other/Localization/Language to switch languages).

If there was a guide, it would only have 1 step: Merge everything with TES5Edit. One pitfall of note is that the black soul gems have a different vendor keyword attached to them - just use the one from Requiem in the Requiem Compat versions. Additionally, there needs to be additional versions that support the Hard Times Requiem extension, since that also makes some quite swooping changes to the soul gem records.

I'd imagine the multiple ESPs can be cut down by using STRING translation files, like a few other mods use for localization. EDIT: One more thing: High time to make Requiem compatible versions of Soul Gems Differ. It's really no different than making compatibility patches for other mods, just use TES5Edit to do it. PM the author of Requiem afterwards just so that he knows that the two mods are now compatible with each other.