This mod supports players to have extended features available on vehicles MADE to have these features.

e.g.:
Vehicle A is made to use YLVF, enabling YLVF would allow player to experience extended features on this vehicle.
Vehicle B is a vanilla vehicle which is not made to use YLVF, enabling YLVF have no effect on it.
该模组支持玩家在被制作成使用YLVF的载具上拥有YLVF支持的拓展功能。

例：
载具A被制作成使用YLVF，启用YLVF允许玩家体验该车上拥有的拓展功能。
载具B是原版载具且很明显其不使用YLVF，启用YLVF对该载具无影响。

Currently, YLVF does not support players to convert vehicles to use any YLVF extended features.
*: Converting might be investigated after YLVF 1.0.0 version.

e.g.:
Vehicle C is a vehicle made to use a custom script but not YLVF, player cannot convert this vehicle to use YLVF.
目前，YLVF不支持玩家转化已有载具去使用YLVF的拓展功能。
*：转化功能可能在 YLVF1.0.0 版本以后进行研究

例：
载具C被制作成使用一个其它脚本而不是YLVF，玩家不能转化该载具使其使用YLVF

If on main menu, go to 'Mod manager', find YLVF mod, click on it and you should see a button says 'Options', click this button would take you to mod options.
If in-game, pause game, at bottom of screen find a button says 'YLVF settings', click this button would take you to mod options.
如果在主菜单，打开‘Mod manager’界面，找到YLVF模组，点击模组会显示一个写着‘Options’的按钮，点击这个按钮会进入模组选项。
如果在游戏中，暂停游戏，在平面底端寻找一个写有‘YLVF Settings’的按钮，点击该按钮会进入模组选项。

• Vehicles using YLVF customizable spawning DOES NOT work with vanilla spawn panel (more info: FAQ #6)
  
• Default key to bring up YLVF spawning panel is 'F9' (check mod options if you changed that)
  
• After this, a panel with a list would appear at left. It would list all available packs using YLVF spawning, subscribe vehicle packs using YLVF spawning to get more.
  
• If you have at least one pack, select the one you want.
  
• A secondary panel would display automatically, click around to see what you can spawn.

• 使用YLVF自定义生成的载具不与原版生成菜单兼容（详细信息见 FAQ #6）
  
• 默认唤起YLVF生成面板的快捷键是‘F9’（如果你修改过键位请检查模组选项）
  
• 随后，一个带有列表的面板会出现在左侧。其会显示全部可用的使用YLVF生成的车辆包，订阅使用YLVF生成的车辆包以获取更多。
  
• 如果你有至少一个车辆包，选择点击你想要的那个。
  
• 一个二级面板会自动出现，随便几个按钮点几下来看看可以生成什么。

Eh, no for now
*: I'm planning to make one before YLVF 1.0 version release
我不到啊（就是没有
*：有计划在 YLVF 1.0 版本前做一个

NO
If you need a more detailed and in-depth explanation of this, please continue reading
不能
如果你需要一个更详细且深入的解释，请继续阅读

---

---

Basic information behind spawning

1. Game vanilla spawning using prefabs/instances to spawn objects, which is more friendly for objects W/O variations.
   
2. It is possible to apply variations to those objects, BUT ONLY by including a script inside the prefab/instance.
   
3. Spawning another object with variations HAVE TO spawn the same script again, otherwise no variation can be applied or (possibly) nothing would spawn.
   
4. Complexity of script increases as more numbers/types of variations are included.
   
5. Personal View: If one very complex script is only used once for spawning, it's very inefficient. Therefore I choose to avoid this.
   
6. Consequentially: Each vehicle pack would have its own script (provided by YLVF toolkit), therefore it can be reused whenever you want to spawn from it.
   
7. Consequentially:
   
   • These scripts are identical so they have to be controlled by a main script, otherwise conflicts would appear rapidly. Here in this case, YLVF (spawning branch) acts as the control script.
     
   • These scripts HAVE TO be able to activate automatically by YLVF so players don't have to activate each vehicle pack after subscribed.
     
   • These scripts can located in different directories (e.g.: steam folder for subscribers and local folder for creators) therefore using ANY forms of file including wouldn't work for all cases given that modding is based on Lua (with limited functions) rather than C# or C++.
8. Spawning registration is the only function in game that can reach all mod folders under all directories, and these registry keys can read by mods so spawning registration is used. This is also the reason for the DUMMY object under YLVF category if you open the vanilla spawning panel.

Drawbacks of using vanilla spawning in this case

1. Scripts cannot be reused when spawning a new vehicle
   
2. Same complexity for users to use (if customization feature kept completely)

关于生成的基本信息

1. 游戏原版生成使用预设（prefab/instance）来生成物品，其对不带有变种的物品来说是更为友好的
   
2. 你可以让这些物品带有变种，但是仅在生成的预设中包含一个脚本的时候可以实现
   
3. 生成另一个带有变种的物品必须再次生成一个同样的脚本，否则不会有任何变种或（可能）不会生成任何物品
   
4. 脚本复杂度随变种数目与类别数目增加
   
5. 个人观点：如果一个复杂脚本只被使用一次那么这就十分低效。因此我选择避免
   
6. 因此：每个车辆包会拥有其自己的脚本（由 YLVF toolkit 提供），因此它们可以在任何你想要生成车辆的时候重复使用
   
7. 因此：
   
   • 这些脚本都是完全一致的所以它们必需受一个主脚本控制，否则冲突会经常发生。在这里，YLVF（生成部分）充当控制脚本
     
   • 这些脚本必须能够被 YLVF 自动启用，以此玩家不必在订阅后再手动启用车包
     
   • 这些脚本可以位于不同文件目录下（例如：对于订阅者是steam文件夹下，对于作者则是本地文件夹下）因此在游戏的模组制作是基于 Lua（功能受限版）而不是 C# 或 C++ 的前提下，使用任何形式的文件引用都不会确保在任何条件下有效
8. 生成物品注册功能是游戏仅有的可以读取在全部模组文件夹目录下的全部模组的功能，并且其注册参数可以被模组读取。因此这里使用了生成物品注册功能。这也是你会在游戏原版生成菜单下看到分类为 YLVF，名称为 DUMMY 的物品的原因

这里使用原版生成的缺点

1. 脚本不可重复利用
   
2. 对于玩家而言的使用上有同等复杂度（若完全保留自定义生成功能）

Currently this is a game limitation: All lights on any vehicles are controlled be game at the first place. So once this vehicle is not driven (either by you or a mod), lights are turned off by game, mods have no way to turn it back on. (ref: issue #152[github.com]).

Therefore this also means: if a light on a vehicle leaves on, when the vehicle is not being driven, the light is structurally not a part of that vehicle. It's just a light attached to that vehicle (e.g.: ALS).
目前这是游戏限制：在任何载具上的全部灯光首先都是被游戏控制的。因此一旦这辆载具未被驾驶（玩家或mod控制），全部灯光就会关闭，模组没有任何办法可以开启这些灯光。（参见：issue #152[github.com]）

因此这也代表：如果车上的某盏灯（在车辆不被驾驶的情况下）保持常亮，这盏灯在结构上不属于这辆车。它就是个栓在车上的灯（比如秽土转生的ALS）