LMS

We are happy to announce our latest project Lenny's Mod Loader - a unique way of installing and maintaining mods in Grand Theft Auto V. Stop worrying about where to place things, stress no longer over confusing files or folders and effortlessly enable or disable the loading of individual mods as you please. While still in early stages of development, Lenny's Mod Loader already provides many useful features to make modding more fun. Ultimately we hope to provide a fully-fledged Mod Manager UI allowing you to quickly install, remove, enable and disable modifications. Stay tuned for further updates and make sure to check out the full post.

This guide describes how to install a replacement vehicle that does not yet have an install.xml file Converting an replacement vehicle for usage with LML is very simple and often even less work than adding an addon vehicle. If you want to convert a replacement vehicle to an addon vehicle instead, check out our guide here. Concept When installing replacement vehicles, you usually either directly replace the files in an RPF or use the mods folder to replace them. Either way, you have to know the path of the vehicle you want to replace. The same does not apply to mods installed via LML in most cases. For vehicle mods that replace the model and/or the texture, you do not need to know the path, making installation very simple. More complex mods might require you to specify the game path to override, these examples can be found in our install.xml documentation. Folder Layout Create a new subfolder in your "lml" folder. We like to keep things clean, so we move all files (the model and the textures such ytd and yft) into a subfolder called "replace". This is it for the folder! Install.xml Now to make LML correctly load the files, we have to provide it with some information on our mod. Since this is a simple mod, not much needs to be specified. Create a new file called install.xml in the folder of your mod. You can find an example install.xml below that will make your replacement vehicle work out of the box. We recommend you change the name of the mod to identify it easily. If you vehicle has some special requirements such as data files, please visit the LML subforums and the install.xml documentation for more elaborate examples. <EasyInstall> <Name>Replacement Car</Name> <Author>You</Author> <Version>1.0.0</Version> <Link></Link> <Metadata> </Metadata> <Replacements> <Replacement name="New Police Car"> <FileReplacements>replace</FileReplacements> </Replacement> </Replacements> </EasyInstall> That's it! Your vehicle will now appear modded in the game.

Necessary Files Replacement vehicles usually lack the necessary files to function as addon vehicles. Sometimes they just include a new texture pack, sometimes they include a new model and textures but no data files. Depending on what you already have, different files need to be created. Scenario 1: Textures only This is the scenario where you need to do the most work. Since there is no model data to work with, but you need a model for an addon car, you first need to export the model yft from the game. So if you have say police2.ytd for a new texture pack, you need to locate and export police2.yft and export it. Usually the mod's readme has the location of where to put the texture. In the same location you will find the model file. Export it and put it in the same folder your texture is in. Now you have Scenario 2. Scenario 2: Model and texture file Equipped with a model and a texture file, all there is left is telling the game about the new vehicle. For this, it needs at least a new entry in the vehicles.meta file. At the end of the post you can find an example vehicles.meta entry where all you need to change is the name of the vehicle to match the name of the texture and model files. Since replacement files are supposed to replace existing files, you should rename the model and texture file to a new and unused name first, such as police6. Use this name in the vehicles.meta file then. Scenario 3: Model, texture and data files Some replacement models might offer a replacement handling or vehicles.meta entry. This makes it even easier for us. Simply copy the entry and move it to a new file only containing that one entry. Then adjust the name in the data file to the name of your model, such as police6. You now have all the files necessary to load a vehicle as an addon vehicle. Check out our guide here on how to proceed. Vehicles.meta Template

This guide describes how to install an addon vehicle that does not yet have an install.xml file Converting an addon vehicle for usage with LML is very simple in most cases. If it is a FiveM resource, chances are LML is able to create an install.xml file automatically. Try downloading the vehicle using LML and see if it works. Folder Layout Create a new subfolder in your "lml" folder. We like to keep things clean, so we move all streaming files (the model and the textures such ytd and yft) into a subfolder called "streaming". For data files, for instance vehicles.meta and handling.meta we do the same, placing them in a subfolder called "data". This is it for the folder! Install.xml Now to make LML correctly load the files, we have to provide it with some information on our mod. Since this is a simple mod, not much needs to be specified. Create a new file called install.xml in the folder of your mod. You can find an example install.xml below that will make your addon vehicle work out of the box. We recommend you change the name of the mod to identify it easily. If you vehicle has some special requirements such as audio gamedata, please visit the LML subforums for more elaborate examples. <?xml version="1.0" encoding="utf-8"?> <EasyInstall> <Name>My Car</Name> <Author>You</Author> <Version>1.0.0</Version> <Link></Link> <Metadata></Metadata> <Addons> <Addon name="My Car"> <StreamingFiles>stream</StreamingFiles> <DataFiles>data</DataFiles> </Addon> </Addons> </EasyInstall> You are now able to spawn the vehicle by using the RPH console in-game and typing "spawn" followed by the name of the vehicle (the name specified in the vehicles.meta and/or the name of the streaming files).

The mods.xml folder allows you to enable and disable mods as well as specifiy their load order. It will be auto-generated if not present and can be found in the lml folder. New mods will be automatically added and are enabled by default. The tag IsExtension in an install.xml file allows you to indicate that a given mod package is extending another mod. If set to true, the extension package will automatically be added as the last item in the mods.xml load order (the default is new mods are added at the top) so it can overwrite other mods loaded first. Load order / Overwriting mods The new load order feature specifies the order in which LML loads both, data and streaming files into the game. This is usually not important, unless you want to overwrite files from another mod. If you install a new car model NINEF in one folder and then download a separate texture pack for this model, you may not want to overwrite the texture file in the original NINEF folder. Instead, to keep things separated and clean you can have a separate folder with just the texture in it. By moving this mod down the load order list, its texture file will be loaded last, i.e. it will be the one the game uses. A few words of caution regarding overwriting. For streaming files the parser is usually smart enough to detect multiple files with the same name and will only ever send the last one according to the load order to the game. This just makes the process a bit quicker and prevents the game from reloading a resource multiple times. For data files this is obviously not possible, since they do not have unique names. Hence all data files are sent to the game and it is up to the game to respect the load order. Most data file parsers in the game reject new entries with the same name, which means that internally we send the overwritten data file first instead of last, to make sure it is used. All other entries with the same name are then rejected by the game. Alas, things are not always that simple and a few data file parsers, such as carvariations respect the last loaded file, so here we flip the load order again. This is nothing you need to worry about too much, but something to keep in mind when playing around with less common data files in case you run into issues. The log file also indicates the order in which the files are sent to aid debugging. If you find a file parser that requires overwritten files to be sent last, just tell me and I will make the necessary changes.