Dependences (Required):

Try Before You Buy at Karuza's Plugin Corner - https://discord.gg/jxwVpn9mEq

The Trucker Event brings utility and some role play fun to the Karuza semi trucks and any similar custom vehicle truck/trailer combos.

Trailers will spawn at configured monuments, marked on the map, ready to be picked up.

Trailers automatically spawn at configured monuments and must be picked up by the trucks. Players then transport them to randomized delivery zones within a specified time limit, which will earn them a reward of your choosing. Additionally, if all trailers during the event runtime are delivered, a bonus reward can be given to all players that successfully delivered a trailer.

The plugin features a flexible route system, allowing fully random deliveries or predefined routes between specific monuments. You can configure different delivery types which can yield differetn rewards, time limits, and spawn locations.

Players receive guidance through map markers that display trailer locations, as well as marking delivery locations when towed.

The reward system is customizable, supporting commands (with player steamid wildcard support), item rewards, and chance-based payouts. You can also grant bonus rewards when all deliveries are completed, encouraging full participation.

Several vanilla monuments are pre-configured with trailer spawn positions and drop off locations. You can easily change the locations or add additional monuments in the config file. I recommend using rustedit to define positions relative to the monument.

With built-in commands, you can create custom monument positions, add trailer spawn points, and define delivery zones in-game.

The event is aimed at PVE/RP servers, however PVP action can still take place in the form of destroying trailers to prevent players getting rewarded, or hijacking towed trailers from other players.

An optional leaderboard plugin is also available for free.

Core concept:

• Trailers spawn at configured monuments
• Players attach them to their trucks
• Deliver to a randomized destination within a time limit
• Earn rewards for successful deliveries

Spawn and delivery points:

• Supports all vanilla monuments with several pre-configured
• Optionally add custom monuments anywhere on the map using commands
• Multiple spawn points and delivery zones per monument are supported

Route system:

• Fully random routes between available monuments
• Optionally you configure delivery routes between specific monuments
• Control which delivery types can spawn where

Visual and audio cues:

• Trailer locations, their destination and remaining time will be displayed on the map
• When a trailer is attached, driver will see the destination on the map, in addition to a visible marker
• If the trailer is lost/detached, an audio cue will warn the driver, and a chat message will advise the trailer has detached.

Simple reward system:

• Player is given the configured reward once they deliver the trailer to it's destination
• Reward can be configured based on the type of delivery
• Reward can vary based on the configured chances
• Bonus reward to all participating players if all trailers are delivered.

Admin Commands:

kot.start - forces the event to start (works in chat and console)

kot.stop - forces the event to end (worksd in chat and console)

truckercreate "position name" - allows you to create a custom position anchor, for example at a custom monument

truckeraddspawn "position name" - adds a trailer spawn point relative to the custom position name configured above. Spawn rotation will be the direction you are looking when running this command.

truckerdrop "position name" - add a delivery zone relative to the custom position name configured above.

Hooks:

void OnTruckerStart(int eventId) - called when the event starts

void OnTruckerEnd(Dictionary<string, object> summary) - called when the event ends, where summary contains:

• eventId (int)
• spawned (int)
• completed (int)
• failed (int)
• completedByUser (Dictionary<ulong, object>)

API:

bool IsTruckerActive() - returns true if the event is currently running

Default config: