Nukes

Nukes are claimable rewards posted in Discord for one Premium game server. Use them for repeating community drops of Helios currency, XP, kits, or Rust items. Players claim from the posted Nuke; a claim limit lets you cap the number of successful claims on each drop.

Staff need Manage Server permission and Premium on the selected Rust server. Creating a regular setup posts the first drop immediately. Opening the editor or changing its fields only prepares a draft.

Open Nuke Manager on the dashboard

1. Open the intended Rust server in the dashboard.
2. Choose Discord → Nukes, then expand Nuke Manager.
3. Find Automatic Nuke Rewards and click Create Nuke.

The saved row shows the reward, repeat interval, channels, claim limit, mention role, Ends, and Last posted. This screenshot contains an older testing setup; its amount and dates are not suggested settings. Read Stop recurring drops before relying on an Expired badge.

Create a regular Nuke

1. Choose Nuke Reward and fill in its fields using the table below.
2. Set Repeat Every and Repeat Unit, such as 1 → Hours. The repeat interval can be between one minute and 30 days.
3. Set the duration shown as Run For and Run For Unit. The example below uses 1 → Days. See the timing note below before using it as a stopping point.
4. Leave Mention Role → No role ping unless you intend to notify a role on every drop.
5. To cap successful claims on each posted drop, enable Limit total claims and enter Maximum Claims. Leave it off for unlimited claimants. Each person can still claim a particular drop only once.
6. Under Post Nuke In, select the intended Discord channels. Check the whole list for an already-selected channel before adding another. Helios supports one to 25 destinations per setup.
7. Review the reward, timing, channels, and role ping. Create & Post Nuke saves the setup and posts its first drop immediately; Cancel closes it without creating a Nuke.

Reward	Fields and delivery
In-game currency	Enter Currency Amount. Despite the selector label, a regular currency Nuke credits the player's Helios Wallet; it does not spawn a Rust item.
XP	Enter XP Amount for Battle Pass XP.
In-game kit	Choose a live Kit from the selected Rust server, add a friendly Name in /bag, and enter Reward Worth. The claim adds the kit to /bag.
Rust item	Choose Rust Item, enter its Item Quantity, a friendly Name in /bag, and Reward Worth. The claim adds the item reward to /bag.

In this example, each new drop offers 100 currency to each successful claimant, up to 10 claimants. The amount is not split between them. The claim limit belongs to each drop, rather than the whole recurring setup. Posting the same drop in multiple channels does not give a player another claim on that drop.

Use the actual saved kit on your selected server. Name in /bag is the friendly reward name, while Reward Worth is the stored value shown for that reward; it is not an additional coin payout. A kit or item Nuke claim goes to the bag for later redemption. See Bag and Items for linking, being online, and using a server-bound reward.

These editor screenshots are unsaved examples. No Nuke was posted or claimed while capturing them. The immediate-first-post warning is important: do not use Create & Post Nuke just to preview a reward.

Timing, claims, and stopping a setup

Repeat Every controls the gap between recurring posts. Each posted Nuke has its own claim state and closing time. Check Closes on the actual Discord drop rather than assuming that another post closes the previous one. Drops may overlap, and a player can claim separate drops when eligible.

The Discord setup calls its duration Expires; the dashboard labels its duration Run For. The current reward worker uses the saved duration when building each drop's claim window, capped at 30 days for regular Nukes. A paid Nuke has a separate fixed 24-hour claim window.

Stop recurring drops

To stop future recurring posts, find the saved setup under Automatic Nuke Rewards and choose Remove, then confirm the removal. Removing a setup does not take back rewards players already received.

Do not rely on Run For or the Expired badge alone to stop recurring posts. The current worker does not enforce that setup end time as a stop condition. Remove the setup when the event is over, including after a one-off test. Check that its saved row is gone before leaving it unattended.

Paid Nuke delivery and images

Paid delivery

1. In Nuke Manager → Paid Nuke Delivery, choose Paid Nuke Channel.
2. Choose an optional Mention Role, or No role ping to avoid notifications.
3. Click Save Paid Settings.
4. Configure the paid reward through Helios Store products or the existing Tip4Serv paid Nuke parse guide.

Paid delivery's channel and role are shared across the whole Discord community. Changing them while viewing one Rust server also changes the destination for other servers' paid Nukes. Regular setups keep their own selected channels and mention role. The screenshot shows existing testing choices, including an Admin role ping; choose the destination and ping behavior your community actually needs.

Paid Nukes follow a supported purchase or reward parse and have a 24-hour claim window. Saving the paid delivery settings does not create a store product, complete a purchase, or post a free test drop.

Nuke image

Under Nuke Image, enter a Direct HTTPS Image URL, then click Save Image. This immediately saves the image for the selected game server; it uses a different scope from the shared paid delivery settings. View Current opens the saved image. Use a direct image URL, not a page containing an image.

Prefer Discord?

Run /nuke server:"<SERVER>". You need Manage Server permission and Premium on that selected server.

The first screen gives you five choices:

• New — make a new recurring nuke.
• List — review saved rewards, how often they post, their claim window, and their channels.
• Remove — permanently delete a saved nuke.
• Nuke Image — submit a new image link for future drops.
• Paid Nuke Settings — choose where purchase-triggered nukes post and which role they mention.

Create a regular Nuke in Discord

1. Choose New.
2. Pick Currency, XP, Kit, or Item.
3. Fill in the reward. Kits need their saved kit name, a name players will see in /bag, and a worth. Items need their Rust shortname, /bag name, quantity, and worth.
4. Set Frequency for how often the nuke posts, such as 15m, 1h, or 1d.
5. Set Expires for the reward duration, such as 12h or 1d. See the timing and stopping notes above.
6. Choose one or more Discord channels. Add a mention role only if you want to notify that role every time.
7. Review the summary and choose Finalize.

Use Max Claims to cap successful claimants on each drop. Leave it off when everyone may claim before that drop closes.

For a one-off event drop, create it, confirm it posted correctly, then remove that saved setup so it cannot post again later.

List reviews saved rewards and destinations; Remove deletes a saved setup. Nuke Image opens the image form. Paid Nuke Settings → Set Nuke Channel changes the shared paid destination; Paid Nuke Mention sets its role and Clear Paid Mention removes the ping.

If a nuke is not working

Check the selected server, its Premium status, the saved channels, and the configured reward name. Helios needs View Channel, Send Messages, and Embed Links in each destination. A dashboard create attempt that cannot post to any chosen channel reports an error and removes that failed setup; review the error and refresh before retrying.

For kits, the kit must exist on that exact game server. For items, use the correct Rust item. If a kit or item claim reports a full bag, free a slot and follow Helios's response before retrying. If it says already claimed, expired, or maximum claims reached, another click does not create another reward. Check the player's Wallet, Battle Pass XP, or /bag according to the reward type.

Currency and XP claims do not use the kit/item bag-redemption step. For an in-game kit or item redemption problem, check the linked gamertag, required server, online status, and the bag item's server binding.