Can i use a vanilla save or a save from another mod setup?

No, this mod requires a fresh game start.

"vanilla" = unmodified original game

--

Is there a game menu setting, that i should avoid by all means?

Yes, do not play with "Enemy Scale" active in the game menu. It is off by default.

--

Can i play all W3 game modes?

No. The quick starts with HoS and BaW as well as New Game Plus (NG+) are not supported.

--

I would like to keep my current mod setup. Can i do that?

Yes, you can.
Rename your "mods" folder to for example "mods_disabled" or whatever differs from "mods".
Also check your DLC folder for DLC folder mod files, eventually store them away.
Then make a new "mods" folder, and use that for the LFT installation.
The game always reads from "mods" folder. So switching between different mod setups is possible, using respective game saves.

Usage of a blank "mods" folder is also the safest way to install LFT and corresponding mod files.

--

The page has quite a lot information.
Do you need to know all the descriptions before downloading and installing?

No. You can also download and install the mod along the instructions (txt files within LFT download).
And checking back later at the sources on this page, just when needed.
In other words: When you are used to install W3 mods, you can go straight for downloading the file. However you should look at least into the 'Other Mods' section of this LFT page, especially the "Complementary Mods" and also further below there.

Further basic infos

LFT installation requirement and process:

The mod installation must be done on a working vanilla game, version as mentioned above.
It is then simple copy and paste with easy-to-follow instructions.

A mods folder that contains already mods works as well, just when those are compatible. Logically, re-running Script Merger is duty then.

New to W3 mods? Note, a "mods" folder does not exist by default. No worries, that "mods" folder comes with the LFT mod files, also the "bin" and "DLC" folder.
Btw., the LFT installation does not change vanilla data. Breaking the original game is impossible.

--

Updates:

Changes are cumulative and save friendly with saves from the LFT started game (except when explicitely otherwise mentioned).

--

Support:

Only given when updated to the newest version.

--

Play modes:

No file support for New Game plus (NG+) and HoS or BaW quickstart.
Thus do not play NG+ or HoS and BaW quick game starts with LFT.

--

Changelog:

For version 1.0 until present version with Downloads (Documentation folder), because way too massive for the page.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Tools, Compatibility and Priority


1) Script Merger for merging script mods with each other and with script codes from LFT.
Do not script merge the xml files (Bundled Text) from LFT! You would break the LFT mod, if you do.
Simply ignore xml file "conflicts" in Bundled Text window of Script Merger, no exception. 

I apply the Script Merger v0.6.2, works well for me since installed ages ago.
Plus i highly recommend Script Merger updated to the Script Merger Unofficial Patch version. 

Advice:
- Apply the Script Merger after every mod update as part of a update routine, serves as general control.
- As one update routine part: In case the RedEngine parses the scripts and the gamestart reaches the game menu, exit the game!
And relaunch the game. Then load a LFT save and play. This is an important preventive measurement.


