Tsar's Common Library 2.0 [Only for B41]

Tsar's Common Library 2.0 [Only for B41]

This library adds no playable content on its own — it's the shared foundation behind the Tsar's Companies vehicle line: Autotsar Trailers, Aquatsar Yacht Club, Agrotsar Farming and several Tuning Atelier packs depend on it. It provides reusable templates for vehicle equipment (fridges, stoves, fuel tanks) and tuning parts like bumpers, bullbars and roof racks, plus extra context/radial-menu functions. With over 4.6 million subscribers, it's effectively mandatory once any Tsar's vehicle mod runs on your server. As the title states, it's strictly Build 41 only, no Build 42 version yet. Add Workshop ID 2392709985 and Mod ID tsarslib to WorkshopItems=/Mods= before the dependent vehicle mods — load order matters.

Tip: If the library is missing from the list, dependent mods will throw load errors on server start — check INI ordering first.

Plan the rollout and operation

Maintain Tsar's Common Library as the shared base for all installed Tsar vehicle mods. Keep its Workshop and mod IDs ahead of dependants and update the group together. Test one vehicle, radial menu, attachment, and inventory after a restart. Do not carry the Build 41 library blindly into another branch; first confirm that every dependant package has a compatible release.

Before changes, back up the save, sandbox configuration, and server INI, and record the Workshop ID, mod ID, game branch, and order. Both lists must contain the same projects in dependency order; a Workshop download alone does not enable the mod. Start a world copy, connect at least two clients, and test the core feature, persistence, death or reconnecting, and a full restart. Review console.txt and the server log for missing files or Lua errors. After Workshop updates, update dependencies together and retain the last working combination. Before removal, clean up additional items, vehicles, clothing, or slots on a copy. When moving between Build 41 and 42, verify every mod individually; a similar name is not proof of compatibility. This protects the live save from incomplete downloads and branch conflicts.