Frequently Asked Questions: Difference between revisions

(2 intermediate revisions by the same user not shown)

Line 118:

=== Can new moves be added? ===

The move list cannot be expanded at the moment, but ~~you can replace~~ some ~~of the~~ unused ~~moves (named [M:D1])~~. ~~Keep in mind that not all the [M:D1] moves~~ are ~~unused. Here’s a list with~~ the ~~known [M:D1] moves~~:

The move list cannot be expanded at the moment, but there's some unused move slots that can be replaced without any side effects. They are the following:

* 361: Excavate

* 362: Spin Slash

* 404: attack animation with no sound effect (safe to edit)

* 411: attack animation with no sound effect (safe to edit)

Line 132:

Line 130:

* 419: walking animation with no sound effect (safe to edit)

* 420: walking animation with no sound effect (safe to edit)

* 557: generic move sound effect (likely safe to edit, not confirmed)

* 558: generic move sound effect (likely safe to edit, not confirmed)

There's also a set of moves used for special purposes, which you can replace if you're certain their effect will never be called in your hack (for example, if you remove the Secret Bazaar, you can replace moves 421-423). These moves are the following:

* 361: Excavate

* 362: Spin Slash

* 421: Secret Bazaar Escape

* 422: Secret Bazaar Cleanse

Line 141:

Line 146:

* 428: All-Hit Orb

* 429: Foe-Seal Orb

* 467: Judgement

* 543: Weather Ball Sun

* 544: Weather Ball Hail

Line 156:

Line 160:

* 555: Skull Bash second half

* 556: Ghost-type Curse animation

* 557: generic move sound effect

If you need even more slots, you can also replace existing regular moves with entirely new ones. If you choose to do so, keep in mind that some moves have hardcoded checks that will cause problems if you replace them, so you should probably shouldn't touch those. Here's the list of moves with known hardcoded behavior:

* 558: generic move sound effect

~~Of course~~, you ~~could~~ also replace existing moves. If you choose to do so, keep in mind that some moves have hardcoded checks that will cause problems if you replace them, so you should probably shouldn't touch those. Here's the list of moves with known hardcoded behavior:

* 031: Weather Ball (has a special type check in <code>GetMoveTypeForMonster</code>)

Line 232:

Line 234:

