Difference between revisions of "Conditional Out of Bounds (Riidefi)"
Jump to navigation
Jump to search
(→Cheat Codes: quote "Korean people are smart enough to port it themselves") |
|||
| Line 1: | Line 1: | ||
| − | '''Conditional out of bounds''' is a [[Cheat Code|cheat code]] created by [[Riidefi]] that makes it easier for track authors to implement intersections without having to worry about unintended fall boundaries being triggered when someone on the lower part of the track gets too much air. It makes use of [[AREA type#AREA_type_0x0A_.28Fall_Boundary.29|AREA type 10]] which will serve as the conditional out of bounds | + | '''Conditional out of bounds''' is a [[Cheat Code|cheat code]] created by [[Riidefi]] that makes it easier for track authors to implement intersections without having to worry about unintended fall boundaries being triggered when someone on the lower part of the track gets too much air. It makes use of [[AREA type#AREA_type_0x0A_.28Fall_Boundary.29|AREA type 10]] which will serve as the conditional out of bounds. |
== Usage == | == Usage == | ||
| − | Add an AREA of type 10 (0xA) to the KMP. The first and second AREA parameters, "P1" and "P2", define the checkpoint range: the area will be enabled if and only if a player is in the Cth checkpoint sector such that P1 <= C < | + | Add an AREA of type 10 (0xA) to the KMP. The first and second AREA parameters, "P1" and "P2", define the checkpoint range: the area will be enabled if and only if a player is in the Cth checkpoint sector such that P1 <= C < P2.<br> |
| + | NOTE: If both P1 and P2 are zero, this code is disabled, and the boundary is unconditionally enabled. | ||
== License == | == License == | ||
| Line 11: | Line 12: | ||
== Cheat Codes == | == Cheat Codes == | ||
| − | <spoiler text="Conditional OOB, PAL"> | + | <spoiler text="Conditional OOB v1.1, PAL"> |
<pre> | <pre> | ||
Conditional OOB v1.1, PAL [Riidefi] | Conditional OOB v1.1, PAL [Riidefi] | ||
| Line 38: | Line 39: | ||
60000000 00000000 | 60000000 00000000 | ||
</pre></spoiler> | </pre></spoiler> | ||
| − | <spoiler text="Conditional OOB, NTSC-U"> | + | <spoiler text="Conditional OOB v1.1, NTSC-U"> |
<pre> | <pre> | ||
Conditional OOB v1.1, NTSC-U [Riidefi] | Conditional OOB v1.1, NTSC-U [Riidefi] | ||
| Line 65: | Line 66: | ||
60000000 00000000 | 60000000 00000000 | ||
</pre></spoiler> | </pre></spoiler> | ||
| − | <spoiler text="Conditional OOB, NTSC-J"> | + | <spoiler text="Conditional OOB v1.1, NTSC-J"> |
<pre> | <pre> | ||
Conditional OOB v1.1, NTSC-J [Riidefi] | Conditional OOB v1.1, NTSC-J [Riidefi] | ||
| Line 92: | Line 93: | ||
60000000 00000000 | 60000000 00000000 | ||
</pre></spoiler> | </pre></spoiler> | ||
| − | <spoiler text="Conditional OOB, NTSC-K"> | + | <spoiler text="Conditional OOB v1.1, NTSC-K"> |
<pre> | <pre> | ||
| − | Conditional OOB v1. | + | Conditional OOB v1.1, NTSC-K [Riidefi] |
| − | C255F8CC | + | C255F8CC 00000016 |
| − | + | 7C630735 41A000A4 | |
| − | + | 3CA0809B 809F0018 | |
| − | + | 8105BD28 5467103A | |
| − | + | 5467103A 80C5BD70 | |
| − | + | 38A0FFFF 8108002C | |
| − | + | 88040010 81080000 | |
| − | + | 8086000C 5400103A | |
| − | + | 5400103A 7CC8382E | |
| − | + | 7C84002E 80C60004 | |
| − | + | A104000A A006002A | |
| − | + | A0E60028 7C040034 | |
| − | + | 7C004050 7CE60034 | |
| − | + | 54C6D97E 54C6D97E | |
| − | + | 5484D97E 5484D97E | |
| − | + | 7CC62038 54000FFE | |
| + | 54000FFE 3086FFFF | ||
| + | 7CC43110 7C874010 | ||
| + | 7C850190 7C800038 | ||
| + | 7CC40378 3004FFFF | ||
| + | 7C802110 3804FFFF | ||
| + | 7C031B78 2C030000 | ||
60000000 00000000 | 60000000 00000000 | ||
</pre></spoiler> | </pre></spoiler> | ||
[[category:Cheat Codes|!]] | [[category:Cheat Codes|!]] | ||
Revision as of 18:02, 9 July 2020
Conditional out of bounds is a cheat code created by Riidefi that makes it easier for track authors to implement intersections without having to worry about unintended fall boundaries being triggered when someone on the lower part of the track gets too much air. It makes use of AREA type 10 which will serve as the conditional out of bounds.
Usage
Add an AREA of type 10 (0xA) to the KMP. The first and second AREA parameters, "P1" and "P2", define the checkpoint range: the area will be enabled if and only if a player is in the Cth checkpoint sector such that P1 <= C < P2.
NOTE: If both P1 and P2 are zero, this code is disabled, and the boundary is unconditionally enabled.
License
CTGP and LE-Code are exempt from the GPLv3 license. They may instead license this code under the MIT license. In doing so, they may alter, supplement, or entirely remove this copyright notice.