Kill Process Action
Automatically terminate running system processes when alerts trigger. Useful for ending programs, stopping services, or creating interactive "chaos" effects where viewers can close applications.
What You Need
- Administrator privileges (recommended for killing most processes)
- Knowledge of process names you want to terminate
- TipLink running with appropriate permissions
Quick Start
- Create or edit an alert
- Add the Kill Process action
- Select process(es) from the dropdown
- Save and test
Configuration interface screenshot will be added here.
Killing system processes can crash applications, lose unsaved work, or make your system unstable. Always save your work before testing. Never kill critical system processes (explorer.exe, svchost.exe, etc.).
Configuration Options
Process Selection
Select Process
- Dropdown of currently running processes
- Can select multiple processes
- All selected processes will be terminated simultaneously
- Process list refreshes when you open the dropdown
Process names shown are the executable names (e.g., notepad.exe, chrome.exe, Discord.exe). The list only shows processes currently running when you open the dropdown.
Setup Guide
Basic Setup
-
Identify Target Process
- Open Task Manager (Ctrl+Shift+Esc)
- Go to "Details" tab
- Find the process name (e.g.,
notepad.exe) - Note the exact name including
.exe
-
Create Alert
- Navigate to Alerts section
- Create or edit an alert
- Set appropriate trigger conditions
-
Add Kill Process Action
- In Actions section, click "Add Action"
- Select "Kill a System Process"
-
Select Process
- Start the target application first
- Open the process dropdown
- Find and select your target process(es)
- Save
-
Test Carefully
- Save all work in target application
- Trigger the alert
- Verify process terminates
Multiple Process Setup
To kill several applications at once:
- Start all target applications
- Open process dropdown
- Hold Ctrl and click each process
- All selected processes terminate together
Permission Setup
For killing protected processes:
-
Run TipLink as Administrator
- Right-click TipLink
- Select "Run as administrator"
- May need to do this every time
-
Create shortcut (optional)
- Right-click TipLink shortcut
- Properties → Advanced
- Check "Run as administrator"
- Apply
Running TipLink as administrator allows it to kill more processes but also gives it elevated permissions. Only do this if you understand the security implications.
Common Use Cases
Close Notepad
- Great for testing/demos
- Process:
notepad.exe - Safe to test repeatedly
End Game
- "Close my game for $50" channel point reward
- Process: Your game's exe (e.g.,
game.exe) - Set high cost to prevent spam
Discord Chaos
- Viewers can close your Discord
- Process:
Discord.exeorDiscordCanary.exe - Use with cooldown to prevent abuse
Browser Tab Reset
- Kill and restart browser
- Process:
chrome.exe,firefox.exe, ormsedge.exe - Combine with another action to relaunch
Stop Music Player
- End media playback
- Process:
spotify.exe,vlc.exe, etc. - Good for "skip song" interactions
Close OBS (not recommended during stream!)
- Process:
obs64.exe - Only use for testing offline
- Will end your stream instantly
Troubleshooting
Process not in dropdown
- Make sure the application is running first
- Refresh dropdown by closing and reopening it
- Check Task Manager to verify process is running
- Some processes may have different names than the application
Action triggers but process doesn't close
- TipLink may need administrator privileges
- Process may be protected by OS
- Multiple instances may exist (only one gets killed)
- Check TipLink logs for error messages
Wrong process closes
- Multiple programs may share process names
- Verify exact process name in Task Manager
- Check for multiple instances
- Consider using more specific targeting
Permission denied errors
- Run TipLink as administrator
- Some system processes cannot be killed
- Security software may block termination
Process closes but immediately restarts
- Application has auto-restart enabled
- Windows may restart critical system processes
- Parent process may respawn child processes
Safety & Best Practices
- Never kill: explorer.exe, svchost.exe, csrss.exe, winlogon.exe, or other system processes
- Save all work before testing
- Use cooldowns to prevent spam/abuse
- Test offline before using live
- Warn viewers about what can be killed
- Have backup plans if something goes wrong
Safe Processes to Kill (for testing):
- ✅ notepad.exe
- ✅ calc.exe
- ✅ mspaint.exe
- ✅ Discord.exe (if you're willing to restart it)
- ✅ Your own games/applications
Dangerous Processes (avoid):
- ❌ explorer.exe (Windows shell - kills taskbar/desktop)
- ❌ svchost.exe (system services)
- ❌ obs64.exe (will end your stream)
- ❌ TipLink.exe (will close TipLink itself)
- ❌ Any process you don't recognize
Recommended Settings:
- Use high cost channel point rewards
- Enable cooldowns (30-60 seconds minimum)
- Set user-level limits (once per user per hour)
- Use rate limiting on alerts
- Have recovery plan for critical processes
Testing Checklist:
- ✅ Save all work before testing
- ✅ Test with safe processes first (notepad.exe)
- ✅ Verify correct process closes
- ✅ Test cooldown/rate limit works
- ✅ Have recovery method ready
- ✅ Test as non-admin and admin
- ✅ Document which processes you're using
Technical Reference
Process Termination:
- Uses Windows API
TerminateProcess - Forceful termination (not graceful shutdown)
- No save prompts (data may be lost)
- Exit code: 1
Process Selection:
- Lists processes visible to current user
- Elevated processes require admin rights
- Process list snapshot taken when dropdown opens
- Multiple instances of same process may exist
Limitations:
- Cannot kill protected system processes
- Cannot kill processes owned by other users (without admin)
- Some services auto-restart after termination
- May be blocked by antivirus/security software
Permissions:
- Standard user: Can kill own processes
- Administrator: Can kill most processes
- System processes: Usually protected even from admin
Error Handling:
- Logs errors to TipLink console
- Fails silently if permission denied
- No retry logic (one attempt per trigger)
Performance:
- Instant termination attempt
- No cleanup or graceful shutdown
- Does not wait for process to exit
- Multiple processes killed in parallel
Process Naming:
- Case-insensitive matching
- Must include
.exeextension - Matches exact process name only
- First matching process is terminated (if multiple exist)