Cruiser

Cruiser is mainly worth checking through vehicle access route, driving, speed, and terrain behavior, fuel, repair, health, and storage, ownership and removal behavior, inventory, backpack, and toolbelt screens, and crafting, workstation, and recipe screens. Do that in a copied save or test server before changing a main world.

Use Nexus Mods listing for exact file names, branches, screenshots, and update notes, then confirm the in-game behavior listed above still works after a restart.

• Check whether the vehicle is crafted, bought, looted, quested, or admin-spawned.
• Drive through roads, bridges, trader areas, POI doors, hills, and rough ground.
• Refuel, damage, repair, fill storage, save, restart, and reconnect before public use.
• Test existing vehicles on a copied world before updating or removing the pack.

Cruiser needs testing across the whole vehicle loop: getting it, fuelling and repairing it, storing items in it, and driving it on real roads and POIs.

• Check crafting, trader access, loot, or admin spawn separately.
• Drive through cities, bridges, trader areas, and rough terrain.

The important test is persistence: ownership, vehicle storage, repair state, fuel, position, and removal behavior after restart.

• Do not use player-owned live vehicles as the first removal test.
• Keep a world backup before changing a vehicle pack.

On servers, write parking, abandoned vehicle, storage loss, and admin-recovery rules before the MOD becomes part of regular play.

• Restart and reconnect before calling the setup stable.
• Tell players how vehicle storage is handled on rollback.