Contest data structure (Generation III): Difference between revisions

jamming link
(→‎Format: Fill in mystery byte)
(jamming link)
 
(7 intermediate revisions by 4 users not shown)
Line 2: Line 2:
{{cleanup}}
{{cleanup}}
==Format==
==Format==
Information about a move's [[Appeal]]/[[Jam]] and other contest-related data in the {{game|Ruby and Sapphire|s}}, {{2v2|FireRed|LeafGreen|s}}, and {{v|Emerald}} games are stored in a 4-byte data structure.
Information about a move's [[Appeal]]/[[Jamming]] and other Contest-related data in the {{game|Ruby and Sapphire|s}}, {{2v2|FireRed|LeafGreen}}, and {{v|Emerald}} games are stored in a 4-byte data structure.


{| align="center" style="border: 1px solid #88a; background: #f8f8ff; padding: 0.5em;" cellspacing="1"
{| align="center" style="border: 1px solid #88a; background: #f8f8ff; padding: 0.5em;" cellspacing="1"
Line 34: Line 34:
==Notes==
==Notes==


Unlike most other structures which use the move's ID as the key for this array, this array of structures uses the move's contest description ID as its index.
Unlike most other structures which use the move's ID as the key for this array, this array of structures uses the move's Contest description ID as its index.


==Fingerprint==
==Fingerprint==


Since this array uses the move's contest description ID as its index, we chose to display the corresponding description after each structure.
Since this array uses the move's Contest description ID as its index, we chose to display the corresponding description after each structure.


<pre>
<pre>
Line 53: Line 53:


==See also==
==See also==
* [[Contest move data structure in Generation III]]
* [[Contest move data structure (Generation III)]]


{{data structure}}
{{data structure}}<br>
{{Project Games notice|data structure}}
{{Project Games notice|data structure}}