Hi!

Castle Grounds

2026-06-11T09:12:02Z

Oyion gaming:

Castle Grounds

2026-06-11T09:10:43Z

Oyion gaming: Added

The castle grounds is the main starting point of the game and serves as the exterior of the castle.

== The Moat ==
The moat surrounds the castle when you first start the game. Go to the [[basement]] and go right of [[Hazy Maze Cave]], you will find a puzzle. To solve it, you need to ground pound both pillars. the water will start draining. Once you go back outside, you will see that the water from the moat is gone! This is required for the vanish cap.
== Secrets ==
There's a hangable ceiling under the bridge but the bridge is so high you would need to use a [[Backwards Long Jump]]. There's a cannon that can launch you up to the castle roof but if you use a really tricky triple jump at the corner of it you can get on there.

Castle Grounds

2026-06-11T09:03:02Z

Oyion gaming:

2024-12-08T23:20:15Z

Oyion gaming: /* Throwing */Idk

{{object_infobox_2
|title= Chuckya
|image= STROOP- Chuckya.png|100×100px|A chuckya
|group= General Actor
|group2= Common 0
|modelID= 0xDF
|tangibility=1000
|draw=
|gravity=4
|friction=10
|buoyancy=2
|interaction=Grabbable
|damage=
|health=
|radius=150
|height=100
|hurtbox_radius=
|hurtbox_height=
|offset=
|coins=5
|behaviorScript=[https://github.com/n64decomp/sm64/blob/master/data/behavior_data.c#L662 Chuckya Initialization Code]
|behaviorCode=[https://github.com/n64decomp/sm64/blob/master/src/game/behaviors/chuckya.inc.c Chuckya behavior file]
}}
'''Chuckyas''' are purple enemies. They try to pick up Mario, and after doing so, spin around and then throw him. They do not directly damage Mario, but can throw him into the death barrier or cause fall damage if they throw him off a ledge. Mario can defeat them by picking them up and throwing them onto the ground.

==Locations==
The following courses have Chuckyas:

*[[Wet-Dry World]]
*[[Tall, Tall Mountain]]
*[[Tiny-Huge Island]]
*[[Rainbow Ride]]
*[[Bowser in the Sky]]

== Escaping Chuckya ==
When Chuckya grabs Mario a counter is initialized that lets Mario escape from Chuckya if it reaches 11. The counter starts at zero, and increases by one every time the player presses the A button or moves the joystick from the inside to the outside of its radius.<ref>[https://youtu.be/_R8c70zuJSw "Escaping from Chuckya's Grasp" by UncommentatedPannen]</ref> This is possible to do 1.5 times per frame with [[pause buffering]].

== Behavior ==
=== Moving ===
Through all movement, Chuckya accelerates at a rate of 4 units/f2 up to a maximum of 30 units/f and slows down at the same rate. Chuckya's movement is composed of three different steps, which loop over and over again:
# Chuckya turns towards Mario in increment of maximum 1024 angular units until he is less than 4096 horizontal angular units in front of him or for 41 frames, whichever happens first
#* Even if Mario is already within 4096 angular units, Chuckya will turn for at least one frame toward Mario and will stop early if it reaches exactly 0 angular units
# If Mario is in less than 2000 units laterally from Chuckya's home, Chuckya will chase forwards until Mario is behind a line perpendicular to Chuckya's forward direction
#* If Mario is more than 2000 units away from the home, Chuckya will turn back and move toward its home, modifying its speed until it reaches 10 speed, until it is within 500 units laterally, afterwhich it will instantly stop and wait for Mario to be within 1900 units of the home to turn again
# Chuckya will stop for 48 frames

Due to the way the engine functions, Chuckya's position will not be updated if Mario is more than 4000 units away from it, but its angle and speed will still update

This behavior is exploited in the [[A Button Challenge]] to have Chuckya drop at the start of the stage in Bowser in the Sky<ref>[https://www.youtube.com/watch?v=opnLYxrVWMc "The Chuckya Drop" by UncommentatedPannen]</ref>

=== Throwing ===
When Chuckya grabs Mario, a random number between 10 and 40 is generated to serve as a timer. Every frame, Chuckya will rotate by 2048 horizontal angular units counterclockwise and the timer is decreased by 1. If Mario does not escape, he will be thrown when the timer is less than 0 and one of the following conditions is met:
* There is a floor no more than 50 units below a point 150 units in front of Chuckya
* The timer reaches -17

Once one of those conditions is met, Chuckya will throw Mario at its anchor point (Similar to Mario's [[HOLP]]). This anchor point is only updated when Chuckya is rendered, which opens itself to [[Chuckya Wrong Throw]]. If Chuckya throws you underwater you will be warped up

== References ==
<references />

{{objects}}
[[Category:Enemies]]
[[Category:Objects]]

Crash

2024-12-08T23:09:37Z

Oyion gaming: /* CPU Crashes */Idk

A '''Crash''', '''Freeze''', or '''Hardlock''' is when the [[Threads#Game Thread|game thread]] of SM64 stops executing instructions (as opposed to a [[Softlock|softlock]], where the game is still running as normal but is stuck in a loop without any way to get out). Crashes can occur in several different ways, such as a game thread exception or an [[RCP]] (graphics) crash.
==CPU Crashes==
{| class="wikitable sortable"
! Cause !! Exception Type !! Notes
|-
| Exceed the [[Objects#Object limit|object limit]] || style="background-color: #ffb65e"| N/A || This is technically not a crash as the game developers accounted for this scenario and made the game enter an infinite loop. However, this infinite loop has the same symptoms as a crash and is one for all practical purposes, so it is included here. This "crash" can be done via a variety of methods including cloning, hat duplication, monty-mole pellet build-up, or money-bag duplication.
|-
| Sending the camera into a [[Parallel Universe|PU]]|| style="background-color: #ff9696" | Floating-Point Overflow ||
|-
| Walking at PU speed for only a portion of the 4 quarter steps on a [[frame]] || style="background-color: #ff9696"| Floating-Point Overflow ||
|-
| Moving at PU speed with no joystick input for all 4 quarter steps on a frame || style="background-color: #ff9696"| Floating-Point Overflow ||
|-
| Moving 16384 distance into a wall (Often a PU Crash) || style="background-color: #ff9696"| Floating-Point Overflow ||
|-
| Walking with a speed greater than or equal to 2^31 / 170 (~12.632M) || style="background-color: #ff9696"| Floating-Point Overflow || Mario's speed is multiplied by 170 in some intermediate calculations and casted to an int. When this cast exceeds 2^31 an FPE occurs.
|-
| Turning during a walking action such that speed times change in yaw is greater than or equal to 2^31 * 12 (~12.583M with dyaw = 2048) || style="background-color: #ff9696"| Floating-Point Overflow || Similar to the above.
|-
| Bully Knockback Division-by-Zero || style="background-color: #ff9696"| Floating-Point Division-by-Zero || By positioning Mario at the exact same X and Z coordinates as the bully, a division-by-zero exception occurs when the game divides by the lateral distance between Mario and the bully to calculate Mario and the bully's new speed after the collision.<ref>[https://www.youtube.com/watch?v=8jd3A2euOjg "Game Crash from Bully Knockback DIV/0" by UncommentatedPannen]</ref>
|-
| Bully/Bob-omb Angle Overflow || style="background-color: #ff9696"| Floating-Point Overflow || When a Bully or Bob-omb is out-of-bounds, the code to keep their angle between -32768 and 32767 doesn't run, and eventually it becomes big enough that a floating-point overflow exception occurs when casted back to an int.<ref>[https://www.youtube.com/watch?v=ZrMxO1eZPGU "Game Crash from Bully Angle Double-to-Int Conversion" by UncommentatedPannen]</ref><ref>[https://www.youtube.com/watch?v=kwQu5qQg-M0 "Game Crash from Bob-omb Angle Double-to-Int Conversion" by UncommentatedPannen]</ref>
|-
| Deleting a non-existent file on the File Select Screen<ref>[https://youtu.be/-N5OQPgA6YI "How to crash Super Mario 64 in 20 seconds" by rattleman123456]</ref> || style="background-color: #fffca8"| Address Error || The game tries to find the button object corresponding to the file and set its state to erased. However, the button object doesn't exist (a New File button is there instead), so it ends up trying to write to NULL
In different versions like the new switch version it could not crash instead say file 9 has been deleted.
|-
| Moving a shadow above [[surface]] 12 while it's over OOB || style="background-color: #fffca8"| Address Error || The surface SURFACE_INTANGIBLE (surface 12) has the special property that in some cases find_floor will look for floors below an intangible surface if it finds one. If there's no floor below the intangible surface, find_floor will return NULL for the found floor but the height of the intangible floor. As floors are null-checked by checking if their height is the default value of -11000, this will cause a NULL dereference the next time the game tries to use the floor variable.
|-
| Killing a Monty Mole remotely || style="background-color: #fffca8"| Address Error || The game tries to find which hole the Monty Mole should spawn in, but all the available holes are too far away from Mario, so no hole is chosen and the Monty Mole tries to go to a null hole.<ref>[https://www.youtube.com/watch?v=P4AQ9AmWa9s "Long Range Monty Mole Kill Game Crash" by UncommentatedPannen]</ref>
|-
| Killing an uninitialized Monty Mole<ref>[https://www.youtube.com/watch?v=aafLNwyR5kk "Uninitialized Monty Moles" by UncommentatedPannen]</ref> || style="background-color: #fffca8"| Address Error || Similar to above.
|-
| Going out of bounds in a room with a painting || style="background-color: #fffca8"| Address Error || Paintings use the floor type of Mario's floor to decide how they should ripple. Going out-of-bounds causes them to try to read the floor type of null.
|-
| Being pushed off of a hangable [[ceiling]] while hanging and stationary without another ceiling above || style="background-color: #fffca8"| Address Error || The game has a check to make Mario enter freefall if the ceiling above him is not hangable. The programmers failed to account for the ceiling being NULL, so if Mario is pushed off the ceiling and has no ceiling above him the game will try to read the type of a null ceiling and crash.
|-
| Sound glitch || Unknown || "Sound glitch" refers to when the audio thread encounters an exception (usually an address error exception), therefore causing the sound to cut out. When the game thread next tries to interface with the audio thread on a level load, the game thread crashes as well. Sound glitch is often treated as one singular glitch even though it is really a class of glitches in the audio library. Sound glitches are usually J-exclusive, however some instances such as the [[BitS]] sound glitch are not.
|-
| Teleporting while passing over a loading zone || style="background-color: #fffca8"| Address Error || Since the area changed, there is now no teleporter with the same ID as the one Mario used to warp. Thus the game returns NULL when trying to find an associated warp node to warp to, and crashes when trying to access information about its destination. Under certain conditions, this can cause a Wrong Warp on PAL or Shindou VC.
|-
| Warping out of a level while passing over a loading zone || style="background-color: #fffca8"| Address Error || Similar to above, but only hypothetical. Maybe possible in DDD using the Sub Gate warp and whirlpool cloning to reach the instant loading zone, but not yet achieved without hacks.
|-
| Entering Wiggler's Cave on the Disk Drive version || style="background-color: #ff9696"| Floating-Point Unimplemented Operation || When Wiggler is initialized, his health value is 2048 for a single frame before being reset to 4. Wiggler uses his health to index into a table to get his speed (to move faster when at lower health); 2048 causes it to index out of range and read a denormalized floating-point number as his health, which causes an unimplemented operation exception since the N64 does not implement any operations on denormalized floats except comparisons.
|-
| Having an object too far away from the camera make a noise (JP only)
| style="background-color: #ff9696" | Floating-Point Unimplemented Operation
|When a noise's pan is determined, it uses the position of the object to calculate the pan. When the object's absolute z-position relative to the camera is large (>= 22000 units) and the x-position relative to the camera is very negative (< -66000), an index for the pan will be generated outside of the bounds of the array for the pan. When the value outside of the array is an invalid float, the audio thread will crash (sound glitch). Does not happen when sound mode is set to Mono.
|-
|Casting a shadow on a corrupted triangle
| style="background-color: #ff9696" | Floating-Point Unimplemented Operation
|The limit of surface triangle loaded at once in the game is 2300. However, in [[Hazy Maze Cave]], when using [[Mario's Platform Adventure]], it is possible to load more triangle than this limit. This causes the surfaceList to overwrite part of the face table. If the game tries to cast a shadow on one of the "triangles" created by this situation, the normalX of the triangle will be a pointer and be processed as a denormalized float, which crashes the game when used for arithmethic.<ref>[https://www.twitch.tv/videos/1951116583?t=00h48m42s HMC Denorm Crash]</ref>
|-
|Having the same position as the camera's position || style="background-color: #ff9696" |Floating-Point Division-by-Zero||When Mario stands in the same position as the camera, the game will crash due to a division by zero error.<ref>[https://www.youtube.com/watch?v=vK16L2J0la4 "Faster fastest crash in BoB" by Madghostkek]</ref>
|-
|Rotating a Pendulum using pendulum manipulation beyond the float angle limit.
| style="background-color: #ff9696" |Floating-Point Overflow
|Manipulating the pendulum to rotate beyond the range of an int will error when truncating the float. Verification of this crash took 39 days.<ref>[https://clips.twitch.tv/TiredKnottyOrcaThunBeast-3MHslDyIHpEavrfG "Pendulum Crash" by rcombs]</ref>
|-
|Touching a recovery heart with more than ~10.7M speed.
| style="background-color: #ff9696" |Floating-Point Overflow
|Touching a recovery heart with more than ~10.7M speed will cause float-to-int conversion with a float value that's greater than the max integer value.<ref>[https://youtu.be/nDqSqrnjmHY Game Crash from Touching a Heart with 10.7M Speed]</ref>
|}

==RCP (Graphics) Crashes==
{| class="wikitable sortable"
!Cause!!Exception Type!!Notes
|-
|Have too many 3D models on screen at once|| style="background-color: #fffca8" |Invalid F3D command ||The main display list buffer has two sides, the left side holds F3D commands the game runs, and the right side holds allocated buffers for matrices. When an object's graphics are drawn, 16 bytes are used from the left side and 64 from the right side for each separate 3D model from the object. These two sides overlap when there are too many of these models on screen, leading to both sides being overwritten with garbage data and invalid F3D commands.
|-
|Moving the camera immediately when entering [[VCutM]]|| style="background-color: #fffca8" |Invalid F3D command||The object that spawns the rotating checkerboard platforms in VCutM references a model that doesn't exist. Normally this isn't a problem, since it's not on screen so it's culled before any damage occurs, and it despawns 1 frame after loading the level. However rotating the camera on the first frame, right before it despawns, it just barely comes into view. The non-existent model ends up sending invalid F3D commands to the RCP.
|}
==See Also==
[[Address Error Exception]]
==References==
<references />

[[Category:Glitches]]
{{Glitches}}

User:Oyion gaming

2024-12-08T22:52:29Z

Oyion gaming: Idk

I am a game lover