Discord Notes - Complete Doc

A comprehensive guide for using the notes functionality, including examples, edge cases, and common mistakes to avoid.

1. Creating Notes

Command: !new_note "title" content

✅ Correct Usage:

!new_note "Shopping List" Milk, eggs, bread
!new_note "Meeting Notes" Topics discussed: budget review, project timeline
!new_note "Single-Word-Title" My content here
!new_note "Grandma's pizza Recipe" 1. Mix ingredients\n2. Bake at 350°F\n3. Cool for 10 minutes

❌ Common Mistakes:

• !new_note Shopping List Milk, eggs (Missing quotes around title with space)

• !new_note (Missing both title and content)

• !new_note "My Title" (Missing content)

Important:

• Titles MUST be in quotes if they contain spaces

• Content can be as long as needed

• You can use basic formatting in content (new lines, emoji, etc.)

• Each note gets a unique numeric ID (starting from 1)

2. Viewing Notes

Command: !view_note <note_id>

✅ Correct Usage:

!view_note 1
!view_note 42

❌ Common Mistakes:

• !view_note (Missing note ID)

• !view_note "1" (Adding quotes around ID)

• !view_note shopping (Using title instead of ID)

Output Format:

📝 Title: Your Note Title
Content: Your note content here
Created: 2024-01-01 12:00:00
Last edited: 2024-01-01 12:00:00

3. Listing Notes

Command: !list_notes

Usage:

• Simply type !list_notes

• No additional parameters needed

• Shows all your notes in a clean, formatted list

Output Format:

📝 Your Notes
ID: 1 - Shopping List
Content: Milk, eggs, bread...

ID: 2 - Meeting Notes
Content: Topics discussed: budget...

Important:

• Long notes are truncated to first 100 characters with "..."

• Notes are ordered by ID

• Empty notes list will show "You don't have any notes!"

4. Editing Notes

Command: !edit_note <note_id> new content

✅ Correct Usage:

!edit_note 1 Updated shopping list: milk, bread, eggs, cheese
!edit_note 3 Line 1\nLine 2\nLine 3
!edit_note 5 Brief note

❌ Common Mistakes:

• !edit_note (Missing note ID and content)

• !edit_note 1 (Missing new content)

• !edit_note "1" new content (Quotes around ID)

Important:

• Cannot edit the title (create new note if title change needed)

• Entire content is replaced, not appended

• Last edited timestamp updates automatically

• Original creation date is preserved

5. Deleting Notes

Command: !delete_note <note_id>

✅ Correct Usage:

!delete_note 1
!delete_note 42

❌ Common Mistakes:

• !delete_note (Missing note ID)

• !delete_note "1" (Quotes around ID)

• !delete_note all (Cannot bulk delete)

Important:

• Deletion is permanent and cannot be undone

• Bot confirms successful deletion

• Note IDs are not reused or reassigned

• Deleting non-existent notes returns error

6. Searching Notes

Command: !search_notes <query>

✅ Correct Usage:

!search_notes grocery
!search_notes "project meeting"
!search_notes TODO
!search_notes 2024

Search Behavior:

• Searches both titles and content

• Case-insensitive (MILK = milk = Milk)

• Partial word matches work (searching "meet" finds "meeting")

• Multiple words are searched together

• Returns all matching notes

Output Format:

🔍 Search Results for 'query'
ID: 1 - Title: Meeting Notes
Content: Discussed project timeline...

ID: 3 - Title: Team Meeting
Content: Weekly sync about...

Advanced Tips & Features

Best Practices for Note Organization

Consistent Titling:

• Use prefixes for related notes (e.g., "Project: Task 1", "Project: Task 2")

• Add dates to time-sensitive notes (e.g., "Meeting 2024-01-01")

• Use descriptive titles for easy searching

Content Structure:

• Use line breaks (\n) for better readability

• Put important information at the start (shown in list view)

• Use emojis for visual organization (📅, 📝, ⚠️, etc.)

Command Combinations

• Search before editing to find the right note ID

• List notes before deleting to verify ID

• View note before editing to confirm content

Error Recovery

If you encounter errors:

• Check note ID exists (!list_notes)

• Verify command syntax (!help <command>)

• Ensure you're the note owner

• Try operation again

Quick Reference Table

Getting Help

• Use !help <command> for quick command reference

• Errors include helpful messages explaining what went wrong

• Commands can be used in any text channel where the bot is present