--- id: plugin.expression-interaction title: Expression Interaction scope: plugins status: active priority: 10 visibility: user category: Plugin tags: plugin, expression-interaction generated: true editable: false updated_at: "2026-06-25T12:06:11.231Z" --- # Expression Interaction Express yourself through interactions with other users, such as hugging, bonking, comforting, etc ## Metadata Plugin ID: expression-interaction Version: 0.2.0 Default state: enabled ## Web Routes - /plugins/expression-interaction - GET /plugins/expression-interaction - POST /plugins/expression-interaction/settings - POST /plugins/expression-interaction/actions/create - POST /plugins/expression-interaction/actions/:id/update - POST /plugins/expression-interaction/actions/:id/toggle - POST /plugins/expression-interaction/actions/:id/archive - POST /plugins/expression-interaction/actions/:id/restore ## Route Reference ### MOUNT /plugins/expression-interaction - Purpose: Mounts the plugin router at this base WebUI path. - Inputs: No request parameters detected by static analysis. - Response format: Plugin router mount point. - Access: Access is controlled by the mount options and individual plugin routes. - Side effects: No direct route action; child routes handle requests. - Limits/notes: Mount metadata is inferred from static source scanning. ### GET /plugins/expression-interaction - Purpose: Renders or serves the expression-interaction plugin page. - Inputs: No request parameters detected by static analysis. - Response format: HTML page rendered from an EJS view - Access: admin access expected; logged-in session required or used - Side effects: Usually read-only. - Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. ### POST /plugins/expression-interaction/settings - Purpose: Processes the expression-interaction plugin action for settings. - Inputs: body: full submitted body is passed to a helper; exact fields are defined by the matching form/service - Response format: HTTP redirect after handling the request - Access: admin access expected; logged-in session required or used - Side effects: writes or mutates server-side state - Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Most non-API POST routes are browser form submissions and usually redirect after completion. ### POST /plugins/expression-interaction/actions/create - Purpose: Processes the expression-interaction plugin action for actions create. - Inputs: body: full submitted body is passed to a helper; exact fields are defined by the matching form/service - Response format: HTTP redirect after handling the request - Access: admin access expected; logged-in session required or used - Side effects: writes or mutates server-side state - Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Most non-API POST routes are browser form submissions and usually redirect after completion. ### POST /plugins/expression-interaction/actions/:id/update - Purpose: Processes the expression-interaction plugin action for actions id update. - Inputs: path params: `id`; body: full submitted body is passed to a helper; exact fields are defined by the matching form/service - Response format: HTTP redirect after handling the request - Access: admin access expected; logged-in session required or used - Side effects: writes or mutates server-side state - Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Most non-API POST routes are browser form submissions and usually redirect after completion. ### POST /plugins/expression-interaction/actions/:id/toggle - Purpose: Processes the expression-interaction plugin action for actions id toggle. - Inputs: path params: `id` - Response format: HTTP redirect after handling the request - Access: admin access expected; logged-in session required or used - Side effects: Action route; side effects were not detected statically. - Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Most non-API POST routes are browser form submissions and usually redirect after completion. ### POST /plugins/expression-interaction/actions/:id/archive - Purpose: Processes the expression-interaction plugin action for actions id archive. - Inputs: path params: `id` - Response format: HTTP redirect after handling the request - Access: admin access expected; logged-in session required or used - Side effects: writes or mutates server-side state - Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Most non-API POST routes are browser form submissions and usually redirect after completion. ### POST /plugins/expression-interaction/actions/:id/restore - Purpose: Processes the expression-interaction plugin action for actions id restore. - Inputs: path params: `id` - Response format: HTTP redirect after handling the request - Access: admin access expected; logged-in session required or used - Side effects: writes or mutates server-side state - Limits/notes: Generated from static route source analysis; confirm exact behavior in the handler before changing integrations. Most non-API POST routes are browser form submissions and usually redirect after completion. ## Commands - No plugin command triggers detected. ## Source Plugin folder: plugins/expression-interaction