Antinuke Logs

Overview

The Antinuke Logs system provides detailed logging of all security events, protection triggers, and configuration changes in your server. By setting up a dedicated log channel, you can monitor antinuke activity in real-time and maintain an audit trail of security incidents.

Log channels receive detailed information about every antinuke action, including who triggered protections, what actions were taken, and when settings were modified.

Access Control

Only the following can manage the log channel:

Server Owner: Full access to configure log channel
Extra Owners: Can set and modify the log channel
Antinuke Administrators: Can set and modify log channel

Regular members cannot view or modify log channel settings, ensuring security event privacy.

Commands

setlog

Configure the log channel for your antinuke system. If no channel is specified, the bot will automatically create a “Celestia-logs” channel with proper permissions.

,setlog [#channel]

,setlog #security-logs
,setlog
,anlog #mod-logs
,logset

Aliases: anlog, logset
Permissions: Server Owner or Antinuke Administrator

Running the command without arguments will auto-create a hidden “Celestia-logs” channel if one doesn’t already exist.

setlog (view status)

View your current log channel configuration and available options.

,setlog

,setlog
,anlog
,logset

Aliases: anlog, logset
Permissions: Server Owner or Antinuke Administrator

Running the command without arguments displays the current log channel and configuration instructions.

What Gets Logged

The log channel records detailed information about all antinuke activities:

System Changes
Protection Settings
Security Events

Track system status modifications:

Antinuke system enable/disable
Protection module enable/disable
Antinuke administrator additions/removals
Log channel configuration

Auto-Creation Feature

Automatic Channel SetupWhen you run ,setlog without specifying a channel, Celestia will automatically create a secure log channel for you.

Auto-created channel features:

Name: Celestia-logs
Type: Text channel
Visibility: Hidden from @everyone
Permissions: Bot and command executor can view
Topic: Descriptive text indicating antinuke purpose

Example:

,setlog

This will create a new channel or use an existing “Celestia-logs” channel.

Setup Process

Choose Setup Method

Decide whether to use an existing channel or let the bot create one:Option 1: Use existing channel

,setlog #your-channel

Option 2: Auto-create channel

,setlog

Verify Permissions

Ensure the bot has the following permissions in the log channel:

View Channel
Send Messages
Embed Links
Attach Files

Without proper permissions, logs cannot be sent to the channel.

Confirm Configuration

Check that the log channel is set correctly:

,setlog

You should see your configured channel in the status display.

Monitor Logs

Watch for antinuke events in your log channel. Test by triggering a protection or making a configuration change.

Channel Requirements

For a channel to function as an antinuke log channel, it must meet these requirements:

Text-Based

Must be a text channel or announcement channel

Bot Access

Bot must have view and send message permissions

Embed Permissions

Bot needs permission to send embeds and attachments

Stable Channel

Should not be deleted or frequently modified

Log Format

All antinuke events are logged as detailed embeds showing exactly what happened and who made the change:

Setting Updates
Admin Changes
Protection Changes
Punishment Updates
Protection Triggers

Antinuke setting updatedShows configuration changes like log channel setup:

Setting: What was changed (e.g., log channel)
Value: New value (e.g., #an-logs)
Changed By: User who made the change
Server: Server name and timestamp

Common Use Cases

Initial Setup with Auto-Creation

,setlog

Let Celestia automatically create a secure, properly configured log channel for you. This is the fastest setup method.

Using Existing Moderation Logs

,setlog #mod-logs
,setlog #security
,setlog #admin-logs

Integrate antinuke logs with your existing moderation or security logging channel.

Checking Current Configuration

,setlog

View your current log channel and get setup instructions if not configured.

Switching Log Channels

# Switch to a different channel
,setlog #new-security-logs

Change your log channel destination when reorganizing your server structure.

Private Security Monitoring

,setlog

Auto-created channels are hidden from @everyone, perfect for private security monitoring visible only to admins.

Best Practices

Set Up Logs Early

Configure your log channel as soon as you set up antinuke protections.

,setlog

Early setup ensures you don’t miss any security events during your server’s protection period.

Keep Channel Private

Ensure only trusted staff can view the log channel to prevent information leaks.Recommended Permissions:

@everyone: No access
Moderators: View only
Admins: View and manage

Regular Monitoring

Check your log channel regularly for activity and configuration changes.

# Quick check of log channel status
,setlog

Monitor for:

System enable/disable events
Protection configuration changes
Administrator additions or removals
Unexpected punishment modifications
Protection trigger patterns

Archive Old Logs

Consider periodically archiving old logs to keep the channel manageable while maintaining records.

Discord has built-in message search that works well for recent logs, but consider exporting older logs for long-term storage.

Verify Bot Permissions

Regularly check that the bot still has proper permissions in the log channel.Required Permissions:

View Channel ✓
Send Messages ✓
Embed Links ✓
Attach Files ✓

Troubleshooting

Logs not appearing in channel

Problem: No logs are being sent to the configured channelSolutions:

Verify bot permissions: View Channel, Send Messages, Embed Links
Check if the channel still exists and wasn’t deleted
Confirm log channel is properly set: ,setlog
Try setting the channel again: ,setlog #your-channel

If the log channel is deleted, you must set a new one for logs to resume.

Cannot set log channel

Problem: Command fails when trying to set log channelPossible Causes:

You lack required permissions (not owner/antinuke admin)
Bot lacks “Manage Channels” permission for auto-creation
Channel mentioned is not a text channel

Solution: Check your permissions with ,setlog and ensure you’re mentioning a valid text channel.

Auto-creation fails

Problem: Bot cannot create Celestia-logs channelCause: Bot lacks “Manage Channels” permissionSolution:

Grant bot “Manage Channels” permission
Or manually create a channel and set it: ,setlog #manual-logs

Check the bot’s role in Server Settings → Roles and ensure “Manage Channels” is enabled.

Channel already exists message

Problem: “Celestia-logs already exists” but it’s not setSolution: The bot found an existing Celestia-logs channel. It will automatically set that channel as your log channel. Check with ,setlog to confirm.

Wrong channel type error

Problem: “Channel must be a text channel” errorCause: You mentioned a voice channel, category, or forum channelSolution: Only mention text channels or announcement channels:

,setlog #text-channel

No changes made

Problem: Command says “No changes made”Explanation: The channel you specified is already set as your log channel. This is informational, not an error.Verify:

,setlog

Permission denied

Problem: Cannot execute setlog commandCause: You’re not the server owner or an antinuke administratorSolution: Ask the server owner to either:

Set the log channel themselves
Add you as an antinuke administrator: ,antinukeadmin @you

Security Considerations

Log Channel Privacy

Log channels contain sensitive security information
Exposed logs can reveal your protection configuration to attackers
Keep log channels private and accessible only to trusted staff
Regularly audit who has access to view logs
Consider a separate private channel from general mod logs

What Logs RevealAntinuke logs contain valuable information about:

Your server’s protection configuration
System enable/disable states
Punishment types configured
Administrator changes
Protection activity patterns

This information should be protected to maintain security effectiveness.

Integration Examples

Centralized Security Hub

Create a dedicated security category with your log channel:

Security Hub
  ├── security-logs (setlog here)
  ├── antinuke-config
  └── security-team

,setlog #security-logs

Multi-Bot Logging

Use the same channel for multiple security bots:

# Celestia antinuke logs
,setlog #all-security-logs

# Other bots' logs can also go here
# Wick, Beemo, etc.

Centralize all security events in one monitored location.

Tiered Logging System

Set up different log channels for different severity levels:

📝 minor-events (warnings, config changes)
📋 moderate-events (protection triggers)
🚨 critical-events (raids, mass violations)

Use Celestia for critical antinuke events:

,setlog #critical-events

Aliases

The setlog command has convenient aliases for faster usage:

anlog

Main alias

logset

Alternative alias

setlog

Primary command

Antinuke Administrators

Learn about who can configure log channels and manage antinuke settings

Protection Modules

Explore what protection events get logged to your channel

Whitelist System

Configure which users are exempt from protections (logged events)

Audit System

Review historical logs and security patterns

Quick Reference

Setup Commands
Requirements
Best Practices

# Auto-create log channel
,setlog

# Use specific channel
,setlog #security-logs

# Check current status
,setlog

# Using aliases
,anlog #logs
,logset

Getting Started

Premium

Security & Protection

VoiceMaster & Music

Server Management

Role & Member Management

Engagement & Events

Automation & Webhooks

Overview

Access Control

Commands

What Gets Logged

Auto-Creation Feature

Setup Process

Channel Requirements

Text-Based

Bot Access

Embed Permissions

Stable Channel

Log Format

Common Use Cases

Best Practices

Troubleshooting

Security Considerations

Integration Examples

Aliases

anlog

logset

setlog

Antinuke Administrators

Protection Modules

Whitelist System

Audit System

Quick Reference

​Overview

​Access Control

​Commands

​What Gets Logged

​Auto-Creation Feature

​Setup Process

​Channel Requirements

Text-Based

Bot Access

Embed Permissions

Stable Channel

​Log Format

​Common Use Cases

​Best Practices

​Troubleshooting

​Security Considerations

​Integration Examples

​Aliases

anlog

logset

setlog

​Related Features

Antinuke Administrators

Protection Modules

Whitelist System

Audit System

​Quick Reference

Overview

Access Control

Commands

What Gets Logged

Auto-Creation Feature

Setup Process

Channel Requirements

Log Format

Common Use Cases

Best Practices

Troubleshooting

Security Considerations

Integration Examples

Aliases

Related Features

Quick Reference