Missions.lua
*
Missions Config (missions.lua)
This configuration defines pre-delivery and delivery missions for each vehicle class and the associated mission metadata.
Missions Per Class
Config.Missions = {
["d"] = { pre = { }, delivery = { } },
["c"] = { pre = { "meet_contact", "hack_laptop" }, delivery = { } },
["b"] = { pre = { "meet_contact" }, delivery = { } },
["a"] = { pre = { }, delivery = { } },
["s"] = { pre = { }, delivery = { } }
}- pre – missions that must be completed before vehicle pickup.
- delivery – missions that must be completed after picking up the vehicle.
- Missions are assigned per vehicle class (
d,c,b,a,s) to adjust difficulty and complexity.
Mission Data
Config.MissionData = {
["meet_contact"] = {
title = "Meet Shady Contact",
desc = "Find the contact and collect the key/device.",
roles = {"hacker", "driver", "lookout", "coordinator"}
},
["hack_laptop"] = {
title = "Hack the Laptop",
desc = "Complete the hack to retrieve vehicle GPS.",
roles = {"hacker", "driver", "lookout", "coordinator"}
}
}Explanation of Fields
| Field | Description |
|---|---|
title | Name of the mission shown to players. |
desc | Brief description of mission objectives. |
roles | List of player roles involved in the mission. Can be hacker, driver, lookout, coordinator, etc. |
Notes
- Pre-missions can include tasks like hacking, meeting contacts, or gathering intel before the boost begins.
- Delivery missions can include tasks during or after the vehicle drop-off.
- Roles allow team-based gameplay, where different players perform specialized tasks.
- You can expand
MissionDatawith custom missions for higher-tier vehicle classes. - Mission flow is flexible and can be combined with minigames, tracker removal, or random challenges for added variety.