In base\appearance_mappings.json, entity types have their resources defined. The vehicle definition is below:

These are the part names used in filenames for .mesh and .ent files. Each header is their category - base is used in both Interior & Exterior.

Interior

• base

• steering_wheel

• pedals

Exterior

• base

• bumper_f

• bumper_b

• hood

• trunk

• door_fl

• door_fr

• door_bl

• door_br

• fuelcap

• fuelport

Wheel

• wheel

This section contains an overview of things that you might encounter while modding vehicles. For a full list of sub-pages, please check the link tree in the left-hand menu.

Appearances

For the documentation on .app files (appearance definitions), see here or check the appearance mappings subpage.

Entity Files

For the documentation on .ent files, see here.

An example entry for a vehicle entEntityTemplate from a vehicle's .ent file looks like this:

Referenced from base\appearances_mappings.json, base\vehicles\vehicle_filename_parsing.json contains a regex string is defined that outlines the allowable file names for .ent files (play around with this regex here):

(?:v_)?([a-zA-Z]+|av)\d?_([a-zA-Z]+)_(?:[a-zA-Z]+(?:_[a-zA-Z]+)*)__(?:int|ext)\d{2}_([a-zA-Z]+(?:_[a-zA-Z]+)*)_\d{2}.*\.ent

For a filename like v_sport2_mizutani_shion__ext01_body_01.ent, this would match the following groups:

• Group 1: sport

• Group 2: mizutani

• Group 3: body

Group 3 has no mapping, is of the type partType.

Curiously, this regex doesn't work for vehicles such as the Type 66, or the 911, since numbers aren't permitted in Group 2. It's unknown if this is even used, or if there is replacing done at some point.