If you want to share custom liveries/teams for an online event, for example for an important league race, there are two ways to do this:

  1. Enable skin transfer on the dedicated server: this means all clients that have selected a custom livery will, after connecting to the server, automatically transfer that livery to the server where it will be redistributed to all other users joining that same server. That is not the topic of this guide.
  2. Create a new component that you distribute to your everybody involved beforehand. The easiest way to do this is via a workshop item that people can subscribe to. An alternative is to make it available for download from the dedicated server. You can even distribute and install it manually.
In this guide we will be focusing on method 2 for paid content that consists of a base component and and update component only!


Before getting started: What is an rfcmp?

For our purposes here, we don't need to get into the details of what an 'rfcmp' is, all that's needed is a basic set of steps to create one, and then how to install and distribute it after.

The advantages of creating an 'update rfcmp':

  1. Drivers don't have to show up early to an event just to make sure their skins get uploaded and distributed on the live server.
  2. More control: admins can check all liveries and related files are working and make sure no mistakes were made by each driver when they set up their custom team
  3. Less load on the server, no skins are transferred by the server itself, and therefore it requires no extra bandwidth. All clients have the full content before joining the event. 

This method does require a little extra work, but once you get the hang of it should be relatively easy to keep doing.

Important


Part 1: Setting up the VEH files

The VEH file contains all of the details for any specific team.
Each custom team will have it's own veh file that contains

Step 1: Creating a new, empty folder.

Example: 'Bentley League Updates'

Step 2: Collect all your livery files into that folder.

Step 3: Open MAS2.exe

Step 4: Extract files from the existing upgrade MAS.

Step 5: Edit the extracted files, creating a template for your new ones.

So now we have these files

Step 6: Configuring the livery and other information about your vehicles.

DefaultLivery="<team-name>.dds"
MaterialOverride="BentleyGT3_BaseMat.json"

Example:

DefaultLivery="Studio397.dds"
MaterialOverride="BentleyGT3_BaseMat.json"

IMPORTANT: Do NOT edit the line MaterialOverride!

Number=<my car number>
Team="<my team name>"
PitGroup="Group1"
Driver="<unique driver name>"
Description="Bentley Continental GT3 #<my car number>"
Engine="Bentley 4L V8"
Manufacturer="Bentley"
Classes="GT3, GT3_Bentley_Continental"

FullTeamName="Bentley"
TeamHeadquarters=""

Category="Bentley, Bentley Continental GT3"

Example:

Number=397
Team="Studio 397"
PitGroup="Group1"
Driver="Jefferson Bartholomew"
Description="Bentley Continental GT3 #397"
Engine="Bentley 4L V8"
Manufacturer="Bentley"
Classes="GT3, GT3_Bentley_Continental"

FullTeamName="Bentley"
TeamHeadquarters=""

Category="Bentley, Bentley Continental GT3"

Step 7: Repeat for each car!

Part 2: Packing the MAS file

Step 1: Populating the new MAS file.

Step 2: Creating the new MAS file.

Part 3: Packing the 'update rfcmp'

Step 1: Create a new update component.

Step 2:

Step 3:

Step 4: Select Component

Step 5: Component