2) Go for the Mod Limit Fix. Alternatively apply Mod Limit Adjuster (i'm using this latter one, and recommend it).


In case somebody applies Mod Merger, do not mod merge the LFT modfiles, no exception.

And don't confuse script merge and mod merge.

Additionally, i recommend the following programs: 7zip for compressed files. And Notepad++ for example for .txt, .xml, .ws files and diverse other files, that can be opened/edited with a text editor. They are free but very capable.

--

Compatibility:

Not compatible with other gameplay overhaul mods and almost every mod with xml files.
Else, much compatibility is given. I'm using 200+ mods aside to the LFT mod files (see 'Other Mods' section).

--

Priority (load order):

When playing with diverse mods, load order is an important aspect.
For playing LFT it is very relevant to have the LFT main mod folder above all other mod folders. Highest priority is requirement.
Except "Compilation Trigger" (from Community Patch) and "Merged Files" (script merge result) with priority above LFT main mod folder.
The mod folder names provide that by default though, so it does not need any extra action. Further below is a link with according images.

But how to manually change load order (priority) of mod folders, simple and quick?
Few common examples:
Rename folder "modalpha" to "modzeta". Priority is much lower now, alphabetical.
Rename folder "modalpha" to "mod0alpha". Due to the 0 number, it will get an even higher priority.
Rename folder "modzeta" to "mod9zeta". Due to the 9 number, it will get an even lower priority.
Alphabetic and numeric mod folder name combinations for simple and quick prio settings.
For a better readability and still quicker folder name editing, i'm using this structure: "mod000_abc_xyz" (numeric, alphabetic order).
That's really not witcher-work ;)

In regard of LFT and other mods, there is basically nothing to do as user within this theme. Because mod names provide the needed load order.
Everything here stated is extra info, when somebody puts hands on mod names and manages load order manually.

For the case, a user changes mod names and such mod contains script (.ws) files, re-running Script Merger is required. All other mod files can get name changes at every time, just without re-running Script Merger.

--

Script Merger application:

When using other mods and LFT (or any other overhaul mod), with running Script Merger, a lot "conflicts" will be shown. Aside to "Bundled Text" window (xml files, see above), there is "Non-Bundled Text" which is listing all non xml files. First mod file in lines with same files takes priority, overwrites. Simple as that.
Decide the priority with mod name change, if needed. Ignore "conflicts" when it is not script (.ws) files.
Understand that the Script Merger tool is basically for merging script (.ws) files on the right side of the window. And secondly for getting an overview of the priority of other used mod files, left side of the window. You don't script merge any Bundled Text files nor Non Bundled Text files.

That said, advanced users or modders can manually script merge/merge diverse files. But this is merely no theme for the normal mod user with Script Merger tool and LFT. In other words, everything is good and works properly, when proceeding as described.

According images on Imgur.com:
Script Merger: Script Merger done
Mods folder: mods
DLC folder: files
(click on them to enlarge)

--

LFT "Addon" files:

There might be LFT "Addon" release files (possibly only temporary, optional or hotfixes). Those are exceptions from the above mentioned load order.
"Addon" means here literally "add it on" the LFT main mod folder. In other words: They shall have higher priority than the main LFT folder. But remain still below the CP "Compilation Trigger" and "Merged Files". The "Addon" mod names provide that also by default, so no fuzz.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Integrated Mods

Check the Credits section at the bottom of this page for integrated mods.

However, the download folder contains a list of integrated mods, too. Thus you can check that also when offline.

Primal Needs (PN), specific hints:

- Make yourself familiar with PN functions and its screen indicator (UI), rather called "HUD". It's basically explained on the PN page there.

- Important game menu settings for PN: Check Options, Video, then HUD Configuration. "HUD" must be active, as well as "HUD Tipps"! I think those settings are default vanilla, so this here is a preventive hint. Other settings there are not PN related, free choice.

- LFT is designed to play with PN features active. The PN mod menu but allows to disable single features or even all of them. However, PN delivers RPG contents for the game that should have been in vanilla. Thus playing the game without PN active is like "Easy Mode" or like "soup without salt"! Anyways, it is a core part of the LFT mod design. If you don't like PN, then better choose other mods.

Common hints:

- LFT has some mod menus from integrated mods. These are behind one extra 'Mods' button. So if a player has two such 'Mods' buttons in the game menu under Options, then the other one is from other installed mods.

- Short-keys and other things regarding integrated mods are explained in the LFT folder, "instructions" and "info" txt files.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Performance

As for massive code editing and code additions, as well as many added icons, the game start loading can take a tad more time.

In regard of in-game loading, i don't experience any LFT related issues. This mod contains no files that drain FPS, ie. no heavy textures. Also note, the 'Fast Stash Menu' mod is integrated already.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Strings

The LFT mod works with every game localization (W3 language version). Original game strings are not changed.
This has pro's and con's, as follows.
A big advantage is a general compatibility, it just doesn't need any such strings patches. Another one, a really huge workload is saved on my, or the modders, side. Thus the focus of the modding work has been playing, then actual gameplay modding, playtesting, adjusting and then releasing the results.
Disadvantage is, that many added items (when based on vanilla items) have the same item name. The latter normally doesn't matter, because those items apply other icons (exclusively new added ones), have different "quality" icons (grey/none, blue, orange, etc.) and different categories. So they are quite easy to identify on first glance in the inventory or elsewhere in the world. Likewise they are auto-sorted accordingly in the inventory and the stash.   

As follows mod parts from integrated mods with custom text translation, speak, exclusively added .w3strings files:

a) Primal Needs (PN) mod menu and some item terms & item descriptions. Translations provided: cz, de, en, fr, pl, ru.
Do not use other PN translation (strings) mods, they are incompatible with LFT (because PN is uniquely customised).

b) Meditation UI mod menu. Translations provided: cz, de, en, fr, pl, ru.

