HOLP: Difference between revisions
No edit summary |
m (added dates for references.) |
||
(8 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
{{stub}} | {{stub}} | ||
The '''HOLP''', short for '''Held Object's Last Position''', represents the coordinates at which the object [[Mario]] held last was last rendered. The HOLP is not reset when changing [[courses]] or files, but is reset to the origin ([0, 0, 0]) when starting the game. When released, objects are re-activated and placed at the HOLP, which is usually in front of [[Mario]]. However, if the object was not rendered while being held by Mario, the HOLP would not update during that time, so the object won't appear in front of Mario. | The HOLP Technique was originally created by Sonicwiifan<ref>[https://youtu.be/xX85HBa7tms?si=Qf8hShhwL-3MukoY Bob-omb Teleport Glitch | ||
31/12/2009]</ref> and Pannenkoek2012<ref>[https://youtu.be/seQ-IL-eNqk?si=iOYX1NbbfF6nhwFc SM64 - Hat Glitches (4/4) - Object Displacement Glitch 18/6/2013]</ref>. | |||
The '''HOLP''', short for '''Held Object's Last Position''', represents the coordinates at which the object [[Mario]] held last was last rendered. The HOLP is not reset when changing [[courses]] or files, but is reset to the origin ([0, 0, 0]) when starting the game. When released, objects are re-activated and placed at the HOLP, which is usually in front of [[Mario]]. However, if the object was not rendered while being held by Mario, the HOLP would not update during that time, so the object won't appear in front of Mario. A similar effect can be observed with the anchor point when executing a [[Chuckya Wrong Throw]]. | |||
The HOLP is specifically not updated when- | The HOLP is specifically not updated when- | ||
* The camera is 20,300 units away | *The camera is 20,300 units away | ||
* The camera is panned away from Mario | *The camera is panned away from Mario | ||
* With [[Hat | *With [[Hat in Hand]] (as the object doesn't load) | ||
* During [[Pause-Buffered Hitstun]] | *During [[Pause Buffering|Pause-Buffered Hitstun]] | ||
* Using [[Instant Release|instant release]] | *Using [[Instant Release|instant release]] | ||
* By changing a model to be blank using [[ | *Holding an object [[BCA| behind the camera]] | ||
*By changing a model to be blank using [[Object_Adoption#Spiny_Adoption|spiny adoption]] (cork box only, which doesn't occur in vanilla) | |||
==Effect on Objects== | ==Effect on Objects== | ||
Line 14: | Line 19: | ||
[[Category:Values]] | [[Category:Values]] | ||
<references /> |
Latest revision as of 16:04, 29 June 2024
The HOLP Technique was originally created by Sonicwiifan[1] and Pannenkoek2012[2].
The HOLP, short for Held Object's Last Position, represents the coordinates at which the object Mario held last was last rendered. The HOLP is not reset when changing courses or files, but is reset to the origin ([0, 0, 0]) when starting the game. When released, objects are re-activated and placed at the HOLP, which is usually in front of Mario. However, if the object was not rendered while being held by Mario, the HOLP would not update during that time, so the object won't appear in front of Mario. A similar effect can be observed with the anchor point when executing a Chuckya Wrong Throw.
The HOLP is specifically not updated when-
- The camera is 20,300 units away
- The camera is panned away from Mario
- With Hat in Hand (as the object doesn't load)
- During Pause-Buffered Hitstun
- Using instant release
- Holding an object behind the camera
- By changing a model to be blank using spiny adoption (cork box only, which doesn't occur in vanilla)
Effect on Objects
When an object is thrown, it will appear at the HOLP. When an object is dropped, it will appear at the HOLP laterally (i.e. share the HOLP's X and Z values) but will be at Mario's height (i.e. it will share his Y value). The exception to this is Bowser, who will always appear directly in front of Mario regardless of the HOLP.
- ↑ [https://youtu.be/xX85HBa7tms?si=Qf8hShhwL-3MukoY Bob-omb Teleport Glitch 31/12/2009]
- ↑ SM64 - Hat Glitches (4/4) - Object Displacement Glitch 18/6/2013