XNotify

XNotify is the Xbox 360 on-screen notification system used for sign-in prompts, achievements, storage warnings, party/chat events, and other shell-level status messages.

XeCLI exposes XNotify through the rgh notify, rgh notify-icons, and rgh jrpc2 notify commands so you can send operator messages directly to the console without opening a separate tool.

At the practical level, every XNotify workflow comes down to three inputs:

• message text
• icon/logo identifier
• a healthy notification-capable JRPC/XDRPC path on the console

What XeCLI Supports

XeCLI supports:

• direct message sends with a numeric icon ID
• direct message sends with a built-in icon name
• reusable icon presets for operator shortcuts
• the same icon mapping through both notify and jrpc2 notify

Examples:

rgh notify "XeCLI connected"
rgh notify "XeCLI connected" 14
rgh notify --message "XeCLI connected" --logo 14
rgh notify --message "Build finished" --icon success
rgh jrpc2 notify "Module load complete" 27
rgh notify-icons list
rgh notify-icons add --name success --logo 14

Representative output:

SUCCESS Notification sent
message="XeCLI connected" logo=14 (Flashing happy face)

Why XNotify Matters

In real RGH/JTAG workflows, XNotify is useful for:

• confirming that a long-running action finished while you are looking at the console
• validating that JRPC2 is alive and responding
• confirming trainer, module, save, or plugin operations without manually checking files first
• building custom tooling that gives visible operator feedback during scripted workflows

What XNotify Actually Is

XNotify is the shell popup system built into the Xbox 360 dashboard environment.

It is the same notification family used for:

• sign-in and sign-out messages
• achievement and avatar award toasts
• storage and controller warnings
• party/chat prompts
• download and update notices

That is why the icon list contains shell-event names instead of generic app icons. XeCLI is not inventing a new notification framework. It is exposing the console’s existing one in a terminal-friendly way.

Command Surface

rgh notify

Operator-facing notification command.

Examples:

rgh notify "XeCLI connected"
rgh notify "XeCLI connected" 14
rgh notify --message "XeCLI connected" --logo 14
rgh notify --message "Upload complete" --icon success

Notes:

• the second positional argument can be a numeric icon ID
• --logo accepts decimal or 0x hex
• --icon resolves a named preset from your local config
• if no icon is provided, XeCLI uses its default notification path

rgh notify-icons list

Shows the built-in icon catalog and any saved presets.

Examples:

rgh notify-icons list
rgh notify-icons list --json

rgh notify-icons show

Resolves one icon by name or number.

Examples:

rgh notify-icons show 14
rgh notify-icons show achievement
rgh notify-icons show avatar-award

rgh notify-icons add

Creates a reusable local alias.

Examples:

rgh notify-icons add --name success --logo 14
rgh notify-icons add --name achievement --logo 27
rgh notify-icons add --name avatar --logo 60

rgh notify-icons remove

Removes a saved alias.

Examples:

rgh notify-icons remove --name success

rgh jrpc2 notify

Lower-level JRPC2-backed notification send. Use this if you want to stay inside the jrpc2 namespace for scripting or RPC-focused workflows.

Examples:

rgh jrpc2 notify "XeCLI connected"
rgh jrpc2 notify "XeCLI connected" 14

Numeric Icon Usage

The most direct form is:

rgh notify "XeCLI connected" 14

That means:

• message text = XeCLI connected
• logo/icon id = 14

This is the fastest operator form when you already know the ID you want.

Direct RPC Usage Notes

If you are building tooling outside XeCLI, the lower-level shape is still:

• message text
• icon/logo ID
• dispatch through the console notification RPC path

XeCLI already normalizes the useful operator forms:

rgh notify "XeCLI connected" 14
rgh jrpc2 notify "XeCLI connected" 14
rgh notify --message "XeCLI connected" --logo 14

That keeps users away from raw command framing while still matching the way other JRPC/XDRPC-capable tools think about XNotify.

Built-In Icon Reference

Common operator-friendly icons:

Broader built-in catalog:

Suggested Operator Patterns

Use a small predictable icon set instead of choosing a random logo each time.

Recommended mapping:

• 14 for success
• 15 for failure
• 12 or 55 for transfer/download events
• 16 for patch/tool actions
• 27 for major completion milestones
• 42 for plain-text messages when you want the icon hidden

Examples:

rgh notify "Save upload complete" 14
rgh notify "Transfer failed" 15
rgh notify "Downloading title update" 12
rgh notify "Patch applied" 16
rgh notify "Decompile finished" 27

Direct Integration Notes

XeCLI is a command-line wrapper around the same practical workflow you would use in another JRPC/XDRPC-capable tool: send message text plus a numeric icon ID to the console’s notification path.

If you are building your own tool:

• keep the icon ID mapping local so your UI can show readable names
• expose both numeric and named icon selection
• use visible completion/failure notifications for long-running actions
• do not assume every console/plugin stack has the same RPC health

The important practical contract is:

• message text
• icon/logo ID
• working JRPC2/XDRPC-style notification call path

Troubleshooting

If notifications do not appear:

• confirm JRPC2 is loaded and healthy
• confirm your console is signed into a shell/session where notifications are visible
• test with a simple known icon first, such as 14
• test the lower-level path directly with rgh jrpc2 notify

Useful checks:

rgh notify "XeCLI connected" 14
rgh jrpc2 notify "XeCLI connected" 14
rgh notify-icons show 14
rgh notify-icons list