Difference between revisions of "Proc"

ADVERTISEMENT
From Diablo Wiki
Jump to: navigation, search
m
Line 1: Line 1:
'''Proc''' is an acronym that refers a [[skill]] or [[item]] effect being activated when there is a percentage chance of activation. If a [[skill]] effect in the game has a chance to happen on a melee hit, then the percentage chance is the "proc rate".
+
'''Proc''' is a term that refers a [[skill]], [[item]], or other effect that is activated automatically, usually on some percentage chance. If a [[skill]] effect in the game has a chance to happen on a melee hit, then the percentage chance is the "proc rate".
  
 +
Procs are widely used in World of Warcraft skills,[http://www.wowwiki.com/Proc] which no doubt influenced the Diablo III developers in their design.
  
==Examples==
+
* See more [[Reference]] terms.
If a [[Barbarian]] has invested skill points into [[Berserker State]], the spell has a 6% "proc chance" when fighting enemies. This means there is a 6% chance the skill's active component will activate.
+
 
 +
 
 +
==Procs in Diablo III==
 +
 
 +
Procs are present in many game functions, though they may not be referred to as "procs" by the developers. For instance, functions like [[Critical Hit]]s are procs, as they trigger a special effect some set % of the time. 
 +
 
 +
 
 +
The only (so far) known skill that works as a proc in Diablo III is the [[Barbarian]]'s [[Revenge]] skill, which was described as a "proc" by [[@Diablo]] in March 2011. [http://twitter.com/Diablo/statuses/48845117712367616]
 +
 
 +
<blue>No it's a skill, it's a proc, which isn't quite the same as a passive.</blue>
  
This is also true on [[item]]s, where there is a chance of an effect going off on hit, and can also relate to spell casts, being hit, scoring a [[Critical Hit]], [[Dodge]] or any other event in the game.
 
  
  
Line 15: Line 24:
 
When developers and players were talking about "special procedures" it was abbreviated to "proc". It evolved to a verb ("proced", "proc'd" or "procced"), indicating the procedure was activated.
 
When developers and players were talking about "special procedures" it was abbreviated to "proc". It evolved to a verb ("proced", "proc'd" or "procced"), indicating the procedure was activated.
  
 +
 +
===Origin Explanation===
 +
 +
Old time RPG developer [http://www.raphkoster.com/ Raph Koster]'s explanation:
 +
 +
::Short for spec_proc (special procedure), which is a bit of code triggered to cover a special case that the default code doesn’t handle.
 +
 +
::In the older muds there was almost no variation between what a given object could do. For example all weapons used the weapon type, then you could specify damage type (was it a sword or a mace), damage ranges, and so on.
 +
 +
::To get the weapon to do anything special, you had limited choices. Depending on the architecture, you could attach a spell to be cast, or could attach a script if the code supported it. In the codebases that Brad & co. played, the devs could not script, so the codebase allowed a pointer to a special hardcoded procedure to be entered in the weapon data.
 +
 +
::“Proc” is almost entirely [[Everquest]] slang... Even in the muds, it wasn’t that widely used because only some codebases used the term. It took EQ publicizing the inherited term to make it common knowledge.
 +
 +
 +
==References==
 +
 +
* [http://www.wowwiki.com/Proc Procs on World of Warcraft].
 +
* [http://www.nerfbat.com/2006/04/15/what-is-a-proc/ What is a Proc?
  
  
Line 21: Line 48:
 
[[Category:Glossary]]
 
[[Category:Glossary]]
 
[[Category:Abbreviations]]
 
[[Category:Abbreviations]]
 +
[[category:reference]]

Revision as of 11:53, 19 March 2011

Proc is a term that refers a skill, item, or other effect that is activated automatically, usually on some percentage chance. If a skill effect in the game has a chance to happen on a melee hit, then the percentage chance is the "proc rate".

Procs are widely used in World of Warcraft skills,[1] which no doubt influenced the Diablo III developers in their design.


Procs in Diablo III

Procs are present in many game functions, though they may not be referred to as "procs" by the developers. For instance, functions like Critical Hits are procs, as they trigger a special effect some set % of the time.


The only (so far) known skill that works as a proc in Diablo III is the Barbarian's Revenge skill, which was described as a "proc" by @Diablo in March 2011. [2]

No it's a skill, it's a proc, which isn't quite the same as a passive.


Background

The term "proc" is a programming term that refers to an event triggered under particular circumstances, or being "processed".

Proc is also sometimes short for "spec_proc" ("special procedure"), used by the original programmer of Circle-MUD, Jeremy Elson and possibly the original programmers of diku-MUD as well. These "special procedures" are functions assigned to objects, players, and locations to invoke a "special procedure" when a specific event occurs. These were used in a variety of ways in Circle-MUD, and might have originated the term.

When developers and players were talking about "special procedures" it was abbreviated to "proc". It evolved to a verb ("proced", "proc'd" or "procced"), indicating the procedure was activated.


Origin Explanation

Old time RPG developer Raph Koster's explanation:

Short for spec_proc (special procedure), which is a bit of code triggered to cover a special case that the default code doesn’t handle.
In the older muds there was almost no variation between what a given object could do. For example all weapons used the weapon type, then you could specify damage type (was it a sword or a mace), damage ranges, and so on.
To get the weapon to do anything special, you had limited choices. Depending on the architecture, you could attach a spell to be cast, or could attach a script if the code supported it. In the codebases that Brad & co. played, the devs could not script, so the codebase allowed a pointer to a special hardcoded procedure to be entered in the weapon data.
“Proc” is almost entirely Everquest slang... Even in the muds, it wasn’t that widely used because only some codebases used the term. It took EQ publicizing the inherited term to make it common knowledge.


References