Non-translated strings from mod integrations use the english strings translation.
In other words, there aren't empty lines, regardless which W3 game localization is used. Just in case that happens though with your localization, easy customization is possible, as follows: Copy the according "en" strings file, and exchange that "en" part of the strings file name to your language abreviation for .w3strings files. So those at least have a name/description in English language in the game.

Feel free to provide the strings file translations to your language for according mod parts and send me the file (will be credited). Or make an own mod page for this purpose (no objections).

Sub Sections:
A. Complementary gameplay mods and basic fixes & improvements
B. Compatibility, categories and recommendations
C. Incompatibility, categories and exceptions

Regarding all here listed mods: An installation should happen after the LFT installation. That is at least the basic recommendation for an installation-order, just first the gameplay overhaul mod as "mothership", afterwards all other mods.
Edit: Since the Next-Gen version 4.0 is out, take care to choose the right mod version, when a mod offers a "Classic" and "Next-Gen" edition.


A. Complementary gameplay mods and basic fixes & improvements


Complementary gameplay mods

Following gameplay mods by Partoutatix are compatible and must-haves with LFT.
These mods are like LFT of gameplay-fixing character, and thus are complementary to LFT's modding aspects. They were applied parallel to the LFT development, thus part of the balancing, so don't miss them!
Install them along its own instructions (consider hint below). Then run Script Merger, auto-solved.
Three of these mods need easy to apply LFT patches (in LFT Patches folder *, with Readme.txt).

Alchemy, refill:
Simple Alchemy Refill  (SAR Herbs Version 1.2) *

Economy, prices deleveled:
Deleveled Gear Prices *
Cheaper Lore Friendlier Shop Prices
Cheaper Repair (I use v1.0, without mod menu)
Cheaper Runewright
Cheaper Corvo Bianco

Loot items:
No Junk Weapon Drops (I use v1.1)

No Duplicate Relics
Note, while there shouldn't be any relic sword/armor/horse loot item duplicates in LFT, that mod might help in regard of such relic shop items, when the game engine applies according quasi generic item spawns for shops. This mod is rather an optional recommendation.

Enemies, non-quest monster spawns:
Monsters Come Out At Night *

Hint: Do not use other mods from above mentioned aspects. It is indepth content of LFT. Thus can break the gameplay and cause bugs, if you do. This concerns also and especially other mods by Partoutatix like from his LEGO compilation.

Further highly recommended gameplay mods, by different other modders, as follows.

Roach gameplay:
Thoughtful Roach
Less Magic Roach

Holster utilities, accessoires:
Wearable Pocket Items
Accessory Slot Mod
E3 VGX Bearbag *
Hoods *
* optional LFT gameplay patches available (in LFT Optional folder).

Special weapon gear handling:
Swords on Roach
Crossbow and Torch on Roach (makes good sense for the crossbow).


Basic fixes & improvements

Huge collection of fixes, improvements and re-enabled contents:
Bug Fix Ultimate Collection
Called now "Brothers in Arms", short BiA, compatible with load order below LFT (lower priority than LFT).
BiA comes with different folders. The usage with LFT would be as follows:
- BiA main mod folder, calling "modBugFix__MasterCollection01": This is the most important and original BiA mod file. Drop it into the mods folder, ready. No merge nor do anything else with this file, except a custom load order with other mods!
- BiA xml folder: Do not use this file with LFT! LFT is pre-patched, according xml contents and item icons are part of LFT.
- BiA scripts folder: Recommendation, don't use this file with LFT!
- BiA DLC folder: Recommendation, don't use this file with LFT!
As short summary for LFT with BiA: Use the main file "modBugFix__MasterCollection01" and good (update that file with new BiA releases).
Edit: BiA got another file structure with v8.0. I didn't have opportunity to check compatibility. Recommendation: Keep the here suggested priority, and merge scripts only.

Fixes quest location icons, complementary to BiA's collection:
Novigrad Crest in Journal Restored

Quasi fix, restored content:
Witcher Lore Collection (WLC, compatible with load order below LFT)
Drop into the mods folder, ready. Do not merge the xml files, LFT is pre-patched with according necessary xml entries.

Very essential:
Fix Stuck Quest Items

Ground fixes:
No Stair Rolling (a classic)
No Fall Damage (just needed, also a classic)

Several essential mods:
Enable Mimics (Lip Movement and more, i would not recommend the shadows version)
Screen FX Removal
No More Glowing (NMG)
Unseen Monsters
Jump In Shallow Water
Vampires Have No Shadows

