Custom-Physics Drivable Vehicle in Luau
ESCOPO
Generate a professional drivable vehicle implementation for Roblox, suitable for cars or motorcycles, with custom physics based on modern forces/constraints. The result prioritizes progressive acceleration, braking, smooth steering, configurable suspension, speed limit, traction, controlled drifting, and predictable network behavior.
The prompt requests a complete architecture with a shared ModuleScript, an authoritative server Script, and a LocalScript for control capture and visual feedback. It also requires RemoteEvents validation, preventing the client from controlling speed, forces, damage, or any important vehicle state.
Ideal for developers who want to replace generic VehicleSeat systems with an extensible, commented base adaptable to custom vehicles. Just provide the real Explorer structure, part names, constraints, and remotes already in place to receive files ready to paste into Roblox Studio.
Conteudo
Prompt principal
Act as a senior Roblox developer specialized in Luau, vehicle physics, client-server architecture, and multiplayer security. Create a complete drivable vehicle system with custom physics for [CAR/MOTORCYCLE], ready to integrate into my Roblox game. Do not deliver pseudocode, incomplete snippets, nonexistent APIs, or a solution based only on VehicleSeat without its own physics. Before generating the code, you must use the context below. If any essential field is missing, ask at most 8 objective questions before programming. If there is enough information, assume reasonable values, state those assumptions in a short section, and deliver the complete solution. MY GAME CONTEXT (I will fill in): - Vehicle type: [car / motorcycle] - Path and name of the vehicle Model in Explorer: [e.g.: Workspace.Vehicles.Car01] - Root part/chassis and PrimaryPart: [name] - Name of the VehicleSeat, Seat, or occupancy system: [name/path] - Wheels: [names and positions: front left, front right, rear left, rear right; or motorcycle] - Existing constraints per wheel (HingeConstraint, SpringConstraint, attachments): [detail] - Existing attachments and their respective names: [detail] - Existing RemoteEvents/RemoteFunctions and their paths: [detail or “none”] - Current structure of ReplicatedStorage, ServerScriptService, and StarterPlayerScripts: [detail] - Is the vehicle spawned manually, by garage, or cloned from ServerStorage?: [detail] - Desired parameters: maximum speed, acceleration, reverse, brake force, steering angle, suspension height/stiffness/damping, grip, drift, and approximate mass: [detail] - Target platform: [PC / mobile / console / all] - Additional rules, such as fuel, damage, vehicle ownership, respawn, and multiple vehicles: [detail] Design the solution using a robust architecture in three files, adapting the paths to the data I provided: (1) a ModuleScript called VehiclePhysicsConfig in ReplicatedStorage.Shared, containing Luau typing, parameters, utilities, and per-vehicle configuration; (2) a Script called VehicleServer in ServerScriptService, responsible for creating/configuring connections, controlling authoritative state, assigning network ownership when appropriate, validating the driver, and applying or authorizing physical forces; (3) a LocalScript called VehicleController in StarterPlayer.StarterPlayerScripts, responsible exclusively for reading keyboard/gamepad/touch input, smoothing local input, and sending minimal commands to the server. If my project requires another location, explain the change precisely and keep the separation of responsibilities. Implement modern custom physics with constraints and/or forces compatible with current Roblox, preferring VectorForce, AngularVelocity, AlignOrientation, HingeConstraint, and SpringConstraint when it makes sense. Do not use BodyVelocity, BodyGyro, or other legacy BodyMovers unless I explicitly ask for them. The system must include: progressive acceleration and deceleration; reverse gear; braking; speed-dependent steering; smooth steering; speed limit; rolling resistance and drag; configurable traction; controlled drifting; configurable suspension; reliable detection of wheels on the ground using RaycastParams that exclude the vehicle itself; and stabilization to reduce flipping without making handling feel artificial. For motorcycles, include controlled visual/physical leaning in turns and appropriate stabilization; for cars, handle front steering and front/rear/4x4 traction according to configuration. Security is mandatory. The client can never decide damage, currency, inventory, teleport, final speed, final force, vehicle ownership, or occupant. Every input sent by RemoteEvent must be validated on the server: the player is the authorized occupant, the vehicle exists, values are finite numbers, they are within the expected range, sending frequency is limited, the vehicle state allows the command, and the player is not trying to control someone else’s vehicle. Include simple rate limiting per player/vehicle and cleanup of connections, states, and ownership when the player leaves, dies, leaves the seat, or the vehicle is destroyed. Do not trust names sent by the client to locate instances. Deliver the response in this order: 1) brief architecture overview; 2) exact installation tree in Explorer; 3) all complete files, each in its own markdown block with ```lua, preceded by the path, type (Script, LocalScript, or ModuleScript), and file name; 4) explicit list of objects/Attachments/Constraints that I need to create or rename in the vehicle; 5) installation and testing instructions in Roblox Studio, including Play Solo and Start Server with 2 Players testing; 6) diagnostic checklist for problems such as wheels not touching, vehicle not moving, inverted steering, network ownership, and missing RemoteEvent. The code must be valid Luau, complete, commented in Brazilian Portuguese, with --!strict when viable, types for relevant structures, WaitForChild with timeouts, and useful warn messages. Avoid external dependencies. Preserve my names and paths when provided; use default names only when I do not provide them. Explain where to adjust driving parameters without requiring changes to the core logic.