These lines must be placed within <code>def 0 {</code>.

'''Note''': Evolving your starters ~~might cause them~~ to be removed from the active team~~, and you~~ can only add them back if [[Performance Progress Flags|performance progress flags 7 and 20]] are enabled.

'''Note''': Evolving any pokémon currently in your active team will disband it, which will cause your starters to be removed from the active team. You can only add them back if [[Performance Progress Flags|performance progress flags 7 and 20]] are enabled. You can add two more lines similar to the one used above to enable flag 10 to enable these two as well, although bear in mind that enabling these two flags has other side effects (check the page linked earlier for details).

=== Is there a way to mass edit data? ===

Line 276:

Line 278:

screen2_FadeIn(0, 30);

screen_FadeInAll(1, 30);

</syntaxhighlight>Then go back up until you see <code>forever {</code>, which should be on line 36. Select everything from that line to the line <code>switch ( message_Menu(MENU_PERSONALITY_TEST_END) ) { }</code>, (should be line 319) and delete it. Then paste the code you copied from case 28 where you deleted that chunk of code. You can optionally fix the indentation by pressing shift+tab a few times. Save the script and start a new game, the quiz will be automatically skipped and you will have the default player and partner as your team.

</syntaxhighlight>Then go back up until you see <code>forever {</code>, which should be on line 36. Select everything from that line (including the line itself) to the line <code>switch ( message_Menu(MENU_PERSONALITY_TEST_END) ) { }</code> (also included, should be line 319) and delete it. Then paste the code you copied from case 28 where you deleted that chunk of code. You can optionally fix the indentation by pressing shift+tab a few times. Save the script and start a new game, the quiz will be automatically skipped and you will have the default player and partner as your team.

=== What language are scripts written in? ===

@@ Line 118: / Line 118: @@
 === Can new moves be added? ===
-The move list cannot be expanded at the moment, but you can replace some of the unused moves (named [M:D1]). Keep in mind that not all the [M:D1] moves are unused. Here’s a list with the known [M:D1] moves:
+The move list cannot be expanded at the moment, but there's some unused move slots that can be replaced without any side effects. They are the following:
-* 361: Excavate
-* 362: Spin Slash
 * 404: attack animation with no sound effect (safe to edit)
 * 411: attack animation with no sound effect (safe to edit)
@@ Line 132: / Line 130: @@
 * 419: walking animation with no sound effect (safe to edit)
 * 420: walking animation with no sound effect (safe to edit)
+* 557: generic move sound effect (likely safe to edit, not confirmed)
+* 558: generic move sound effect (likely safe to edit, not confirmed)
+There's also a set of moves used for special purposes, which you can replace if you're certain their effect will never be called in your hack (for example, if you remove the Secret Bazaar, you can replace moves 421-423). These moves are the following:
+* 361: Excavate
+* 362: Spin Slash
 * 421: Secret Bazaar Escape
 * 422: Secret Bazaar Cleanse
@@ Line 141: / Line 146: @@
 * 428: All-Hit Orb
 * 429: Foe-Seal Orb
-* 467: Judgement
 * 543: Weather Ball Sun
 * 544: Weather Ball Hail
@@ Line 156: / Line 160: @@
 * 555: Skull Bash second half
 * 556: Ghost-type Curse animation
-* 557: generic move sound effect
+If you need even more slots, you can also replace existing regular moves with entirely new ones. If you choose to do so, keep in mind that some moves have hardcoded checks that will cause problems if you replace them, so you should probably shouldn't touch those. Here's the list of moves with known hardcoded behavior:
-* 558: generic move sound effect
-Of course, you could also replace existing moves. If you choose to do so, keep in mind that some moves have hardcoded checks that will cause problems if you replace them, so you should probably shouldn't touch those. Here's the list of moves with known hardcoded behavior:
 * 031: Weather Ball (has a special type check in <code>GetMoveTypeForMonster</code>)
@@ Line 232: / Line 234: @@
 These lines must be placed within <code>def 0 {</code>.
-'''Note''': Evolving your starters might cause them to be removed from the active team, and you can only add them back if [[Performance Progress Flags|performance progress flags 7 and 20]] are enabled.
+'''Note''': Evolving any pokémon currently in your active team will disband it, which will cause your starters to be removed from the active team. You can only add them back if [[Performance Progress Flags|performance progress flags 7 and 20]] are enabled. You can add two more lines similar to the one used above to enable flag 10 to enable these two as well, although bear in mind that enabling these two flags has other side effects (check the page linked earlier for details).
 === Is there a way to mass edit data? ===
@@ Line 276: / Line 278: @@
 screen2_FadeIn(0, 30);
 screen_FadeInAll(1, 30);
-</syntaxhighlight>Then go back up until you see <code>forever {</code>, which should be on line 36. Select everything from that line to the line <code>switch ( message_Menu(MENU_PERSONALITY_TEST_END) ) { }</code>, (should be line 319) and delete it. Then paste the code you copied from case 28 where you deleted that chunk of code. You can optionally fix the indentation by pressing shift+tab a few times. Save the script and start a new game, the quiz will be automatically skipped and you will have the default player and partner as your team.
+</syntaxhighlight>Then go back up until you see <code>forever {</code>, which should be on line 36. Select everything from that line (including the line itself) to the line <code>switch ( message_Menu(MENU_PERSONALITY_TEST_END) ) { }</code> (also included, should be line 319) and delete it. Then paste the code you copied from case 28 where you deleted that chunk of code. You can optionally fix the indentation by pressing shift+tab a few times. Save the script and start a new game, the quiz will be automatically skipped and you will have the default player and partner as your team.
 === What language are scripts written in? ===