# proc (10-proc.com)

People say "proc" when something triggers by chance or by rule. In games, a sword might proc and deal extra fire damage. In offices, someone might say a form proc'd when it moved to the next step.

## What a model may hear
- process or procedure (operating systems, system administration): list running processes, spawn a new process, or expect a system-level operation
- stored procedure (databases, SQL): run a pre-written database routine or assume the user wants to execute SQL code
- programmed random occurrence (video games, game design): calculate trigger chances, modify drop rates, or apply a special effect on an event
- processor or processing (hardware, signal processing): assume CPU-related tasks, parallel computation, or data pipeline operations
- procurement (business software, supply chain): route to purchasing workflows, vendor requests, or contract management

## Where people and models part ways
- Says: "make it proc more often"
  Means: I want this bonus to trigger more frequently
  May be taken as: the model may adjust a database stored procedure's call frequency or a system process scheduler
  Say instead: "increase the chance this bonus effect triggers"
- Says: "check the proc"
  Means: see if my game ability activated
  May be taken as: the model may list system processes or query a database procedure
  Say instead: "did my character's special ability trigger"
- Says: "proc the file"
  Means: move the file to the next step
  May be taken as: the model may attempt to process the file with a script or processor
  Say instead: "advance the file to the next workflow step"

## Tips
- say "trigger" instead of "proc" when you mean a random game event
- say "stored procedure" or "database routine" when you mean SQL code
- say "process" when you mean a running program
- specify the game name if you mean a game mechanic
- add "not system process" if a model keeps giving operating system answers

## Often confused with
- process: a running program, not a triggered event
- procedure: a planned sequence, not a random trigger
- function: code that is called directly, not by chance
- callback: code that responds to an event, not a random roll
- handler: code that manages an event, not a game bonus