Sounds:
Quiet (compilation of certain sound mods, for me has big fixing character)

Camera base fix:
Remove Camera Shake and Bobbing
There are more such useful camera&animation "fix" mods (use the Nexus search function).

World situation (very essential, a duty mod for me):
Consequences Of War (proper Wild Hunt endings, application post Wild Hunt)

Diverse fixes:
Besserwisser's Patch (do not use a FCR3 patch file, FCR3 is integrated in LFT; put Besserwisser on a low priority; script merge the script files, not the xml, ignore "conflicts"). I personally use still v2.0 No Armors Edition; works properly without giving any headache.
Edit: See also above my "Edit" about BiA. As Besserwisser now included in BiA, that means logically it can be skipped to install (when BiA 8.0 or higher gets installed).

Various more newer fix/restored content mods:
Harbor Names Restored
Levelup Fix
Omelette Quest
Restored Content - Ciri's Fate (but not really compatible with the following rendering mod)

Realtime rendering:
Immersive Real-time Cutscenes

Other improvements:
World Map Fixes (as mod title says; no load order relevance)

LOD:
LOD Bug Fix Collection (as mod title says; put on very low priority)
Edit: There are newer and better LOD overhauls released now, fe. by Scoutbro. Recommendation: Check that out.

Adrenaline/signs, kind of fix:
Adrenaline Burst Fix

Torches gameplay (realism improvement, nice to have, when using torches):
Realistic Torches

