How abrasic/blendpresence works
Project type and purpose
• This is a Blender add-on (written in Python) that integrates with Discord via Rich Presence.
• Its purpose is to capture Blender context (mode, scene name, render stats, etc.) and push updates to a user’s Discord status.
File structure
• Top-level:
• BlendPresence/ ← the Blender add-on package
• LICENSE, README.md ← documentation and license
• Inside BlendPresence/
• __init__.py ← Blender add-on registration (bl_info) and entry points
• pypresence/ ← vendored Discord RPC client library
– baseclient.py
– client.py
– exceptions.py
– payloads.py
– presence.py
– utils.py
• No separate “frontend/backend”—this is a single plugin running inside Blender’s Python environment.
README for additional insights
• Configuration surface: add-on preferences in Blender’s UI.
• Dependencies: Blender 2.93+, Discord desktop client (for IPC), pypresence (vendored).
Main components & interactions
a. Components
1. Blender Host
• UI Panel & Preferences (Blender’s addon settings)
• Event hooks & timers (frame change, render start/stop)
2. Data Collector
• Reads bpy.context for version, mode, scene, object counts, render progress
• Reads user preferences (buttons, update interval, custom text)
3. Payload Builder
• Assembles JSON payloads (using payloads.py, presence.py)
4. RPC Client (pypresence)
• client.py handles high-level commands (connect, update_presence, close)
• baseclient.py handles low-level IPC socket framing
5. External Service
• Discord Desktop App listening on IPC socket
• Discord GUI displaying the Rich Presence
b. Relationships/Data Flow
• User updates settings in Blender UI → Preferences stored in Blender
• On timer or event, Data Collector polls Blender context → passes to Payload Builder
• Payload Builder invokes RPC Client → serializes & sends over IPC → Discord
• Discord processes JSON, updates user status → Friends see updated presence
c. Architectural patterns
• Plugin/extension pattern (hosted inside Blender)
• Event-driven updates via Blender handlers
• Adapter pattern wrapping pypresence into Blender’s API
• Separation of concerns: UI vs context-gathering vs communication
d. Key technologies
• Blender Python API (bpy)
• pypresence library (vendored)
• Discord IPC protocol (local UNIX/Windows socket)
• JSON payloads conforming to Discord Rich Presence schema