To permanently enable Rust’s normal Cargo Ship event, set cargoship.event_enabled true as an administrator, then save the same setting in rust/server/<server.identity>/cfg/server.cfg and restart the server. The file must contain the command without a leading +. This enables the event after every restart; it does not keep a ship continuously present. For immediate replacement when one leaves, use a plugin such as Endless Cargo.
Playing with friends? Godlike.Host runs hosted Rust servers from 10 data-center locations, with free DDoS protection.
What cargoship.event_enabled controls
cargoship.event_enabled is the Rust server convar that turns the standard Cargo Ship event on or off. Setting it to true permits the game’s ordinary event scheduler to spawn Cargo Ships. Setting it to false disables that event. It is a server-side control, so a normal player cannot run it from the client.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
The command only changes the running server until you store it in a startup configuration. A command entered in a console or RCON session is therefore useful for testing or for enabling the event immediately, but it is not by itself a permanent configuration. “Permanent” here means persistent across process restarts, not a ship that remains in the world forever.
Where an administrator can run the command
| Administration surface | Use |
|---|---|
| Dedicated-server console | Enter the command in the process or hosting panel console. |
| RCON | Send the command through an authenticated RCON connection. |
| In-game administrator F1 console | Run it while connected with the required server administrator privileges. |
Use this exact syntax:
cargoship.event_enabled trueSuccessful execution changes the live convar. It does not edit a file, and it will be lost if the server starts without the setting saved in its configuration or startup arguments. Keep the command in plain text with a space between the convar name and true; do not add quotation marks or a semicolon.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Make Cargo Ship stay enabled after every restart
The dependable vanilla method is to put the convar in the server identity’s server.cfg. Facepunch documents this file as being read at startup and taking priority over command-line settings. The identity matters: Rust can host more than one server directory, and editing the wrong identity leaves the server you actually run unchanged.
- Obtain administrative access. Stop the server before editing files if your host recommends that workflow, or use the panel’s file manager or an SFTP connection with the server stopped. You can also issue the live command first to test permissions.
- Identify the active server identity. Find the directory used by the running instance under
rust/server/. Replace<server.identity>below with that exact directory name. On a host with several instances, compare the identity in the startup profile with the directory you are opening. - Open the configuration file. Edit
rust/server/<server.identity>/cfg/server.cfg. Create the file if your installation does not already have one, while preserving the directory and filename exactly. Do not edit a sample file, a backup, or another instance’s cfg directory. - Add the convar on its own line. The file should contain:
cargoship.event_enabled true- Do not add a plus sign in this file. The
+prefix belongs to startup arguments, not toserver.cfg. Writing+cargoship.event_enabled truein the cfg file can prevent the setting from being interpreted as intended. - Save and restart. A restart causes Rust to read the file. Merely saving it while the process is running does not reliably reapply the convar. Allow the process to shut down cleanly, then start the same server identity again.
- Verify after startup. From an administrator console, check the convar or run the true-setting command again. Confirm the server is using the identity whose cfg file you edited before investigating event timing or plugins.
Facepunch’s documented startup behavior is important when diagnosing conflicting values: the server reads server.cfg at startup and gives it priority over settings supplied on the command line. Treat that file as the canonical vanilla location, especially after migrating a server or changing a hosting panel profile.
Using startup arguments instead
Some managed hosts expose only a startup-command field. In that case, add the setting as a command-line parameter using the startup form:
+cargoship.event_enabled trueStartup arguments are read when the process launches. The distinction is important: use the leading + in the startup-argument field, and omit it in server.cfg. If both are present, the startup-read configuration file is the authoritative place to check because Facepunch states that server.cfg takes priority over command-line settings.
Startup arguments are useful when a panel does not provide file access, but they are tied to that panel’s launch profile. If you later clone the server, change the identity, or move hosts, recheck that the parameter followed the new profile. A cfg file inside the active identity is generally easier to audit and migrate with the rest of the server data.
What “permanently enabled” does—and does not—mean
Permanent enablement means the normal Cargo Ship event is allowed every time the server starts. It does not mean a ship remains spawned forever, that a ship appears immediately on wipe, or that one ship is replaced the instant it leaves. Vanilla Rust still follows its event scheduling and despawning behavior.
There is no documented vanilla interval setting in the official material for this configuration that forces a new ship to spawn continuously. If your goal is simply to let the standard event occur after restarts, the convar and cfg file are sufficient. If your goal is uninterrupted ship availability, you need additional server software. Do not keep toggling the convar while waiting for an event; a true value permits scheduling but does not turn the command into a manual spawn command.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
This distinction also prevents a common support mistake. A successful post-restart query proves that persistence works, but it does not prove that the ship should already be visible. Check the map and normal event timing separately from the configuration value.
How to keep a Cargo Ship continuously available
The uMod plugin Endless Cargo is designed for the continuous-use case. Its stated behavior is to call a new Cargo Ship as soon as the active ship leaves. That is a different outcome from enabling the vanilla event: the plugin manages replacement rather than merely allowing Rust’s normal scheduler to run.
Install and configure the plugin
- Install the current plugin through the normal uMod installation workflow for your server.
- Restart or reload the plugin according to your uMod administration procedure so that its configuration file is generated.
- Open the plugin’s JSON configuration and review every option before enabling it on a populated server. Plugin configuration files are commonly created in the server’s oxide configuration area.
- Set the event duration, loot-round count, spacing, NPC behavior, and logging options to match your server’s rules. The available controls and their defaults can change with the installed plugin version, so use the generated file rather than copying values from an unrelated release.
- Test replacement on a staging or low-population instance. Watch the server console for errors, confirm the ship can navigate, and check that the replacement does not create an unintended loop of overlapping events.
- Keep the administrator command
killcargoavailable for emergencies. The plugin page lists it as an admin control for removing the active cargo event.
uMod plugins may expose console commands usable from the in-game console, the server process, or RCON. Protect those interfaces with the permissions and authentication controls supplied by your host. A plugin adds a maintenance obligation: after Rust updates, check that the plugin still loads, its JSON remains valid, and its event hooks behave normally.
Endless Cargo is appropriate when “always active” means that another ship should be called promptly after the current one leaves. It is not a substitute for a valid ocean path. A plugin can request a ship, but the map and Rust’s navigation systems still determine whether that ship can travel correctly. If your requirement is only persistence after reboot, adding a plugin creates unnecessary maintenance and should be avoided.
Custom maps can prevent Cargo Ship from working
On a standard island map, enabling the convar is usually enough. Custom maps require a navigable ocean area because Rust generates an ocean patrol path for the ship. Facepunch explains that a map with little or no ocean can stall during path generation. A ship may fail to spawn, remain static, or be unable to navigate if the required path was never generated.
Signs that the map is the problem
- The convar is still true after restart, but no ship appears.
- Server startup pauses or reports problems while generating an ocean patrol path.
- The map has a coastline without enough surrounding ocean for a patrol route.
- A manually or plugin-spawned ship appears motionless or follows no valid route.
Map-side fixes
The preferred fix is to rebuild or edit the custom map with enough surrounding ocean for a valid patrol path. This preserves normal Cargo Ship navigation. If the map intentionally has no usable ocean, Facepunch documents disabling both the event and path generation:
cargoship.event_enabled false
baseboat.generate_paths falseFor the no-ocean case, Facepunch also lists:
ai.ocean_patrol_path_iterations 0Those settings are a compatibility choice, not a way to make a ship navigate without water. Do not force-spawn Cargo Ship on a map with no generated path and expect normal movement; the result can be a static or malfunctioning event. If a custom map is intended to support Cargo Ship, fix its ocean coverage instead of compensating with repeated spawn attempts.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Map compatibility should be checked before plugin tuning. Otherwise, an administrator may mistake a navigation failure for a bad plugin configuration, change duration or spacing repeatedly, and still have a ship that cannot move. Read startup output for path-generation errors, then test with the vanilla event before adding replacement logic.
Troubleshoot a setting that resets after restart
The command works live but is gone after reboot
- Check that the line is in
cfg/server.cfgfor the active server identity, not a different instance or template directory. - Remove a leading
+if it appears in the cfg file. - Confirm the file was saved on the server rather than only in a local editor or browser tab.
- Restart the actual Rust process after saving; a map wipe or plugin reload is not the same as a process restart.
- Verify the convar from the console or RCON after startup before changing plugins.
- Check that the host did not launch the server with a different identity or overwrite the cfg from a deployment template.
The file is correct but the ship never appears
Separate configuration persistence from event timing. A true convar permits the normal event; it does not promise an immediate spawn. If an extended period passes with no event, inspect the map’s ocean coverage and path-generation messages first. On a custom map, a valid path is a prerequisite for a moving ship.
Run the convar query after startup, record the result, and then inspect the server console while waiting for the normal scheduler. If the value is true and there are no path errors on a standard map, avoid treating the absence of an immediate ship as proof that the cfg failed.
A plugin is installed but replacement fails
- Confirm the plugin loaded without errors after the latest Rust update.
- Open its generated JSON and check that duration, spacing, loot-round, and NPC options contain valid values for that version.
- Review permissions and the RCON or console source used for administrative commands.
- Use
killcargoonly as an administrator, then observe whether the plugin creates one replacement rather than several. - Test with the vanilla convar enabled and with other cargo-related plugins temporarily disabled to identify conflicts.
- Check the map’s ocean path independently; plugin replacement cannot repair missing navigation data.
The ship is static on a custom map
A static ship indicates a navigation-path problem more often than a missing convar. Restore sufficient ocean around the map or disable the event on that map. Spawning additional ships without fixing path generation can increase clutter without restoring navigation.
Recommended Free Tools
Vanilla configuration or a continuous-cargo plugin?
| Decision point | Vanilla cfg/startup setting | Continuous-cargo plugin |
|---|---|---|
| Persistence method | server.cfg or startup arguments read when the server launches |
Plugin installation plus a generated JSON configuration |
| Behavior | Allows Rust’s normal Cargo Ship event schedule | Can call a replacement when the active ship leaves |
| Control surface | The cargoship.event_enabled convar |
Plugin settings, commands, and administrator permissions |
| Map requirement | Requires a usable ocean patrol path for normal navigation | Still depends on a map where spawned ships can navigate correctly |
| Maintenance | Minimal; recheck the identity path after migrations | Must be checked for compatibility and configuration changes after Rust updates |
| Best fit | Event should be available normally after every restart | Players need prompt replacement or controls beyond the vanilla convar |
Choose the vanilla route when “enabled after every restart” is the requirement. Choose the plugin route when players need a ship available again immediately after the previous one departs, or when you need event duration, loot rounds, spacing, NPC, or logging controls beyond the vanilla convar.
There is no physical hardware or Amazon product required for this task. The work is server administration: an authenticated command, a cfg or startup edit, and, only when needed, plugin software. A managed Rust host may expose console, RCON, startup arguments, and file-manager controls, but the exact panel features depend on the host.
A repeatable verification checklist
- Use an administrator account or authenticated RCON session.
- Run
cargoship.event_enabled trueonce to confirm the command is accepted. - Locate the active identity under
rust/server/. - Place
cargoship.event_enabled truein that identity’scfg/server.cfg, without+. - Restart the server and query the convar again.
- Wait for the normal event rather than treating immediate appearance as proof of persistence.
- If the map is custom, inspect ocean coverage and path-generation output.
- If uninterrupted availability is required, install and test a maintained continuous-cargo plugin instead of trying to achieve that behavior with the convar alone.
- After any Rust update, verify the convar, map navigation, and plugin load status before reopening the server to players.
Answers to common administration questions
Can an ordinary player enable Cargo Ship?
No. The convar is a server administration control. It must be issued through the server console, an authenticated RCON connection, or an administrator F1 console.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Should I put a plus sign before the command?
Only when entering it as a startup argument. In server.cfg, use cargoship.event_enabled true with no leading plus sign.
Does this command spawn a ship immediately?
No. It enables the normal event. Continuous replacement or custom timing requires a plugin designed for that purpose.
Why does a custom map break Cargo Ship?
A map without enough ocean may not produce the ocean patrol path the ship needs. Expand the usable ocean area or disable the event and path generation for that map.
Where exactly should the cfg file be?
Use rust/server/<server.identity>/cfg/server.cfg for the identity that the running instance actually launches. Editing another identity, a template, or a backup does not change the live server.
Is a map wipe enough to apply the setting?
No. Saving the cfg and restarting the Rust process is the reliable application step. A wipe or plugin reload is not equivalent to a process restart.
Can I use both startup arguments and server.cfg?
You can encounter both, but keep the canonical value in server.cfg and verify that file first. Facepunch documents that the startup-read cfg takes priority over command-line settings.
What should I do if I want a ship always available?
Use a maintained continuous-cargo plugin such as Endless Cargo, configure its JSON options, and test it on a compatible map. The vanilla convar alone does not provide immediate replacement.
Will Endless Cargo work on a no-ocean map?
Not reliably. Replacement software still depends on a generated ocean patrol path. Fix the map’s ocean coverage or disable Cargo Ship on a map that cannot support navigation.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →What should I check after a Rust update?
Confirm that cargoship.event_enabled remains true after restart, inspect path-generation output on custom maps, and verify that the plugin loads without errors and retains valid JSON configuration.
Frequently Asked Questions
How do I permanently enable Cargo Ship on my Rust server?
Run cargoship.event_enabled true as an administrator, put the same line without a leading + in rust/server/<server.identity>/cfg/server.cfg, and restart the server.
Why does Cargo Ship stop spawning after a restart?
The live command does not persist by itself. Check that the line is in the active identity’s server.cfg, has no leading plus sign, was saved on the server, and was followed by a full process restart.
How do I make Cargo Ship always active?
The vanilla convar enables normal scheduling but does not keep a ship continuously present. Use a maintained plugin such as Endless Cargo for replacement when the active ship leaves.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What is the cargoship.event_enabled command?
It is the server convar that enables or disables the standard Cargo Ship event. Use true to permit automatic spawning and false to disable it.
Why is Cargo Ship static on my custom map?
The map may lack enough ocean for Rust to generate a patrol path. Restore usable ocean coverage or disable the event and path generation rather than repeatedly spawning ships.
Do I need a paid product to enable Cargo Ship?
No physical product is required. You need administrator access to the server console, RCON, or F1 console, plus access to the cfg file or startup arguments. A plugin is optional for continuous replacement.
The Bottom Line
For normal, restart-persistent Cargo Ship events, run cargoship.event_enabled true, save it without + in the active server identity’s cfg/server.cfg, and restart Rust. Verify the convar after startup. If you need a ship replaced as soon as one leaves, use and maintain a compatible plugin such as Endless Cargo; if the map lacks a usable ocean patrol path, fix the map or disable the event rather than forcing spawns.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