Extra file "fix":
Merged Free DLC - Mod Limit Fix (very optional; i'm using it, despite applying Mod Limit Adjuster)



B. Compatibility, categories and recommendations

"Green lighted" mod categories and hints.

Below the categories: Some example mods that i use and recommend.

The example mods are perfectly compatible with LFT and all linked mods on the LFT page.


# Appearance mods, when pure texture/model replacers
All mods from this category should be compatible with LFT. Required, the replacer is actually a pure replacer mod (no xml or any other files, that contain stats).

LFT special info for this category (mod content by default):
The KM/Hunter armors are upgrade items: Start master->magic->relic using the Cos Wiecej models, then witcher->grandmaster using KM/Hunter vanilla models on its own (no relic pre-req), grandmaster with setbonuses; the "Witcher" swords are in this upgrade system.
Newly added a KM-Hunter line for witcher and grandmaster upgrades using Novigradian Armor Set models (pre-req the relic Cos Wiecej armor; physical upgrades). 
Warrior Jacket (WJ) is a standalone relic->witcher upgrade, the vanilla WJ (KM) model is replaced to avoid duplication with the KM armor.
HoS Viper set witcher->grandmaster upgrade with setbonuses. Specials for "Viper" swords upgrade system.
Wolf armor and sword set progression "fixed" (pre-req grandmaster). Specials for the early game (master, magic, relic; light chest armor).
Manticore has extended grandmaster upgrades. Specials for the early game (master, magic, relic, witcher; chest armor and pants).
There are more specials with witcher/school gear. And many non-witcher/school armors and swords got an upgrade system, some also specials.
For all armors the weights and classes (light, medium, heavy) are along model shape and form. All swords have proper weights incl. the scabbard and belts.

Aside to this info above, note: Two armor mods are integrated in LFT. This is Cos Wiecej and Novigradian Armor Set (see also Credits). Do not apply them with LFT!

Geralt, witcher school armors:
Witcher Armors Dirty and Worn Retexture (best complete witcher school armors texture mod)
Classic Manticore Armor (use with higher priority than aforementioned mod)

Geralt, body mods:
... not listed (i'm using diverse lore-friendly Geralt body replacer mods, which may vary at times)

Geralt, gear mods:
Book Inspired Medaillon
Leather Headbands (No Balancing Impact edition)
Fix Viper KM Armors
Dark Undvik
Temerian Retexture
Fix Nilfgaardian Set
Common Armor Retextures
Cidarian Armor with no Circles
Oathbreaker Armor Dark Theme
Darker Boots
Professional Witcher Belt
Ciri Lore Friendly Book Sword or Ciri Sword Redesign
... diverse more

Here a word about the pretty known Witcher 2 Gear mod (W2G) as relevant info: This in meantime quite old gear mod for non-school armors in the game was once in close connection with LFT as combined usage. This is no more the case! The W2G mod is basically compatible with LFT as replacer for non-school armors, but not the xml file that comes with the regular W2G mod (vanilla gear xml file). My advice: If you use W2G, don't merge the xml file from W2G with LFT's xml's, and in no way give it priority above LFT! Solution: There was once a W2G version by a user in comments there, that operates the W2G mod without the problematic W2G xml file, check that out. Also note, that W2G is not really bugfree in all its armor replacements (most are, but some are not).

Ciri:
Face Retexture, ... (i'm using over a dozen mods for Ciri)

Yen:
Yennefer Concept Hair, ... (and more)

Triss:
TW2 Triss, ... (and more)

I apply many more lore friendly eye, hair, etc. and gear texture/model replacers (main characters, PC, NPCs).

NPCs:
All NPC Scabbards (important: use only the DLC mod file of that mod and it's done; LFT files are pre-patched)
Simple NPC Swords
Unique Eyes for all Witchers
Improved Lady of the Lake
NPC Physics 60 FPS Fix

Monsters and trophies:
HDMR, ... (and more)



# Animation mods
All mods from this category should be compatible with LFT.

Combat animation (script only):

Pirouettes (rolling replacer, for me essential!)

Disable Cinematic Kill Cam (disables the finisher slow-motion, essential)

Better Combat Animation (same page as aforementioned, recommend the No Spins version)

Armor Class Fighting Styles (good armor related basis, modifies same file as aforementioned mod, but no issue to script merge them)

Or other such mods, and any combat stance or dodge mods. Those combat animation mods might have possible incompatibilities with each other. Except the here four above mentioned script mods, that are perfectly compatible.

Also note, w2anims files are very probably responsible for sliding NPCs, and those files are often used in combat animation mods. Script only animation mods don't have this issue.

Combat Speed Mod (CSM) is custom integrated in LFT; as well as few other animation related mods (check 'Credits' section). None of those mods have w2anims files. Sliding NPCs are absent from my game!

One can use enemy animation speed mods with LFT, like for example Speed Force. Personally, i do not apply them, they have an impact on the whole combat balance. Nonetheless, when looking for a still bigger combat challenge, then go for it.


Common animations:

Emote Hotkeys (non combat animations, during exploration, optional assignment via hotkeys; low relevance, just nice-to-have)
Some animations from Emote Hotkeys are content of Primal Needs (PN), thus part of LFT. I assigned a few certain animations which are not covered by PN.

The known 'Complete Animations' mod (CA) derives from the Primal Needs (PN) animations. CA therefore is not compatible with LFT by default, because PN is custom integrated in LFT since a very early LFT release. When a user thinks "I like PN, but can't live without CA", there is a way to merge both mods, namely the script codes along this page. I didn't and won't go that way, just mentioning here the possibility (and no guarantee that it works properly with LFT).



# Visual Effects and similar mods
All mods from this category should be compatible with LFT.

Exploration related:
Reasonable Senses ("Alternative" file only, red/grey, keeps the world from being that colorful, increases realism immersion)
Lamp on Boat (very useful, especially with dark night mods)
Smart Magic Lamp (very useful, especially with dark night mods)
Natural Torchlight (very useful, especially with dark night mods / mod menu settings)
No unsheathing on horseback (very senseful)
Active Medallion (useful and nice to have for some extra immersion)

Other effects:
Skellige Ice Breath (i use "Cold Places" preset/menu)

Camera:
Absolute Camera (multiple camera options, can also "fix" FOV; in my case one manual script merge, simply choosing C)

Potions, Signs (visual effect preference mods):
Dynamic Cat Potion
Axii Cooler Visual Effect
E3 Quen
Lightsource Yrden



# Sound and Music mods
All mods from this category should be compatible with LFT.

Silent UI
MOP Redux



# World Textures, FX, LOD, Weather, Environment, Lighting and Reshades
All mods from this category should be compatible with LFT.

World:
HDRP, and animals, grass, trees, clouds, lights, particles, boats, etc. mods (just along preference; use search function).

World specials:
Winter Is Coming (WiC Skellige edition, winter textures file only, awesome Skellige atmosphere; file needs priority above HDRP!)

Weather and Lighting:
Skellige Winter Weather System (SWWS, regular version, in connection with WiC Skellige winter texture file; needs priority above other weather mods)
Realistic Weather (best) *
Clear Lighting Toussaint (a lite lighting mod) *
Character Lighting Fix (balanced; lower priority)

* alternatively, i use(d) Immersive Lighting (IL); i'm still not certain what i find better. However, with according load order, they can be used together (IL lower than Real Weather, Real Weather lower than SWWS), while the weather steering .csv files of IL and Real Weather might be critical, although i never experienced an actual bug.
Also i'm testing the new Filterless Toussaint instead Clear Lighting Toussaint (will need a while until i'm there in my current playthrough). But pretty certain, Filterless Toussaint is the way to go for me. In order to combine this with IL properly, there is a IL no Toussaint mod; look in the comments of the IL page for the No Toussaint download link.
At last (on 24th December '21), i made myself a supporting combi mod for the latter (IL No Toussaint) and Real Weather, where IL has no weather steering .csv files. That seems to work very good for my purposes, ie. the following mods (priority): SWWS, Real Weather, Filterless Toussaint, IL no Toussaint no csv.

Extra:
Much recommended for the Skellige winter mods is Warmly Dressed Skelligers (Skellige NPCs carry winter cloths)

Day/Night cycle:
Darker Nights (can't live without the dark nights of that mod; lower priority than the lighting and weather mods)
For the smooth usage, apply the updated DN version by Aldarana linked in comments of the DN page.

Reshade:
Natural colors and sharpen (SweetFX reshade; de-saturation, proper contrast; E3 atmosphere; customisable)

Graphics, presets:
Magical Graphics Settings (as ready preset, i would recommend this)
Personally, i use a custom rendering.xml leaned on the above mentioned, certain ini settings and Nvidia driver settings.



# HUD, UI mods
Mods from this category should be compatible with LFT, when they are compatible with the 'Meditation UI' mod (integrated, see link in Credits).

Toggle Minimap (toggling off/on five Hud modules, for maximal exploration immersion, ie. selectively emptying screen)

No Herbs and Enemy Dots on Minimap (for better immersion)

I'm playing with an almost empty screen by default, for maximum immersion (disabled UI's via game menu). Active is the medaillon bar when it is called up (but can be set on/off with short-key), mini-map on/off with short-key and PN indicators on/off with short-key.

For further minimalist approaches, check mods by Strahlimeier.
Especially his Minimalist Loot Menu is a must-have for me in this regard.

Signs Descriptions for Long Journey Extended (highly recommended! because Long Journey Extended is integrated in LFT)

Script merge conflicts have been reported with big UI overhaul mods like 'E3 UI and HUD'.



# Corvo Bianco Villa related mods
All mods from this category should be compatible with LFT.

Requires, that such mods don't change gameplay balancing aspects that are defined in xml files or change same script codes.

Gear stands (swords, armors) from Corvo Bianco villa xml modding can be used with LFT, no changes there in LFT (file not used).



# Companion mods
All mods from this category should be compatible with LFT.

Requires, that such mods don't change gameplay balancing aspects that are defined in existing xml files or change same script codes.

Note, i personally never tried them yet, and i wouldn't recommend the usage prior to the very end of the game (main quests finished) with LFT. But it might be a good option for a post major quests phase as part of a free open world play in this game, when everything of the game's plot is done.



# Quest mods
All mods from this category should be compatible with LFT.

Requires, that such mods don't change gameplay balancing aspects that are defined in existing xml files or change same script codes.

Mods like Ciri's Sole Memento, as well as new map scenario quest mod projects like the ones by Damastor, for example TE, should be compatible. Very probably also A Night To Remember. Note, i personally never tried them yet, and i wouldn't recommend the usage prior to the very end of the game (main quests finished) with LFT. But it might be a good option for a post major quests phase as part of a free open world play in this game, when everything of the game's plot is done.



# Enemy Spawn mods
All mods from this category should be compatible with LFT.

Requires, that such mods don't change gameplay balancing aspects that are defined in existing xml files or change same script codes.

I think here of mods like Random Encounters Reworked. Note, i personally never tried them yet, and i wouldn't recommend the usage with LFT prior to the very end of the game (main quests finished). But it might be a good option for a post major quests phase as part of a free open world play in this game, when everything of the game's plot is done.



# Gwent mods
Gwent mods that solely replace any card illustrations are compatible by default.

For fresh game starts with LFT, the user is free to use a Gwent mod by choice or Gwent vanilla.
Or just using the optional LFT GI custom mod, which works 100 % issuefree with LFT (part of the LFT download, i recommend this one).

With other Gwent mods: The critical file would be the shops xml files, in case other Gwent mods have the shops files as well and deliver new or other Gwent cards.
Why? The LFT shops files are entirely changed versus vanilla and a core part of the LFT gameplay overhaul. Whatever you do in this regard, do not end up with altering xml values of LFT or you will break the LFT gameplay.

Very important: A Gwent gameplay mod user cannot change Gwent gameplay mods with existing saves. Doing so will lead to unsolvable Gwent bugs and saves from such a midgame Gwent gameplay mod installation-change are corrupted. So the decision, which Gwent gameplay mod shall be used for a playthrough should be taken before starting a fresh game. Using the mentioned LFT GI mod is like "apply and never look back" in this regard. However, Gwent mods that solely replace card illustrations can be applied/removed whenever liked.

Kind of summary, my Gwent mod recommendations, in this order uncritical with LFT:
- LFT GI (custom Gwent Improvements mod, in LFT 'Optional' folder contained; just made/used with LFT's balance, 100 % issuefree)
or
- Gwent Extended (description looks/sounds pretty good, no shops xml file issue, new on nexusmods.com since 16th January 2022)
or
- Gwent Improvements-Ultima (assuming this works almost like the LFT GI custom mod in regard of shops xml files)
and/or (if desired)
- any Gwent mod, that solely changes card illustrations



# Reported compatible gameplay mods

wollert: Reported about timescale mod, works technically issuefree with LFT.
My hint: Has a deep impact on the gameplay. While such a mod adds to realism, it is not recommended with LFT.
Because it eases the gameplay in many respects, contradicts the challenge in diverse aspects. Using such mod makes it an "Easy Mode" for the overall challenge and difficulty, and the whole mod design balance is manipulated, quasi neglected. In result, rather not usable with LFT, unless one decides to play such "Easy Mode" game.

koko775775 (LFT team member): He uses Natural Cat Vision with LFT.




C. Incompatibility, categories and exceptions

Here you will find info about incompatible mods.

Gameplay mod contents, that change something of the following aspects are incompatible with LFT:

# Geralt/Ciri, PCs and NPCs: Stats, skills, perks, abilities, encumberance, leveling, getting experience, rewards, damage and combat.
# Geralt/Ciri, PC and NPCs: Armors and weapons, including DLC gear sets, when not pure texture/model replacers (see above B.).
# Gameplay modes: Alchemy, edibles, crafting, meditation and travel/sign-posts.
# Economy: Price mechanics, item prices, trader behaviour and shop contents.
# Items: All loot lists of the game's world, including monster loot, shop items, quest items and all reward items.
# Items: Abilities, levels, qualities, slots, numbers, dismantling and weights.
# Items: Horse gear and trophies, when not pure DLC for entire new items.
# Items: Icons, when not pure DLC for entire new items.
# More categories: Check credits section for integrated mods to avoid overlaying of contents.

These things are defined in xml files besides grounded in script codes or related to them. All relevant xml gameplay files of the game are edited with LFT and a lot scripts as well! Many xml mechanics work together with script code in a complex way. LFT is mainly a xml and script based modification. My advice, don't use other xml mods with LFT, and gameplay script mods can be critical, too. Exceptions below.

Exceptions from this aforementioned "incompatibility" rule:

- Script mods, when they do not change the very same code, are technically compatible. A matter of script merge, and the question, if the script mod content and its mechanics are suitable. So in regard of script gameplay mods, a wise choice is due. My recommendation list above contains a lot script mods, so maybe pick from there.

- All pure DLC mods, when adding actual new stuff are technically complete compatible. Just a matter of balance. I would not recommend to use a DLC mod, that potentially has any bearing with balance (gear, items, abilities, skills and just all stats).

More hints regarding xml file mods:

- Other mods with xml, theoretically compatible, when 'Bundled Text' script merged properly. That means, you know exactly what you are doing. Not recommended at all with LFT though, as the probability that something gets messed up is pretty high.

- "Overwriting" LFT xml files with load order priority setting above LFT is a mistake with LFT, because it very probably will break the mod. LFT "Addon" is the only exception here.

In technical regard: If a mod has xml files and conflicts can be controlled with Script Merger. Best way to solve xml conflicts is priority (load order), and not merging xml, as that can lead to hidden bugs (xml is not scanned by RedEngine). Also csv files belong to this category. As normal mod user, you are probably on the safe side, when with Script Merger detected xml mod files are below LFT in priority (load order).