ZUD plugin - Z-moves, Ultra-Burst, Dynamax, Dynamax adventures [v18]

StCooler · Feb 1, 2021

The ZUD plugin

Z-moves, Ultra-Burst and Dynamax together in one plugin!

By Lucidious89 and StCooler, for the Gen 8 project.

Essentials v18 is deprecated, so is this version of the ZUD plugin.
For the newest release of ZUD, please check ZUD for Essentials19.1

ZUD is the result of the joint work by Lucidious89 and StCooler, merging the former's Dynamax/Max Raid plugin, and the latter's Z-move add-on update.

Contents

As the name suggest, the ZUD plugin contains all the scripting for:

Z-moves (from SM and USUM)
Necrozma's Ultra-Burst
Dynamax
Max Raid battles
Dynamax Adventures (NEW Release 2021-04-13)

Detailed contents:

Spoiler:

>> Download <<

Credits:

Spoiler:

About the version of Essentials

Spoiler:

Installation

Spoiler:

File installation:

Spoiler:

General script installations:

Spoiler:

In Battler_UseMove, in the function:

Code:

  def pbUseMove(choice,specialUsage=false)

below the line "pbBeginTurn(choice)":

Paste this:

Code:

    #===========================================================================
    # Changes Z-Move/Max Moves under certain conditions. (ZUD)
    #===========================================================================
    ret = pbChangePowerMove(choice)
    choice[2] = ret if ret
    #===========================================================================

In Editor_SaveData, in the function:

Code:

def pbSaveAllData

below line "pbSaveShadowMoves; Graphics.update":

Paste this:

Code:

  #=============================================================================
  # Z-Move/Dynamax Data (ZUD)
  #=============================================================================
  pbSaveZMoveCompatibility; Graphics.update
  pbSaveGigantamaxData;   Graphics.update
  #=============================================================================

In Compiler, in the function:

Code:

def pbCompileAllData(mustCompile)

Below the line "pbCompilePokemonForms":
Paste this:

Code:

    #===========================================================================
    # Compiles data for Z-Moves and Dynamax. (ZUD)
    #===========================================================================
    # Depends on PBSpecies, PBMoves, PBItems
    yield(_INTL("Compiling Z-Moves compatibility data"))
    pbCompileZMoveCompatibility
    # Depends on PBSpecies, PBMoves, PBItems
    yield(_INTL("Compiling Gigantamax data"))
    pbCompileGigantamaxData
    #===========================================================================

In the function:

Code:

def pbCompiler

Find the line "Constants.rxdata":
And REPLACE it with this:

Code:

	   "Constants.rxdata",
       #========================================================================
       # Z-Moves/Dynamax Data (ZUD)
       #========================================================================
       "ZUD_zmoves.dat",
       "ZUD_dynamax.dat"
       #========================================================================

In the same function:

Code:

def pbCompiler

Find the line "types.txt" in the textFiles array:
And REPLACE it with this:

Code:

	   "types.txt",
       #========================================================================
       # Z-Moves/Dynamax Data (ZUD)
       #========================================================================
       "ZUD_zmoves.txt",
       "ZUD_dynamax.txt"
       #========================================================================

Script installation for Z-moves:

Spoiler:

In Battler_UseMove, in the function:
Code:
```
  def pbUseMove(choice,specialUsage=false)
```
Next to "@battle.pbCanShowCommands?(@index)" on the same line:
Paste this:
Code:
```
	&& !choice[2].zMove? # Added for Z-Moves (ZUD)
```

In the file Battle_Action_Switching, this step requires more attention, because Gen 8 project and v18.1 handle this part differently.

HERE IS FOR V18 AND V18.1

Spoiler:

HERE IS FOR GEN 8 PROJECT

Spoiler:

In Battle_Action_Other, in the function pbCanMegaEvolve?
Code:
```
  def pbCanMegaEvolve?(idxBattler)
```
Below the line "return false if !@battlers[idxBattler].hasMega?"
Paste this:
Code:
```
	return false if pbCanZMove?(idxBattler) # Added for Z-Moves (ZUD)
```

Script installations for Ultra-Burst:

Spoiler:

Script installations for Dynamax:

Spoiler:

In Battler_UseMove_SuccessChecks, in the function:

Code:

  def pbCanChooseMove?(move,commandPhase,showMessages=true,specialUsage=false)

find the line:

Code:

      next if !b.effects[PBEffects::Imprison] || !b.pbHasMove?(move.id)

and REPLACE it with:

Code:

      #=========================================================================
      # Dynamax - Imprison only blocks base moves, not Max Moves. (ZUD)
      #=========================================================================
      next if move.powerMove?
      basemove = false
      b.eachMoveWithIndex do |m,i|
        next if !b.effects[PBEffects::BaseMoves]
        basemove = true if b.effects[PBEffects::BaseMoves][i].id==move.id
      end
      hasmove = (b.dynamax?) ? basemove : b.pbHasMove?(move.id)
      next if !b.effects[PBEffects::Imprison] || !hasmove
      #=========================================================================

In the same file, in the function:

Code:

  def pbSuccessCheckAgainstTarget(move,user,target)

Above line "# Crafty Shield":
Paste this:

Code:

    #===========================================================================
    # Dynamax - Success Checks (ZUD)
    #===========================================================================
    ret = pbSuccessCheckDynamax(move,user,target)
    return false if ret==false
    #===========================================================================

In Battler_UseMove_TriggerEffects, in the function:

Code:

  def pbEffectsOnMakingHit(move,user,target)

Find the following code:

Code:

      # Grudge
      if target.effects[PBEffects::Grudge] && target.fainted?
        move.pp = 0
        @battle.pbDisplay(_INTL("{1}'s {2} lost all of its PP due to the grudge!",
           user.pbThis,move.name))
      end
      # Destiny Bond (recording that it should apply)
      if target.effects[PBEffects::DestinyBond] && target.fainted?
        if user.effects[PBEffects::DestinyBondTarget]<0
          user.effects[PBEffects::DestinyBondTarget] = target.index
        end
      end

and REPLACE it with:

Code:

      #=========================================================================
      # Effects for Grudge and Destiny Bond. (ZUD)
      #=========================================================================
      pbEffectsOnKO(move,user,target)
      #=========================================================================

In Move_Usage_Calculations, in the function:

Code:

  def pbIsCritical?(user,target)

below the line:

Code:

    c += user.effects[PBEffects::FocusEnergy]

paste this:

Code:

    #===========================================================================
    # Dynamax - The crit-boosting effect of G-Max Chi Strike. (ZUD)
    #===========================================================================
    c += user.effects[PBEffects::ChiStrike]
    #===========================================================================

In Battle_Action_Switching, in the function:

Code:

  def pbOnActiveOne(battler)

Above line "# Stealth Rock":
Paste this:

Code:

    #===========================================================================
    # Dynamax - G-Max Steelsurge hazard effect (ZUD)
    #===========================================================================
    pbSteelsurgeEffect(battler)
    #===========================================================================

In Battle_Phase_EndOfRound, in the function:

Code:

  def pbEndOfRoundPhase

Above line "# Status-curing effects/abilities and HP-healing items":
Paste this:

Code:

    #===========================================================================
    # Dynamax - End of round effects (G-Max Vine Lash, Wildfire, etc.) (ZUD)
    #===========================================================================
    pbEORMaxMoveEffects(priority)
    #===========================================================================

Above line "@endOfRound = false":
Paste this:

Code:

    #===========================================================================
    # Dynamax - Counts down Dynamax turns. (ZUD)
    #===========================================================================
    pbDynamaxTimer
    #===========================================================================

In PScreen_Party, in the class:

Code:

class PokemonPartyPanel < SpriteWrapper

and in the function:

Code:

  def initialize(pokemon,index,viewport=nil)

Below line "@pkmnsprite.z = self.z+2" (the number of spaces on this line may
differ)
Paste this:

Code:

    #===========================================================================
    # Dynamax - Enlarges Pokemon icon sprite when Dynamaxed. (ZUD)
    #===========================================================================
    pbDynamaxSize
    #===========================================================================

In the same class PokemonPartyPanel, in the function:

Code:

  def pokemon=(value)

Below line "@pkmnsprite.pokemon = value if @pkmnsprite && [email protected]?"
In v18.1: below line "@pkmnsprite.pokemon = value"
Paste this:

Code:

    #===========================================================================
    # Dynamax - Enlarges Pokemon icon sprite when Dynamaxed. (ZUD)
    #===========================================================================
    pbDynamaxSize
    #===========================================================================

In the same class PokemonPartyPanel, in the function:

Code:

  def refresh

Below line "@pkmnsprite.color = self.color" (the number of spaces on this line
may differ)
Paste this:

Code:

      #=========================================================================
      # Dynamax - Colors Dynamax Pokemon's icon sprites. (ZUD)
      #=========================================================================
      pbDynamaxColor
      #=========================================================================

In PScreen_Summary, in the function:

Code:

  def drawPage(page)

After the following code:

Code:

    # Show shininess star
    if @pokemon.shiny?
      imagepos.push([sprintf("Graphics/Pictures/shiny"),2,134])
    end

Paste this:

Code:

    #===========================================================================
    # Dynamax - Displays Dynamax Levels and G-Max Factor. (ZUD)
    #===========================================================================
    pbDisplayGMaxFactor   if defined?(@pokemon.dynamax?)
    pbDisplayDynamaxMeter if defined?(@pokemon.dynamax?)
    #===========================================================================

Note that the resulting code should be like this:

Code:

    # Show shininess star
    if @pokemon.shiny?
      imagepos.push([sprintf("Graphics/Pictures/shiny"),2,134])
    end
    #===========================================================================
    # Dynamax - Displays Dynamax Levels and G-Max Factor. (ZUD)
    #===========================================================================
    pbDisplayGMaxFactor   if defined?(@pokemon.dynamax?)
    pbDisplayDynamaxMeter if defined?(@pokemon.dynamax?)
    #===========================================================================

That is, the added code should be AFTER the "end".

In the same function:

Code:

  def drawPage(page)

Above line "# Write the held item's name":
Paste this:

Code:

    #===========================================================================
    # Dynamax - For Dynamax Level display. (ZUD)
    #===========================================================================
    if defined?(@pokemon.dynamax?)
      textpos[3][0]="" if @page==3 && @pokemon.dynamaxAble?
    end
    #===========================================================================

In the function:

Code:

  def drawMoveSelection(moveToLearn)

Find these two lines:

Code:

        imagepos.push(["Graphics/Pictures/types",248,yPos+2,0,move.type*28,64,28])
        textpos.push([PBMoves.getName(move.id),316,yPos,0,moveBase,moveShadow])

And REPLACE these lines with this:

Code:

        #=======================================================================
        # Dynamax - Draws Max Move names and types. (ZUD)
        #=======================================================================
        movelist = drawMaxMoveSel(move,yPos,moveBase,moveShadow,moveToLearn)
        imagepos.push(movelist[0])
        textpos.push(movelist[1])
        #=======================================================================

In the function:

Code:

  def drawSelectedMove(moveToLearn,moveid)

Below line "accuracy = moveData[MOVE_ACCURACY]" (the number of spaces on this
line may differ)
Paste this:

Code:

    #===========================================================================
    # Dynamax - Displays Max Move data. (ZUD)
    #===========================================================================
    maxMoveData = pbGetMaxMoveData(moveToLearn,moveid)
    if maxMoveData
      basedamage = maxMoveData[0]
      accuracy   = maxMoveData[1]
      moveid     = maxMoveData[2]
    end
    #===========================================================================

OPTIONAL: In Debug_Pokemon, in the function:

Code:

  def pbPokemonDebugCommands(settingUpBattle=false)

Above line "commands.add("levelstats","sethappiness",_INTL("Set happiness"))"
Paste this:

Code:

      #=========================================================================
      # Dynamax options. (ZUD)
      #=========================================================================
      commands.add("levelstats","dynamax",_INTL("Dynamax...")) 
      #=========================================================================

In the function:

Code:

  def pbPokemonDebugActions(command,pkmn,pkmnid,heldpoke=nil,settingUpBattle=false)

Above line "when "sethappiness""
Paste this:

Code:

    #===========================================================================
    # Dynamax Values (ZUD)
    #===========================================================================
    when "dynamax"
      cmd = 0
      if pkmn.egg? || pkmn.shadowPokemon? || !pkmn.dynamaxAble?
        pbDisplay(_INTL("Can't edit Dynamax values on that PokÃ©mon."))
        pkmn.dynamax_lvl = 0
        pkmn.gmaxfactor = false
        if pkmn.dynamax?
          pkmn.makeUndynamax
          pkmn.calcStats
          pkmn.pbReversion(false)
        end
        return
      end
      loop do
        dlvl = pkmn.dynamax_lvl
        gmax = "No"
        gmax = "Yes" if pkmn.gmaxFactor?
        dmax = "No"
        dmax = "Yes" if pkmn.dynamax?
        cmd = @scene.pbShowCommands(_INTL("Dynamax Level: {1}\nG-Max Factor: {2}\nDynamaxed: {3}",dlvl,gmax,dmax),[
             _INTL("Set Dynamax Level"),
             _INTL("Set G-Max Factor"),
             _INTL("Set Dynamax"),
             _INTL("Reset All")],cmd)
        break if cmd<0
        case cmd
        when 0   # Set Dynamax Level
          params = ChooseNumberParams.new
          params.setRange(0,10)
          params.setDefaultValue(pkmn.dynamax_lvl)
          params.setCancelValue(pkmn.dynamax_lvl)
          f = Kernel.pbMessageChooseNumber(_INTL("Set {1}'s Dynamax level (max. 10).",
             pkmn.name),params) { @scene.update }
          if f!=pkmn.dynamax_lvl
            pkmn.dynamax_lvl = f
            pbRefreshSingle(pkmnid)
          end
        when 1   # Set G-Max Factor
          if pkmn.gmaxFactor?
            pkmn.removeGMaxFactor
            pbDisplay(_INTL("Gigantamax factor was removed from {1}.",pkmn.name))
          else
            if pkmn.hasGmax? 
              pkmn.giveGMaxFactor
              pbDisplay(_INTL("Gigantamax factor was given to {1}.",pkmn.name))
            else
              pbDisplay(_INTL("{1} doesn't have a Gigantamax form.",pkmn.name))
              if pbConfirm(_INTL("Give it Gigantamax factor anyway?"))
                pkmn.giveGMaxFactor
                pbDisplay(_INTL("Gigantamax factor was given to {1}.",pkmn.name))
              end
            end
          end
          pbRefreshSingle(pkmnid)
        when 2   # Set Dynamax
          if pkmn.dynamax?
            pkmn.makeUndynamax
            pkmn.calcStats
            pkmn.pbReversion(false)
            pbDisplay(_INTL("{1} is no longer dynamaxed.",pkmn.name))
          else
            pkmn.makeDynamax
            pkmn.calcStats
            pkmn.pbReversion(true)
            pbDisplay(_INTL("{1} is dynamaxed.",pkmn.name))
          end
          pbRefreshSingle(pkmnid)
        when 3   # Reset All
          pkmn.setDynamaxLvl(0)
          pkmn.removeGMaxFactor
          if pkmn.dynamax?
            pkmn.makeUndynamax
            pkmn.calcStats
            pkmn.pbReversion(false)
          end
          pbDisplay(_INTL("All dynamax settings restored to default."))
          pbRefreshSingle(pkmnid)
        end
      end
    #===========================================================================

Script installations for Max Raids:

Spoiler:

In BattleHanders_Abilities, in the entry for Emergency Exit:

Code:

BattleHandlers::AbilityOnHPDroppedBelowHalf.add(:EMERGENCYEXIT,

Above the line "# In wild battles":
Paste this:

Code:

	next false if battler.effects[PBEffects::MaxRaidBoss] # For Max Raids (ZUD)

In Battler_UseMove, in the function:

Code:

  def pbUseMove(choice,specialUsage=false)

Below line "break if magicCoater>=0 || magicBouncer>=0"
Paste this:

Code:

        #=======================================================================
        # Max Raids - Ends multi-hit moves early when boss is defeated. (ZUD)
        #=======================================================================
        break if pbBreakRaidMultiHits(targets,i)
        #=======================================================================

(Gen 8 project) Above the lines:

Code:

      # HP-healing held items (checks all battlers rather than just targets
      # because Flame Burst's splash damage affects non-targets)

OR (v18.1) above line "# HP-healing held items":
Paste this:

Code:

    #=========================================================================
    # Max Raids - Effects when target is a Max Raid Pokemon. (ZUD)
    #=========================================================================
    pbProcessRaidEffectsOnHit(move,user,targets,hitNum)
    #=========================================================================

In the function:

Code:

  def pbProcessMoveHit(move,user,targets,hitNum,skipAccuracyCheck)

Above line:

Code:

    if !user.hasActiveAbility?(:SHEERFORCE)

Paste this:

Code:

    #===========================================================================
    # Max Raids - Effects when user is a Max Raid Pokemon. (ZUD)
    #===========================================================================
    pbProcessRaidEffectsOnHit2(move,user,targets)
    #===========================================================================

In the file Move_Usage,
OR in the file BattleScript_Main (if you have the Mid Battle Dialogue installed),
find the function:

Code:

  def pbReduceDamage(user,target)

Above line "if damage>=target.hp":
Paste this:

Code:

    #===========================================================================
    # Max Raids - Damage thresholds for triggering shields. (ZUD)
    #===========================================================================
    damage = pbReduceMaxRaidDamage(target,damage)
    #===========================================================================

In Move_Usage_Calculations, in the function:

Code:

  def pbCalcDamageMultipliers(user,target,numTargets,type,baseDmg,multipliers)

Below line:

Code:

    multipliers[FINAL_DMG_MULT] = pbModifyDamage(multipliers[FINAL_DMG_MULT],user,target)

Paste this:

Code:

    #===========================================================================
    # Max Raids - Reduces damage while behind a Raid Shield. (ZUD)
    #===========================================================================
    pbCalcRaidShieldDamage(target,multipliers)
    #===========================================================================

In PokeBattle_Common, in the function:

Code:

  def pbThrowPokeBall(idxBattler,ball,rareness=nil,showPlayer=false)

Above line "# Calculate the number of shakes (4=capture)":
Paste this:

Code:

    #===========================================================================
    # Max Raids - Prevents capture of Raid Pokemon until it's defeated. (ZUD)
    #===========================================================================
    return if pbRaidCaptureFail(battler,ball)
    #===========================================================================

Above line "pkmn.pbUpdateShadowMoves if pkmn.shadowPokemon?":
Paste this:

Code:

	pbResetRaidPokemon(pkmn) # Reverts Max Raid Boss (ZUD)

In Battle_StartAndEnd,
OR in the file BattleScript_Main (if you have the Mid Battle Dialogue installed),
find the function:

Code:

  def pbStartBattleSendOut(sendOuts)

Find line "pbDisplayPaused(_INTL("Oh! A wild {1} appeared!",foeParty[0].name))":
REPLACE it with this:

Code:

     #=======================================================================
     # Max Raids - Alters encounter text. (ZUD)
     #=======================================================================
     if defined?(MAXRAID_SWITCH) && $game_switches[MAXRAID_SWITCH]
       text = "Dynamaxed"
       text = "Gigantamax" if foeParty[0].gmaxFactor?
       text = "Eternamax"  if isConst?(foeParty[0].species,PBSpecies,:ETERNATUS)
       pbDisplayPaused(_INTL("Oh! A {1} {2} lurks in the den!",text,foeParty[0].name))
     else
       pbDisplayPaused(_INTL("Oh! A wild {1} appeared!",foeParty[0].name))
     end
     #=======================================================================

In Battle_Phase_Command, in the function:

Code:

  def pbCommandPhaseLoop(isPlayer)

Below the line "break if pbCallMenu(idxBattler)":
Paste this:

Code:

        #=======================================================================
        # Max Raids - Replaces the Run command with Cheer during raids. (ZUD)
        #=======================================================================
        when 5    # Cheer
          break if pbCheerMenu(idxBattler)
        #=======================================================================

In Battle_Phase_EndOfRound, in the function:

Code:

  def pbEndOfRoundPhase

Find the lines:

Code:

    pbGainExp
    return if @decision>0
    # Form checks

Above these lines, paste this:

Code:

    #===========================================================================
    # Max Raids - End of round effects. (ZUD)
    #===========================================================================
    pbEORMaxRaidEffects(priority)
    #===========================================================================

In Pokemon_Forms, find the instance for Rotom:

Code:

MultipleForms.register(:ROTOM,{

Above line "idxMoveToReplace = -1":
Paste this:

Code:

    #===========================================================================
    # Max Raids - Allows Rotom forms to properly spawn in Max Raids. (ZUD)
    #===========================================================================
    moveKnown = true if pkmn.form>0 && pkmn.hasMove?(formMoves[pkmn.form-1])
    break if moveKnown
    #===========================================================================

In Scene_Commands, in the function:

Code:

  def pbCommandMenuEx(idxBattler,texts,mode=0)

Find the line:

Code:

      elsif Input.trigger?(Input::B) && mode==1   # Cancel

And REPLACE it with this:

Code:

      elsif Input.trigger?(Input::B) && (mode==1 || mode==5)  # Cancel (ZUD)

What to do if you already installed the previous Dynamax plugin or the Z-move addon

Spoiler:

Support for the previous version of the Dynamax plugin, and for the Z-move add-on is discontinued. You shouldn't download these scripts anymore.

There are three solutions, in decreasing order of radicality:

Backup your file Scripts.rxdata, download the Gen 8 project again, replace your Scripts.rxdata with the clean one, and install the ZUD scripts. You'll also need to install every other script you added.
Do this if you only added new scripts from others, and did little to no scripting on your own.
Backup your file Scripts.rxdata, download the Gen 8 project again, and open both your project, and the Gen 8 project. Copy/paste the following scripts from the Gen 8 project to your project:
Spoiler:
(If you installed the Z-move add-on for v18.dev by StCooler)
- Settings
- PokeBattle_Battler
- Battler_UseMove
- Battler_UseMove_SuccessChecks
- PokeBattle_Move
- PokeBattle_Battle
- Battle_Action_Switching
- Battle_Action_Other
- Battle_Phase_Command
- Battle_Phase_Attack
- PokeBattle_AI
- PokeBattle_SceneMenus
- Scene_Commands
- PBEffects
- PokeBattle_DebugScene
- PokeBattle_ActiveField
- PItem_Items
- PItem_ItemEffects
- PItem_Bag
- Pokemon_Forms
- Editor_SaveData
- Compiler
(If you installed the Dynamax/Max Raid addon by Lucidious89)

Just delete the current Dynamax and Mechanic_Compatibility scripts. The ZUD Plugin uses completely different scripts, all to be installed right above Main.

Also, undo steps 1 & 5 in the Additional Installation guide. These steps are changed in the new plugin. All the other steps *should* still be the same (although the plugin adds some additional new steps).

Audio and Graphics are the same, the new plugin just adds more. Item and Move PBS data is updated though, so those'll have to be replaced.
(This will reset these scripts).
You will need to check your other installed scripts, so that you make sure everything is working correctly.
Do this if you have installed new scripts, but not so many that alter things in battle.
Backup your file Scripts.rxdata, and read carefully the installation processes detailed in the original post for Z-moves and Dynamax. Remove any added line.
This is tedious but it's the cleanest way to do it if you heavily modified your scripts for your project.
Cry. It may help.

F.A.Q.

Spoiler:

StCooler · Feb 1, 2021

The ZUD plugin - Z-move tutorial

This post contains tutorials on:

How to allow the use of Z-moves in game

How to make a new Z-move for damaging moves

How to make a new Z-move for status moves

Mid Battle Dialogue addition

How to use Z-moves in game

Spoiler:

How to make a new Z-move for damaging moves

Spoiler:

How to make a new Z-move for a status move

Spoiler:

Mid Battle Dialogue addition

Spoiler:

Lucidious89 · Feb 1, 2021

The ZUD Plugin - Dynamax Tutorial

This post contains tutorials on:

A detailed overview on all Dynamax mechanics.

How to allow the use of Dynamax in game.

How to make a new G-Max Pokemon.

How to make a new G-Max Move.

Dynamax Overview

Spoiler:

How to Use Dynamax in game.

Spoiler:

A Dynamax Band must first be present in the player's inventory for Dynamax to be possible. NPC's don't require this item. You can add other items that allow Dynamaxing in the DMAX_BANDS array. Once one of these items are obtained, Dynamax will be possible, but only on certain maps. Any map ID listed in the POWERSPOTS array in ZUD_01_Settings_Misc is considered a Power Spot, and capable of supporting Dynamax. By default, this array contains maps for the Pokemon Gym, Pokemon League, and Battle Facilities maps found in Essentials. Change this to suit your game.
If you'd like to make it so Dynamax is possible on any map, you can instead set DMAX_ANYMAP to true. Doing so will ignore the POWERSPOTS array, and instead make it so Dynamax is possible anywhere.
Eternatus is normally unable to Dynamax, however special type of Dynamaxing known as Eternamax is exclusively available to this Pokemon to enter its Eternamax form. This special form is unavailable to the player in the main series, but it's included here if you'd care to use it. Eternamax may only be performed on map ID's found in the ETERNASPOT array. This array is empty by default.
Under normal conditions, Dynamax is only available during trainer battles (or raids). However, you may enable the ability to Dynamax during normal wild encounters by setting CAN_DMAX_WILD to true.
Finally, certain species are completely unable to Dynamax. These species, by default, are limited to Zacian, Zamazenta, and Eternatus (unless Eternamaxing). Add a species to the DMAX_BANLIST array if you want that species to be unable to use Dynamax.
The game switch NO_DYNAMAX will toggle the entire Dynamax mechanic on or off.

NPC Trainers
Your opponents have the ability to use Dynamax against you too, and you can customize this to your liking. This can be manually set in the trainers PBS file, or through the in-game editor. Each trainer's Pokemon have new data that can be set: Dynamax Level, Gigantamax, and Trainer Ace. Dynamax Level is self explanatory. This simply controls the Dynamax Level of the trainer's Pokemon. This is set to a number between 0-10. Gigantamax controls whether or not the trainer's Pokemon will appear in its Gigantamax form. Simply set this to "yes" to make it Gigantamax, otherwise omit it. If you flag a trainer's Pokemon as Gigantamax but the species doesn't have a G-Max form, this is simply ignored.

A Trainer Ace is simply a flag that designates a Pokemon as that trainer's signature Pokemon. For example, Onix could be seen as Brock's ace Pokemon. When a Pokemon in an NPC's party is flagged as a "TrainerAce", the AI will ONLY Dynamax that ace Pokemon, and never waste it on their other Pokemon.

Here's an example of setting up an NPC's Trainer Ace in the trainer PBS data.

Code:

[CAMPER,Liam]
LoseText = "A very good battle, indeed!"
Pokemon = MAWILE,11
Pokemon = MEOWTH,12
    TrainerAce = yes
    DynamaxLvl = 5
    Gigantamax = yes

As seen here, Camper Liam's Meowth is set as his Trainer Ace, which means he will only ever use Dynamax with Meowth, and never waste it on Mawile, regardless of party order. Meowth's Dynamax level and G-Max Factor are also set, so Meowth will always be in its Gigantamax form when Camper Liam Dynamaxes it.

You can also edit these values with the in-game editor, as seen here:

[PokeCommunity.com] ZUD plugin - Z-moves, Ultra-Burst, Dynamax, Dynamax adventures [v18]

Editing Trainer Ace and Dynamax values in the trainer editor.

Note that you can set multiple Pokemon in an NPC's lineup as their Trainer Ace. However, they will simply use their Dynamax for whichever one of those aces they send out first, and be unable to use it again for the others. So you can set multiple aces if you want to give that trainer multiple Dynamax options and make them a little less predictable.

How to make a new G-Max Pokemon.

Spoiler:

How to make a new G-Max Move.

Spoiler:

STEP 1: Move PBS data
To add a new G-Max move, you first define it in moves.txt PBS file like you would any other move:

Code:

XXX,GMAXSOULSHATTER,G-Max Soul Shatter,D00A,1,GHOST,Physical,0,1,0,NearFoe,0,fx,"A Ghost-type attack that Gigantamax Giratina use. This move places a curse on all opponents."

However, there are a few key things to keep in mind with G-Max Moves:

G-Max Moves, and Max Moves in general, derive their base power from the base move it's converted from. So all Max Moves should be given 1 as its base power. If you set this to a number higher than 1 however, the move will use always use this number as its base power instead, and ignore the base move when calculating power. The moves G-Max Drum Solo, G-Max Fireball, and G-Max Hydrosnipe use this feature, as those moves are always set to 160 BP, regardless of the move its based on.
G-Max Moves, and Max Moves in general, derive their damage category from the base move it's converted from. So all Max Moves are listed as Physical moves simply as placeholder, since this will get converted anyway.
The "x" flag is a new flag added by this plugin, and flags the current move as a Max Move. This is a required flag to add on any Max Move.
Just like with any other move, it needs its own function code if it has a unique effect. All Max Moves use function codes D000-D0023, so feel free to continue adding more in this way. If you don't want your custom move to have any special effect, just use D000 as its function code.

STEP 2: Adding the new G-Max code
In ZUD_06_Move_Effects, add your new move beneath the last G-Max Move. Here's a simple example of G-Max Soul Shatter's curse effect.

Code:

#===============================================================================
# G-Max Soul Shatter.
#===============================================================================
# Curses all opposing Pokemon.
#-------------------------------------------------------------------------------
class PokeBattle_Move_D00A < PokeBattle_MaxMove
  def pbEffectAgainstTarget(user,target)
    user.eachOpposing do |b|
      next if b.effects[PBEffects::Curse]
      b.effects[PBEffects::Curse] = true
      @battle.pbDisplay(_INTL("A curse was laid on {1}!",b.pbThis(true)))
    end
  end
end

There's no difference from coding any other move except that you subclass PokeBattle_MaxMove instead of PokeBattle_Move. Keep in mind that Max Moves should never use pbAdditionalEffect for its effects, because these effects work on chance and can be manipulated by certain effects, but Max Move effects always occur. Use pbEffectGeneral or pbEffectAgainstTarget to code these move effects instead.

Lucidious89 · Feb 1, 2021

The ZUD plugin - Max Raid Tutorial

This post contains tutorials on:

A detailed overview on all Max Raid mechanics.

How to set up Max Raid Dens in your game.

How to access and use the Max Raid Database.

Max Raid Overview

Spoiler:

Max Raid Mechanics
In the main series, Max Raid battles pits you and three others up against a wild Dynamaxed Pokemon. These Pokemon have increased HP, as well as special battle mechanics such as shields, and need to be taken down for an opportunity to capture it. If the Dynamax Pokemon KO's your Pokemon a certain number of times, or if a certain number of turns have passed, you and your allies get blown out of the den, and the raid ends.

However, I've taken several liberties in adapting Max Raids into a single player environment. Because of this, this feature doesn't perfectly replicate how the main series portrays Max Raids, but the spirit behind the gameplay remains the same. You're still pitted up against a wild Dynamax Pokemon, and almost all of the gameplay elements from the main series (shields, capture mechanics, den spawns, etc) has been replicated as closely as possible, with details changed for balance adjustment purposes, or simply if I thought it would be more interesting/fun.

Several unique features not found in the main series' version of Max Raids are built into Raid events, such as Hard Mode raids, the ability to set custom rewards, reward bonuses for meeting certain challenges during the raid, a repurposed Cheer mechanic, and more.

Note that all Max Raid installations are optional, and aren't required to include if you don't intend on using them. All other ZUD functions will work perfectly fine if you choose not to install any of the ZUD_MaxRaid scripts.

Accessing a Max Raid Den

Spoiler:

Battling a Max Raid Pokemon

Spoiler:

Encountering G-Max Pikachu in a Max Raid Den.

Upon entering battle, you'll notice that Raid Pokemon have a unique databox. This displays special raid information, such as the turns and KO's you have remaining before the raid ends. If you fail to drop the Raid Pokemon's HP to 1 before the turn count ends, or before it has reduced its KO count to zero, then you will lose the raid and be kicked out. Both the turn count and KO count may fluctuate depending on the Raid's Rank, or other factors. If you're kicked out of a raid, you can come back and challenge the same Pokemon again.

You cannot switch Pokemon while in a Raid Battle, unless a Pokemon is KO'd and replaced. You're also unable to flee during raids, so plan ahead and use all the tools available to you to win.

After a certain point in the battle, the Raid Pokemon will begin attacking multiple times per turn. Raid Pokemon can attack once per turn for every Pokemon you have on the field. So if you fight the Raid Pokemon with 3 Pokemon at once, it'll attack three times per turn. Its first attack will always be a Max Move, with any follow-up attacks being one of its base moves. At the start of the fight, however, it'll only attack once per turn as usual.

Battle Mechanics

Raid Movesets
Spoiler:
Unlike normal Dynamax Pokemon, a raid Pokemon can use its base moves during battle in addition to its Max Moves. At the start of the battle, the raid Pokemon will only use one of its base moves each turn. But after its shields have been triggered, it will begin using its Max Moves as well.

Raid Pokemon have enhanced movesets that pull from every possible move it can learn; whether it be level-up moves, TM/TR's, Egg Moves, or Tutor Moves. A list of possible moves it can learn is generated, and the Raid Pokemon is given up to 4 random moves from that list that fall under the following criteria:
- Move 1: STAB Move
  The Raid Pokemon's first move will be a random compatible STAB move it may learn with a minimum of 80 BP. This adds some reliability to a Raid Pokemon's moveset, as it'll always have at least one powerful attack it can use against you.
- Move 2: Coverage Move
  The Raid Pokemon's second move will be a random compatible move it may learn with a minimum of 70 BP or higher. This move will be of a random non-STAB'd type, excluding Normal. This adds unpredictability to a Raid Pokemon's moveset, as it may often carry counters to types that would normally wall it.
- Move 3: Spread Move
  The Raid Pokemon's third move will be a random compatible spread move that hits 2 or more targets with a minimum of 55 BP or higher. This ensures the Raid Pokemon can strike multiple targets in larger raid sizes.
- Move 4: Support Move
  The Raid Pokemon's fourth move will be a random compatible status move. In most cases, this is usually a move that heals HP (Roost, Recover, Strength Sap, etc), but certain stat boosting moves or species-specific moves may be considered as well. This ensures a more difficult encounter, as the Raid Pokemon has guaranteed access to Max Guard as well as buffing itself in some way.
In addition to all of the above, some species will always spawn with specific moves. Rotom Forms are a great example of this, as they will always spawn with their form-exclusive move. This is handled in the ZUD_MaxRaid_02_Events script, under pbCustomRaidSets. You can add any custom moves here for specific species, and those species will always spawn with those moves. These moves that priority over the randomized moves the Raid Pokemon may be given.
Raid Shields

Spoiler:

Electivire triggering its first round of raid shields after its HP reached a certain threshold.

When the Raid Pokemon's HP drops to half its total hp, it will become shielded by a mysterious barrier. While behind this shield, Raid Pokemon take significantly reduced damage from your attacks, and become completely immune to your status moves. The Raid Pokemon is also immune to additional effects of your moves while behind their shield, so moves that have a chance to burn or lower stats, etc. won't ever activate those additional effects. Max Moves ignore this however, and will still activate their secondary effects through the Raid Pokemon's shields. You must break their shield before you can resume dealing normal damage to them. The number of hits a Raid Pokemon's shields need to be broken scales with the difficulty level of the raid. Any damaging move will reduce the Raid Shield by 1 bar, regardless of the strength of the move. However, Max Moves used by a Dynamax Pokemon will reduce these shields by 2 bars per hit. When a Raid Pokemon's shield is broken, their Defense and Sp.Def will drop by two stages, as well as taking a small portion of damage.

In higher difficulty raids, the Raid Pokemon may activate two rounds of shields. The first round will be triggered when its HP drops to 4/5ths or below of its total HP, with the second round triggering at half HP as before. Planning out when to utilize your Dynamax turns plays a more crucial role in these higher raids, since the raid timer becomes more difficult to manage when you have two separate rounds of shields to deal with.

If a Raid Pokemon protects itself by way of Max Guard, it will prevent any shield damage too. However, I made it so that if you're battling a raid Pokemon in a 1v1 setting, Max Moves will still slightly penetrate Raid Shields through Max Guard, removing 1 bar from the shield. This is to help balance smaller raid encounters a bit.

NOTE: In Debug Mode, if you hold CTRL while attacking a Raid Pokemon's shield, the attack will instantly deplete the entire Raid Shield.
Wave Attacks
Spoiler:
Weavile unleashing its Neutralizing Wave attack.

In addition to shields, Raid Pokemon have access to another mechanic that I've simply called "Wave Attacks". In the main series, only one such wave attack exists. What this did was not only nullify your Pokemon's ability, but also undo any positive stat changes it may have. In addition to this, this effect would also clear away any status conditions the raid Pokemon may have had. I have replicated this mechanic here, and Raid Pokemon will periodically utilize this wave attack during battle. However, I have added three additional wave attacks that I custom built for Hard Mode raids.
- Neutralizing Wave (Standard)
  This is the main wave attack taken from the main series, with the effects outlined above. A Raid Pokemon won't start using this until its taken around a quarter of its HP worth of damage. Once it has, it has a 20% chance each turn to begin the round with this wave attack. The odds of the Raid Pokemon using this will increase if it has its shields up, or if it's suffering from a status condition. Unlike the main series, I've also made it so that this wave attack will also remove the Attract and Leech Seed effects from the Raid Pokemon. Both of these effects proved to be a bit too strong vs a single target, so I added some counterplay for Raid Pokemon to negate them.
  
  This wave attack can be performed multiple times in a battle, even during the same turn that a different wave attack is performed. This wave attack has the highest priority, and will always come out first before the others, or before the Raid Pokemon even attacks.
- Malicious Wave (Hard Mode)
  This wave attack occurs every time the Raid Pokemon uses a damaging move while its shields are down. The power behind its attack is so high that it causes shockwaves that ripple through the den, causing a second hit of additional damage to your Pokemon after the Raid Pokemon attacks. This damage cannot be blocked and will hit through most effects. This will still harm your Pokemon even if the initial attack used by the Raid Pokemon missed, or was ineffective. The damage dealt by this wave attack is equal to 1/16th your Pokemon's total HP. However, this damage doubles to 1/8th if the Raid Pokemon has exhausted all of its shields.
- Invigorating Wave (Hard Mode)
  This wave attack is a once-per battle buff that triggers once the Raid Pokemon drops to 1/2 its total HP or less. If so, it will release this wave attack to boost all of its stats by 1 stage. This ignores the reverse effects of the Contrary ability.
- Immobilizing Wave (Hard Mode)
  This wave attack is a Raid Pokemon's final desperate attempt to stop your victory. Once per battle, if all of the Raid Pokemon's shields have been exhausted, it releases an immense wave that can immobilize your Pokemon, forcing them to skip their action this turn. This may snatch a victory away from you by eating up a precious turn of the raid timer. Dynamax Pokemon are immune to this wave attack, however. So it's often a better idea to save your Dynamax till the endgame of the battle when playing in a Hard Mode raid. This wave attack won't do anything if you happen to use a different action that turn besides using a move.
Although not necessarily a Wave Attack in the traditional sense, the Raid Pokemon will also suppress your ability to switch Pokemon by releasing constant waves of Dynamax Energy. These waves of energy will also deflect any Poke Balls thrown at the Raid Pokemon until they're weakened enough to be caught.
Hard Mode
Spoiler:
Hard Mode raid featuring G-Max Appletun.

Any raid also has the potential to be challenged under Hard Mode rules. This is a unique mechanic for this script that isn't found in the main series. Hard Mode amps up the challenge of your raid battles a bit, making them tougher battles that sometimes require higher levels of strategy and game awareness to overcome. The Raid Pokemon have a variety of new tools and effects to play with under Hard Mode settings, as well as stronger shields and larger HP pools. There will be an icon in the top right hand corner of the raid's entry screen to indicate that this is a Hard Mode raid.

Keep in mind that when challenging a Legendary Raid (Rank 6), these raids will always be challenged under Hard Mode rules, regardless of whether it was set or not.
- Increased Stamina
  In Hard Mode, the Raid Pokemon will have their health pools increased by an additional 10% for each star of the raid's Rank. So a Raid Pokemon found in a 5 Star raid will have 50% additional HP in a Hard Mode Raid. In addition to this, Raid Pokemon will have 1 extra bar of shield HP when they activate their shields in Hard Mode.
- Bonus Wave Attacks
  In Hard Mode, the Raid Pokemon have three additional Wave Attacks it may use during the fight that it wouldn't normally have access to. These additional attacks are outlined in the Wave Attacks section above.
- HP Regeneration
  While a Raid Pokemon's shields are up in Hard Mode, it will recover 1/16th of its total HP at the end of each turn until its shields are broken. This puts extra pressure on you to blow through these shields asap, to prevent the Raid Pokemon from recovering back too much HP. This healing can be negated with Heal Block, however.
- KO Boost
  Each time a Raid Pokemon KO's one of your Pokemon, it will grow in power, gaining +1 Attack and Sp. Atk. This stacks with abilities like Moxie. This effect can quickly cause a Raid Battle to snowball out of your control, and places extra emphasis on valuing defense as much as offense. Sometimes its worth taking up a turn healing or protecting, or even activating Dynamax early to prevent any unnecessary KO's.
- Capture Resistance
  Normally, capturing a raid Pokemon after defeating it has a 100% capture chance. In Hard Mode raids, however, you only have a 20% chance of successfully capturing the Pokemon upon defeating it.
Cheering
Spoiler:
Selecting the Cheer command during a Max Raid Battle.

In the main series, when your Pokemon is KO'd during a raid, you will have to wait one turn before it is revived and sent back out. During this turn, your only available command is to Cheer your allies, which may grant them a variety of random buffs, or even destroy the raid Pokemon's shield. While this mechanic doesn't exactly translate to this version of Max Raids due to being single-player, I have adapted this mechanic to work slightly differently here to give the player some interesting options during a raid.

In battle, the Run command is replaced with Cheer. Selecting this command will skip the turn for that Pokemon, and instead you will use that turn to cheer them on. Cheering a Pokemon can grant a variety of random effects, but you can utilize Cheering in a way that allows you to somewhat control which effect is used. Cheering will have no effect, however, until at least one of your Pokemon have been KO'd. The closer you are to losing a raid, the more useful the effects Cheering may have. Because of this, you can utilize Cheer as a come-back mechanic when you're losing a raid.

Unlike the main series, the strength of a Cheer will stack depending on how many Pokemon you cheer for in a single round. So if you select Cheer for two Pokemon in a single turn, the effects of the Cheer will change versus the effects of a single Cheer. This can stack up to 3 times. Triple Cheers have the strongest and most influential effects.
- Single Cheer
  If you cheer for a single Pokemon in a turn, one of the following effects may randomly occur:
  
  Reflect is set up on your party for 5 turns. This effect is never selected if Reflect is already in play.
  
  Light Screen is set up on your party for 5 turns. This effect is never selected if Light Screen is already in play.
  
  Each ally Pokemon have a random stat increased by a single stage.
  
  The cheer goes off with a whimper, and fails. No effect happens.
- Double Cheer
  If you cheer for two Pokemon in a turn:
  
  If any of your active Pokemon are greatly injured, and have less than 50% of its total HP remaining, all ally Pokemon will have their HP fully restored, and their status cured.
  
  If all your Pokemon are healthy, this Cheer will instead sharply raise a random stat of each ally Pokemon by 2 stages.
- Triple Cheer
  If you cheer for three or more Pokemon in a turn:
  
  If your Dynamax was already used this battle and no longer active, your cheering will recharge your Dynamax Band, allowing you to Dynamax once more.
  
  If the above effect cannot be used, and the Raid Pokemon has a raid shield up, your cheering will shatter the opponent's entire shield and remove it from play.
  
  If neither of the above effects can be used, this Cheer will instead drastically raise a random stat of each ally Pokemon equal to the number of Cheers used this round (3+).
By utilizing Cheer in certain situations, you can completely change the tide of a losing battle. Is your party low on health and your healer is KO'd? A Double Cheer will patch them all up, without having to waste several precious turns using potions. Did the Raid Pokemon pop its raid shields when you don't have enough turns left to feasibly defeat it in time? Maybe a Triple Cheer will help even the odds by removing it. Did you accidentally enter a raid with Magikarp as one of your leads? Well, at least something potentially useful can be done with its turns by using Cheer. Use Cheer as a way of clutching victory when the odds are stacked against you.

Also, something to keep in mind - If you're in a raid with less than three active Pokemon, using a Single/Double Cheer will sometimes grant the stronger effects of a Double or Triple Cheer, but only when the situation is dire (The Raid Pokemon's KO Counter is down to 1, or there's less than 5 remaining turns before you're kicked out of the raid). So when all hope is lost and you see no way of winning a raid in time, sometimes spamming Cheer can come in clutch and save the day.

NOTE: While in Debug Mode, while holding CTRL, selecting Cheer will function like Run instead, allowing you to escape from raid battles. Running from raids is only possible in Debug Mode.
Capturing

Spoiler:

Capture prompt upon defeating the Max Raid Pokemon.

Raid Pokemon will deflect any Poke Balls thrown at them until they're weak enough to be caught. To weaken a Raid Pokemon, you must battle it until its HP is depleted. This will not cause the Raid Pokemon to faint, however, only weaken it so that it's in a capturable state. Once in this state, you will be prompted to throw a Poke Ball at the weakened Pokemon and immediately be brought to the ball pocket in your bag. This is the only time during the battle where a Raid Pokemon may be caught.

After selecting a ball, you will throw it and capture the Pokemon. Raid Pokemon have a 100% capture rate while in this weakened state. However, in Hard Mode, the Pokemon only has a 20% capture rate, regardless of ball (except Master Ball). If the raid Pokemon fails to be caught, or if you choose not to capture it, the Pokemon will flee into the depths of the den. Whether you capture the raid Pokemon or not, you will be rewarded upon exiting the raid.

NOTE: While in Debug Mode, while holding CTRL, you can bypass the Raid Pokemon's ball deflection and capture the Pokemon during any point of the battle.

Completing a Max Raid

Spoiler:

The rewards screen after defeating Gengar in a Max Raid Den.

Upon completing a Raid, you will be taken to the results screen. If the Raid was completed, this will display the Pokemon and its level/ability (if caught), as well as all the rewards you gained from completing the raid. Raids will usually yield various candies, EV Reducing Berries, Vitamins, various training items (Ability Capsule, Bottle Caps, etc), and may also include expensive valuables to sell. You earn no rewards if you were defeated by the Raid Pokemon.

I've also implemented a handful of new custom items as incentives to clearing raids that can be obtained under certain conditions.

Raid Rewards

Rewards By Rank
Spoiler:
The type of rewards you'll find in each raid varies based on the rank of the raid. Some rewards only start appearing when completing higher ranked raids. The rewards stack, so Rank 2 may yield all of Rank 1's rewards in addition to its own, for example. The quantity of each reward also scales based on the rank of the raid (some items are locked into only yielding 1 per raid, however). Some items are also not guaranteed to appear.
- Rank 1
  
  Exp. Candy XS, Exp. Candy S
  
  EV Reducing Berries
- Rank 2 or higher
  
  Rare Candies
  
  Dynamax Candies
- Rank 3 or higher
  
  Exp. Candy M
  
  Vitamins
  
  Technical Records*
  
  Uncommon valuables (Tiny Mushroom, Relic Copper, etc.)
  
  Max Soup (only if 5 Raid Reward Bonuses are earned)
  
  Dynamax Candy XL (only if 5 Raid Reward Bonuses are earned)
- Rank 4 or higher
  
  Exp. Candy L
  
  PP Up
  
  Rare valuables (Big Mushroom, Relic Silver, etc.)
- Rank 5 or higher
  
  Exp. Candy XL
  
  PP Max
  
  Ability Capsule, Ability Patch
  
  Bottle Cap, Gold Bottle Cap
  
  Very Rare valuables (Balm Mushroom, Relic Gold, etc.)
*As like in the main series, Max Raids reward TR's upon completion. The particular TR you receive depends on the type of the Raid Pokemon, and will be a move that matches one of its types. If no appropriate TR exists, or no TR's are installed, no item will be awarded. Only 1 TR will be awarded per raid, and they will only be found in raids beginning at Rank 3 or higher.
Raid Reward Bonuses
Spoiler:
Clearing a Samurott raid with all five Raid Reward Bonuses in tact.

The quantity of rewards received for completing a raid fluctuate based on a unique mechanic known as Raid Reward Bonuses. You can earn up to five different Raid Reward Bonuses upon completing a raid. For each bonus earned, the quantity of any earned rewards increases. You earn bonuses based on how well you performed in the raid, or completing the raid under certain conditions.

Here's a breakdown of all the bonuses that may be gained upon completing a raid:
- Hard Mode: This bonus is awarded if the raid was cleared on the Hard Mode difficulty.
- Perfect: This bonus is awarded if you cleared the raid without a single Pokemon being KO'd.
- Timer: This bonus is awarded if you cleared the raid before the raid timer dropped below half.
- Fair Fight: This bonus is awarded if you defeated the Raid Pokemon without using any Pokemon in battle that out-level the raid Pokemon by more than 5 levels.
- Capture: This bonus is awarded if you successfully captured the Raid Pokemon.
If you clear the raid with all five bonuses in tact, you will receive an additional bonus reward of either a Max Soup, or a Dynamax Candy XL. This is the only way to naturally obtain these items. You may only receive one of these bonus items per raid.
Unique Rewards
Spoiler:
Max Honey rewarded from clearing a Vespiquen raid with at least three Raid Reward Bonuses in tact.

Certain rewards will only be given out when defeating a Max Raid Pokemon of a particular species. In the main series, you may only find Max Honey when defeating Vespiquen in a Max Raid. I've not only included this, but expanded upon it by introducing more Max Items for particular species that fits their theme.

Here are the additional item drops:
- Max Mushrooms: This is rewarded only when defeating a fully-evolved mushroom Pokemon in a Max Raid. This includes Parasect, Breloom, Amoongus, and Shiinotic.
- Max Eggs: This is rewarded only when defeating Blissey in a Max Raid.
- Max Scales: This is rewarded only when defeating Luvdisc in a Max Raid.
- Max Plumage: This is rewarded only when defeating certain fully-evolved birds of prey Pokemon in a Max Raid. This includes Fearow, Noctowl, Staraptor, Braviary, Mandibuzz, and Talonflame.
These unique rewards will only drop if you earned at least three raid bonuses upon clearing the raid.
Environmental Rewards
Spoiler:
Luminous Moss is added to the loot table for raids that take place in the Cave environment.

In addition to all of the above, you may also receive rewards based on a variety of battle conditions. The weather during a raid, or the terrain, or even the environment may all effect which additional items have a chance of appearing in the raid's loot table.
- Weather
  
  Heat Rock (Sunny)
  
  Damp Rock (Rain)
  
  Smooth Rock (Sandstorm)
  
  Icy Rock (Hail)
- Terrain
  
  Electric Seed (Electric Terrain)
  
  Grassy Seed (Grassy Terrain)
  
  Misty Seed (Misty Terrain)
  
  Psychic Seed (Psychic Terrain)
- Environment
  
  Absorb Bulb (Grass)
  
  Power Herb (Tall Grass)
  
  Mystic Water (Moving Water)
  
  Fresh Water (Still Water)
  
  Float Stone (Puddle)
  
  Shoal Shell (Underwater)
  
  Luminous Moss (Cave)
  
  Hard Stone (Rock)
  
  Light Clay (Sand)
  
  Shed Shell (Forest)
  
  Mental Herb (Forest Grass)
  
  Snowball (Snow)
  
  Never Melt Ice (Ice)
  
  Bright Powder (Volcano)
  
  Rare Bone (Graveyard)
  
  Pretty Wing (Sky)
  
  Stardust (Space)
  
  Enigma Berry (Ultra Space)
Custom Rewards

Spoiler:

Icon indicating a custom reward on the Raid Entry screen.

You can add custom rewards to individual raid dens when setting up your Raid events (more on this in the next section). Any item ID or number you enter will add 1 of those items to the loot table of that raid event. You can also add a quantity if you want more than one of those items to be added. When accessing a raid, an icon will be displayed in the top right corner indicating that this raid has a unique custom reward for completing it. Custom rewards will always be the last item displayed in the rewards list upon completing the raid.

How to set up a Max Raid.

Spoiler:

Page 1 & 2 of a basic Max Raid Den event.

Raid Dens can be set up using a simple script, pbMaxRaid. The image above depicts what a simple Raid Den should look like. The first page triggers the raid event, and the second page is for handling the resetting of the den after enought time has elapsed.

However, this script can be expanded upon to create a host of unique raid configurations. By plugging in several arguments in the pbMaxRaid script, you can customize the species, rank, and a variety of other conditions of each individual raid event. Here's the full list of arguments that can be inputted:

Code:

pbMaxRaid(size,rank,pkmn,loot,field,gmax,hard)

What each argument does:

Size

Spoiler:

By default, Raids will be fought in a 3v1 format. However, this is completely customizable and you can set up raids to work under 1v1 or 2v1 battle styles instead. If you're using Modular Battle Scene, this can be scaled up to 4v1 or even 5v1 battles, too.

This can be done in one of two ways. The first way is to go into the settings and set MAXRAID_SIZE from 3 to your desired size. This will cause all raids to default to that size. Alternatively, you can set individual raid events to utilize specific battle sizes with the "size" argument in the pbMaxRaid script. Setting this to a number will force the raid to be fought under the chosen battle format, overriding the default. If you set "size" to nil, it will just return the default battle size.

The size of the raid can be determined by the layout of the raid's entry screen. Above the "View Party" button, all the Pokemon that will lead the battle versus the Raid Pokemon will be displayed here. This layout will change based on the raid size.

Certain raid mechanics will scale differently depending on the size of the raid you choose. For example, the raid timer will scale with the battle size. 1v1 raids offer you the most time to complete them, since you have fewer opportunities to break the Raid Pokemon's shields. You have slightly less turns available in 2v1 formats, and battle sizes 3 or higher always offers the base amount of turns. You will also receive slightly more rewards for participating in larger raid sizes.

If you enter a raid with less able Pokemon in your party than needed to fit the raid size, the raid will automatically scale down to accommodate your party. For example, if you enter a 3v1 raid with only 2 usable party members, the raid will automatically scale down to a 2v1 battle. If you input a raid size that is higher than 3 when you don't have Modular Battle Scene installed, the raid will automatically scale down to 3.

Note: In 1v1 formats, the Raid Pokemon will lose Raid Shield HP if it is struck by a Max Move while under the effects of Max Guard. This effect will not occur in larger battle sizes, however, so keep that in mind.
Rank
Spoiler:
This decides the rank of the raid, which dictates the level range of the raid Pokemon and the overall difficulty of the raid. You can set this to a number from 1-6, with 1-5 being the number of stars the raid has, and 6 being exclusively used for Legendary Raids. If you leave this argument set to "nil", this will instead choose a random rank for the raid based on your badge count. Level 6 will never be selected in this way, however, only raid levels 1-5. If you have 6 or more badges, 1 Star raids will no longer randomly appear. If you have 8 or more, then 2 Star raids will stop appearing too. However, you can manually force a raid rank outside the range of your badge count when you input a specific number.

If the species you entered to spawn in the raid is not naturally found in the Rank you entered, the Rank will automatically scale to suit that species, and ignore what you've inputted here. For example, if you try to spawn a Rattata in a Rank 5 raid, the Rank of the raid will automatically scale down to Rank 2, since that's the highest rank Rattata can appear in.

The strength of a Pokemon scales based on the raid's Rank. Here are the level ranges and other information for the Pokemon found in each Rank:
- Rank 1
  
  The raid Pokemon's level will be between 15-20.
  
  The raid Pokemon is guaranteed to have at least 1 perfect IV.
  
  The raid Pokemon's HP is boosted by 25%.
  
  The raid Pokemon's Shield HP will be equal to whatever MAXRAID_SHIELD is set to.
- Rank 2
  
  The raid Pokemon's level will be between 30-35.
  
  The raid Pokemon is guaranteed to have at least 2 perfect IV's.
  
  The raid Pokemon's HP is boosted by 50%.
  
  The raid Pokemon's Shield HP will be equal to MAXRAID_SHIELD + 1.
- Rank 3
  
  The raid Pokemon's level will be between 40-45.
  
  The raid Pokemon is guaranteed to have at least 3 perfect IV's.
  
  The raid Pokemon has a 20% chance of appearing its G-Max Form, if any.
  
  The raid Pokemon's HP is boosted by 100%.
  
  The raid Pokemon's Shield HP will be equal to MAXRAID_SHIELD + 2.
  
  The raid Pokemon has two rounds of shields.
- Rank 4
  
  The raid Pokemon's level will be between 50-55.
  
  The raid Pokemon is guaranteed to have at least 4 perfect IV's.
  
  The raid Pokemon has a 20% chance of having its Hidden Ability, if any.
  
  The raid Pokemon has a 30% chance of appearing its G-Max Form, if any.
  
  The raid Pokemon's HP is boosted by 150%.
  
  The raid Pokemon's Shield HP will be equal to MAXRAID_SHIELD + 3.
  
  The raid Pokemon has two rounds of shields.
- Rank 5
  
  The raid Pokemon's level will be between 60-65.
  
  The raid Pokemon is guaranteed to have at least 5 perfect IV's.
  
  The raid Pokemon has a 50% chance of having its Hidden Ability, if any.
  
  The raid Pokemon has a 50% chance of appearing its G-Max Form, if any.
  
  The raid Pokemon's HP is boosted by 200%.
  
  The raid Pokemon's Shield HP will be equal to MAXRAID_SHIELD + 4.
  
  The raid Pokemon has two rounds of shields.
  
  The raid Pokemon's KO counter is reduced by 1.
- Rank 6
  
  The raid Pokemon will be level 70.
  
  The raid Pokemon is guaranteed to have flawless IV's.
  
  The raid Pokemon has a 80% chance of having its Hidden Ability, if any.
  
  The raid Pokemon has a 50% chance of appearing its G-Max Form, if any.
  
  The raid Pokemon's HP is boosted by 250%.
  
  The raid Pokemon's Shield HP will be equal to MAXRAID_SHIELD + 5.
  
  The raid Pokemon has two rounds of shields.
  
  The raid Pokemon's KO counter is reduced by 1.
  
  Hard Mode features enabled, and cannot be changed. This boosts HP by an additional 60%, and adds an additional bar to Shield HP.
Note: For all raid ranks, the raid Timer is equal to whatever MAXRAID_TIMER is set to. However, for raid sizes smaller than 3, additional turns are added to the Timer based on the Rank of the raid, as well as the size of the raid. The KO Counter for all raids is equal to whatever MAXRAID_KOS is set to. However, in raids Rank 5 & 6, the KO Counter will always be reduced by 1.
Pkmn
Spoiler:
You have many different ways of generating species for raid events. The simplest method is to have your raid event spawn a specific species by simply setting the "pkmn" argument to a specific species name. This will make it so that raid event will only ever generate that species. You can force specific forms of entered species by including their form number, too.

Examples:
- Entering a species name:
  
  Spoiler:
  
  Code:
  
  pbMaxRaid(nil,1,:MEOWTH)
  
  This will create a 1-Star Raid Den versus Meowth.
  Note: If you enter a banned species, or a species that doesn't exist, the raid will spawn a Ditto instead.
  
  Details on banned species:
  
  Spoiler:
  
  Certain species are excluded from appearing in raids for balance or gameplay reasons. The following species cannot be spawned in raids:
  
  Smeargle
  
  Shedinja
  
  Type: Null
  
  Cosmog
  
  Cosmoem
  
  Poipole
  
  Meltan
  
  Zacian
  
  Zamazenta
  
  Kubfu
  
  Note that Eternatus isn't banned, despite being unable to Dynamax (like Zacian/Zamazenta). If spawned in a raid, Eternatus will always spawn in its Eternamax form. Base Eternatus cannot be encountered in raids, however.
- Entering a species name and form number:
  
  Spoiler:
  
  Code:
  
  pbMaxRaid(nil,1,:MEOWTH_1)
  
  This will create a 1-Star Raid Den versus Alolan Meowth, since form 1 of Meowth is Alolan Meowth.
  Note: If you enter an ineligible form, or a form that doesn't exist, the base form of the species will spawn instead.
  
  Details on specific forms:
  
  Spoiler:
  
  Some forms are excluded from being set in raids. This is handled on a species to species basis. For example, Mega Forms, Primals, and forms that only activate while in battle, such as Zen Mode Darmanitan or Ash-Greninja cannot be set as a raid species, and will simply return the base species instead if set. Other specific cases such as Eternal Flower Floette are banned as well.
  
  Here's a full list of all the forms that ARE allowed, and CAN be set as a raid species:
  
  All Alolan forms
  
  All Galarian forms
  
  All Unown forms*
  
  All Deoxys forms*
  
  All Burmy/Wormadam forms
  
  Both Shellos/Gastrodon forms*
  
  All Rotom forms*
  
  Shaymin Sky Forme*
  
  Both Basculin striped forms*
  
  Both Incarnate and Therian forms for Tornadus, Thundurus, and Landorus*
  
  All Vivillon patterns.
  
  All Furfrou trims.
  
  All flower forms for Flabebe, Floette, and Florges (except Eternal Flower Floette)*
  
  All Pumpkaboo/Gourgiest sizes*
  
  Zygarde 10% Form
  
  Hoopa Unbound*
  
  All Rockruff/Lycanroc forms.
  
  All Oricorio forms*
  
  Minior Meteor forms (0-6 only)*
  
  Both fake and antique forms for Sinistea/Polteagiest
  
  Both Toxtricity forms
  
  Both Urshifu forms*
  
  If any form DOESN'T appear on the above list, it cannot be forced to spawn in a raid.
  
  Forms that are automatically chosen:
  
  Spoiler:
  
  Deerling/Sawsbuck will only ever spawn in the form that suits the season, regardless of what form is set.
  
  Pokemon with male/female forms, such as Meowstic and Indeedee will only spawn in the form that matches the gender they spawn with.
  
  Burmy/Wormadam forms will naturally spawn in the form that suits its environment, or the environment the raid was set to. However, setting a specific form for these Pokemon will override this.
  
  Rockruff/Lycanroc will naturally spawn in the form that suits the time of day. However, setting a specific form for these Pokemon will override this.
  
  Any Pokemon marked with (*) in the above list will spawn in a completely random form if only the base species is set.
  Example:
  
  Spoiler:
  
  If you set an Unown raid, such as:
  
  Code:
  
  pbMaxRaid(nil,1,:UNOWN)
  
  Then Unown will spawn in any of its 28 possible forms. But if you set an Unown raid with a specific form, such as:
  
  Code:
  
  pbMaxRaid(nil,1,:UNOWN_25)
  
  Then Unown will only ever spawn in form 25 (Letter Z form).
  
  Shaymin's forms will only randomize during the day. At night, only its base form will appear.
- Entering a species number:
  
  Spoiler:
  
  Some Pokemon, such as Rotom or Deoxys, will always spawn in a random form if only the base species is entered. For example:
  
  Code:
  
  pbMaxRaid(nil,6,:DEOXYS)
  
  Will randomly spawn Deoxys in its Normal, Attack, Defense, or Speed forms. You can control which individual form spawns in the same manner as the Meowth example above. However, how do your force the base form to only appear, if inputting the base species always causes the forms to randomize? Simple. Just enter the species's National Dex number instead.
  
  Code:
  
  pbMaxRaid(nil,6,386)
  
  This will create a Legendary Raid versus Deoxys, however Deoxys will only ever spawn in its base form, and never randomize between its other forms.
- Entering a species as an array:
  
  Spoiler:
  
  There is yet another way to enter a species for raids, but this method allows you to randomize what species will appear based on multiple factors. You can use this to create raids that will cycle through different random species each time the raid resets. You can apply up to three different filters (Type, Habitat, Regional Dex) to narrow down the scope of which species may be randomly generated. Or, you can apply no filters at all and have the raid randomly select from any species in the National Dex that suits the raid's Rank.
  
  Details on how to use each filter:
  
  Spoiler:
  
  Filter 1: Type
  The first item in the array filters species by type. So for example:
  
  Code:
  
  pbMaxRaid(2,3,[:FIRE])
  
  This will create a 2v1 3-Star raid versus a random Fire-type Pokemon. Note that forms of certain Pokemon are considered, too. So Rotom-Heat and Balie Style Oricorio will both be eligible to randomly appear in this raid due to being Fire-types, but their other forms will not appear.
  
  Filter 2: Habitat
  The second item in the array filters species by their listed Habitats. Habitat data is found in the Pokemon's PBS data, and breaks down each species into different categories based on where they appear in nature (Cave, Sea, Forest, etc.). This is a feature that only existed in Gen 3, so species in later Gens do not have any Habitat data. However, I included an updated PBS file in the download link that adds Habitat data to every species up through Gen 8.
  
  Here is a reference of all the habitats and their numbers:
  ⦁ 0 - None
  ⦁ 1 - Grassland
  ⦁ 2 - Forest
  ⦁ 3 - Water's Edge
  ⦁ 4 - Sea
  ⦁ 5 - Cave
  ⦁ 6 - Mountain
  ⦁ 7 - Rough Terrain
  ⦁ 8 - Urban
  ⦁ 9 - Rare
  
  Here's an example of a raid den utilizing Habitats:
  
  Code:
  
  pbMaxRaid(1,1,[nil,5])
  
  This will create a single battle 1-Star raid versus a random species found in the Cave habitat (Habitat 5). This includes species such as Zubat, Diglett, and Gible.
  
  Here's an example of a raid den filtering species by both Type and Habitat:
  
  Code:
  
  pbMaxRaid(3,5,[:BUG,2])
  
  This will create a 3v1 5-Star raid versus a random Bug-type species found in the Forest habitat (Habitat 2). This includes species such as Heracross, Yanmega, and Scolipede.
  
  Filter 3: Regional Dex
  The final item in the array filters species by their appearance in certain regional dexes. This is also taken from the Pokemon's PBS data. By including this filter, you can ignore species that don't appear in certain regions from being randomly selected as a raid species. By default, Essentials uses dex "0" for the Kanto Dex, and dex "1" for Johto. Your game may use different numbering/dexes, so keep that in mind with the examples below.
  
  Here's an example of a raid den filtering species by Regional Dex:
  
  Code:
  
  pbMaxRaid(1,1,[nil,nil,0])
  
  This will create a single battle 1-Star raid verses a random species found only in the Kanto Dex (Dex 0)
  
  Here's an example of a raid den filtering species with all three filters in place:
  
  Code:
  
  pbMaxRaid(3,5,[:WATER,3,1])
  
  This will create a 3v1 5-Star raid versus a random Water-type species found in the Water's Edge habitat (Habitat 3), and only appears in the Johto Dex (Dex 1). This includes species such as Poliwrath, Politoed, Slowbro, and Slowking.
- How to randomly choose a species from a set list of species:
  
  Spoiler:
  
  If you want to randomize which species appears in your raids, but want to randomly choose out of a set list of species you determine, rather than using the filtering method described above, you can do so like this.
  
  Example:
  
  Code:
  
  poke = [:BULBASAUR,:CHARMANDER,:SQUIRTLE] randpoke = poke.shuffle.first pbMaxRaid(1,2,randpoke)
  
  This will create a single battle 2-Star raid versus a random Pokemon that was set in the "poke" array. In this case, Bulbasaur, Charmander, or Squirtle.
  
  You can enter a Pokemon in the array in any method described in this tutorial so far. So if you want to get really fancy, you could even do something like this:
  
  Code:
  
  poke = [:LUGIA,:SHAYMIN_1,386,[:FIRE],[nil,9]] randpoke = poke.shuffle.first pbMaxRaid(3,6,randpoke)
  
  This will create a 3v1 Legendary Raid versus a random Pokemon that may include Lugia, Shaymin Sky Forme (reverts base form at night), Deoxys (base form only), a random Fire-type Legendary, or a random Legendary found in the "Rare" habitat.
Spoiler:

So with the above methods, you have a bevy of options for generating species for your Max Raids. Set the species name to make that specific species to appear (with its form automatically chosen with certain species). Set the species name with its form number to make a specific species appear in a specific form. Or, set the species as a dex number to make it so only the base form of that species ever appears.

If you want to randomize the species that may appear in the den, you can filter species by Type, Habitat, and Regional Dex by entering the species as an array. Or, you can set up an array of specific species of your choosing, and randomize between those.
Loot
Spoiler:
You can set this as a name or number of a particular item to add 1 of that item to the raid's loot table. Leaving this set to nil won't add any bonus rewards. If you set this as an array, the first item in the array will be the item you receive, and the second item in the array will be the quantity of that item. When accessing a raid that has specialized bonus rewards, a unique icon will be displayed on the top right corner of the entry screen to indicate this.

Basic Examples:
Spoiler:

Code:

pbMaxRaid(nil,4,:CHANSEY,:LUCKYEGG)

This will create a 4-Star Raid Den versus Chansey that will reward you with a Lucky Egg.

Code:

pbMaxRaid(nil,5,:SALAMENCE,[:DRAGONFANG,2])

This will create a 5-Star Raid Den versus Salamence that will reward you with 2 Dragon Fangs.
Advanced Examples:
Spoiler:

If you want there to be multiple items that can be found as bonus loot in a raid, you can set up an array of different items and randomly select one of them to be entered in the pbMaxRaid script.

Code:

loot = [:ORANBERRY,:SITRUSBERRY,:LUMBERRY] randloot = loot.shuffle.first pbMaxRaid(nil,2,:MUNCHLAX,randloot)

This will create a 2-Star Raid Den versus Munchlax that will reward you randomly with an Oran Berry, Sitrus Berry, or Lum Berry upon clearing the raid.

You can randomize the quantity of the item too, and do something like this to add a randomized item in a randomized amount:

Code:

loot = [:HEALTHWING,:MUSCLEWING,:RESISTWING,:GENIUSWING,:CLEVERWING,:SWIFTWING] randloot = loot.shuffle.first randqty = 1+rand(20) pbMaxRaid(nil,3,:PIDGEOT,[randloot,randqty])

This will create a 3-Star raid versus a Pidgeot, which will reward a random wing item listed in the "loot" array, at a random amount between 1-20.
Field
Spoiler:
You have the option of setting specific battlefield conditions for each Raid Den. There are three possible conditions to set: Weather, Terrain, and Environment. You can use these to customize the overall theme of the raid, or set up interesting and unique challenges for specific raids.

By default, raid dens are set with these conditions: No weather, no terrain, Cave environment. This is what you'll get if you set the "field" argument to nil, or omit it.
- Entering an Environment:
  
  Spoiler:
  
  When you set "field" to a number, however, the default environment of the raid will change to reflect the environment associated with that number.
  
  Here's a reference for all the environment numbers:
  
  Spoiler:
  
  ⦁ 0 - None (Displays as "Urban")
  ⦁ 1, 2 - Grass, Tall Grass (Displays as "Grassland")
  ⦁ 3, 4 - Moving Water, Still Water (Displays as "Aquatic")
  ⦁ 5 - Puddle (Displays as "Wetlands")
  ⦁ 6 - Underwater
  ⦁ 7 - Cave (Displays as "Cavern")
  ⦁ 8 - Rocky (Displays as "Earth")
  ⦁ 9 - Sand (Displays as "Sandy")
  ⦁ 10, 11 - Forest, Forest Grass (Displays as "Forest")
  ⦁ 12, 13 - Snow, Ice (Displays as "Frosty")
  ⦁ 14 - Volcano (Displays as "Volcanic")
  ⦁ 15 - Graveyard (Displays as "Spiritual")
  ⦁ 16 - Sky
  ⦁ 17 - Space
  ⦁ 18 - Ultra Space
  
  Example:
  
  Code:
  
  pbMaxRaid(nil,5,:KINGDRA,nil,6)
  
  This will create a 5-Star raid versus Kingdra in the Underwater environment (Environment 6).
  
  The background graphics in battle will change to reflect the inputted environment. So if you set the Environment to 9, you'll use the Sand battle bases and backdrop, letting you set up a Raid with a desert theme. By default, Essentials doesn't come with graphics associated with the Sky, Space, or Ultra Space environments, so please install some of your own if you plan on using those environments (otherwise the background will just be black).
- Entering Weather & Terrain:
  
  Spoiler:
  
  However, if you want to set weather and terrain in addition to the environment, you must set this as an array. In this array, the first item will handle weather, the second will handle terrain, and the third will handle environment. Set a number for each item in the array that corresponds to a particular Weather/Terrain.
  
  Here's a reference for all the weather/terrain numbers:
  
  Spoiler:
  
  Weather
  ⦁ 0 - Clear skies
  ⦁ 1 - Sun
  ⦁ 2 - Rain
  ⦁ 3 - Sandstorm
  ⦁ 4 - Hail
  
  Terrain
  ⦁ 0 - No terrain.
  ⦁ 1 - Electric Terrain
  ⦁ 2 - Grassy Terrain
  ⦁ 3 - Misty Terrain
  ⦁ 4 - Psychic Terrain
  
  Example:
  
  Code:
  
  pbMaxRaid(nil,4,:EXEGGUTOR_1,nil,[1,2,10])
  
  This will create a 4-Star raid versus Alolan Exeggutor in perma-Sunshine (Weather 1), with perma-Grassy Terrain (Terrain 2), and in the Forest environment (Environment 10).
Spoiler:

If you want to randomize one or all of these conditions, simply set that condition to -1. So an array of [-1,0,1] will create a raid in a Grassland environment with no terrain in play, but the weather is always random. Obviously, you can set all three numbers to -1 to randomize everything.
Gmax
Spoiler:
This is a simple true/false option to force a Gigantamax Raid. This is set to false by default. This won't do anything unless the raid species has a G-Max form. Note that this will not prevent G-Max Raids from appearing if set to false, it merely allows you to guarantee one to appear if it's set to true.

Example:
Code:

pbMaxRaid(nil,5,:GENGAR,nil,nil,true)
This will create a 5-Star raid versus a Gigantamax Gengar. Normal Gengar will never appear with "gmax" set to true.
Hard
Spoiler:
This is a simple true/false option to toggle Hard Mode for the raid. This is set to false by default. When battling a Legendary Pokemon in a Rank 6 raid, Hard Mode is automatically turned on, and cannot be disabled.

Example:
Code:

pbMaxRaid(nil,5,:CHARIZARD,nil,nil,false,true)
This will create a 5-Star Hard Mode raid versus a Charizard.

Settings for Raid Battles:
These settings handle the base settings for Max Raid battles, and can be customized to your liking. These are found in ZUD_MaxRaid_01_Battle, at the top of the script.

Spoiler:

MAXRAID_SIZE
This sets the base number of Pokemon you can send out against a Raid Pokemon at once. This number is set to 3 by default. The lowest this number can be is 1, and caps at 3. However, if you're using Modular Battle Scene, this cap is raised to 5. Keep in mind that this is just the base number, so it's possible to set individual raids with different raid sizes.
MAXRAID_KOS
This sets the base number of KO's a Raid Pokemon requires to defeat you in a Max Raid battle. This number is set to 4 by default. The lowest this number can be is 1, and cannot be higher than 6 (it will cap at those numbers even if set outside that range). Keep in mind that this is just the base number, so harder raids may scale this number for difficulty purposes.
MAXRAID_TIMER
This sets the base number of turns a Raid can last before you are kicked out. This number is set to 10 by default. The lowest this number can be is 5, and the highest it can be is 25 (it will cap at those numbers even if set outside that range). Keep in mind that this is just the base number, so harder raids may scale this number for difficulty purposes.
MAXRAID_SHIELD
This sets the base number of bars a Raid Pokemon's shield has during a Max Raid. This number is set to 2 by default. The lowest this number can be is 1, and the highest it can be is 8 (it will cap at those numbers even if set outside that range). Keep in mind that this is just the base number, so harder raids may scale this number for difficulty purposes.
MAXRAID_PKMN
This is the base variable number used to store a Raid Pokemon's data. This is purposely set to a high number (500), because all variable numbers above this one are used to store each individual raid event's Pokemon.
REWARD_BONUSES
This is the variable number used to store a Raid Reward Bonuses. This is an array that tracks the Timer, Perfect, and Fair Fight bonuses.
MAXRAID_SWITCH
This is the switch number used to toggle Max Raid Battles.
HARDMODE_RAID
This is the switch number used to toggle Hard Mode Raids.
ALOLA_REGION
This is used for determining the region designated as "Alola". This is set to 1 by default. Change this to match your game. This setting is found in ZUD_MaxRaid_02_Events.
GALAR_REGION
This is used for determining the region designated as "Galar". This is set to 2 by default. Change this to match your game. This setting is found in ZUD_MaxRaid_02_Events.

Max Raid Database Tutorial.

Spoiler:

TheToxic7326 · Feb 2, 2021

Woah this is awesome! Do the ZUD_ files in the Data folder need to have the XXX_(script name) before it? (ex: 999_Main)

Lucidious89 · Feb 2, 2021

TheToxic7326 said:
Woah this is awesome! Do the ZUD_ files in the Data folder need to have the XXX_(script name) before it? (ex: 999_Main)

No, you can name them whatever you want. Theyre merely named to break up all the code in a clear and concise way. The order of the scripts shouldnt matter too much either, though I wouldnt play with it just to be safe.

TheToxic7326 · Feb 2, 2021

Alright, thank you!

RTCanwind · Feb 2, 2021

I really like the new processing method for max raid database.
The only problem is that in my game, some Pokemon's form numbers are not continuous.
In this case, the generation will cause problems.
Would you be kind to help me about how to deal it?

Lucidious89 · Feb 2, 2021

RTCanwind said:
I really like the new processing method for max raid database.
The only problem is that in my game, some Pokemon's form numbers are not continuous.
In this case, the generation will cause problems.
Would you be kind to help me about how to deal it?

Sure, can you give me an example?

Sir William · Feb 2, 2021

Awesome Script ! No words to say

Devil Monster · Feb 2, 2021

Great Script , I will work on public animation release when I will be free

Rohit :The Charizard Trainer · Feb 2, 2021

This script is awesome 😀

RTCanwind · Feb 2, 2021

For example,I have Charizard_1(Mega)/Charzard_3(Another form)/Charzard_100(Another).And I dont define Charzard_2 and 4 to 99.And now I cant find any Charizard in the database.
And I have Ralts_3 but no 1 or 2.Now there is only ralt_3 in database,I cant find ralts_0(base form).
I wonder if its because my form numbers are not continuous,and if yes,how can I deal that.

Lucidious89 · Feb 2, 2021

RTCanwind said:
For example,I have Charizard_1(Mega)/Charzard_3(Another form)/Charzard_100(Another).And I dont define Charzard_2 and 4 to 99.And now I cant find any Charizard in the database.
And I have Ralts_3 but no 1 or 2.Now there is only ralt_3 in database,I cant find ralts_0(base form).
I wonder if its because my form numbers are not continuous,and if yes,how can I deal that.

Yeah, there are ways to handle this, although it might be messy to have to account for each individual case because they're not in any logical order.

In the ZUD_MaxRaid_02_Events script, find the method def pbInitRaidBanlist. This is where the lists for all eligible species/forms are handled for raids and the database.

There are 3 arrays found within.

"raid_banlist" is the hard-coded banlist of specific species. These Pokemon do not appear in any Max Raid-related events, period. Add a species to this list if you want it be completely banned from both raids and the database.
"random_forms" is a list of species that spawn in a randomized form when encountered in a Max Raid Den.
"base_forms" is a list of species that will only display the base form of a species in the Max Raid Database. This is used for species like Unown, so that only its first form is displayed in the database, rather than having 28 different entries for the same Pokemon.

Below these three arrays, you'll find this section:

Code:

for i in 1..PBSpecies.maxValue
    for f in 0...formdata[i].length
      next if f==0
      fSpecies = pbGetFSpeciesFromForm(i,f)
      formname = pbGetMessage(MessageTypes::FormNames,fSpecies)
      raid_banlist.push(fSpecies) if i==PBSpecies::FLOETTE && f==5
      next if formname=="Alolan" || formname=="Galarian"
      next if i==PBSpecies::PIKACHU && f < 3
      next if i==PBSpecies::BURMY
      next if i==PBSpecies::WORMADAM
      next if i==PBSpecies::SHAYMIN
      next if i==PBSpecies::VIVILLON
      next if i==PBSpecies::FURFROU
      next if i==PBSpecies::MEOWSTIC
      next if i==PBSpecies::ZYGARDE && f < 2
      next if i==PBSpecies::ROCKRUFF
      next if i==PBSpecies::LYCANROC
      next if i==PBSpecies::MINIOR && f < 7
      next if i==PBSpecies::SINISTEA
      next if i==PBSpecies::POLTEAGEIST
      next if i==PBSpecies::TOXTRICITY
      next if i==PBSpecies::INDEEDEE
      next if random_forms.include?(i)
      raid_banlist.push(fSpecies)
    end
  end

What this does is add EVERY FORM in the game to the "raid_banlist" array EXCEPT for the listed species. So for example, all 3 Lycanroc forms are allowed to appear in raids, because Lycanroc's entire species is listed here as an exception. However, only Zygarde 50% and Zygarde 10% forms are allowed to appear in raids, with Zygarde Complete being banned, because the list only makes an exception for Zygarde's first two forms (f < 2).

This might be trickier for you to have to deal with each individual case due to your form numbers not following any logical pattern, but you should be able to adjust this to take your custom forms into account.

The first thing you'd have to decide on though is this: Do you WANT these custom forms to appear in raids? Or no? I'm assuming you only want the base species to appear, with the custom forms being special things that you aren't supposed to have normal access to, or appear in the wild naturally. If so, all you need to do is add Charizard and Ralts to the "base_forms" array. This will make it so that only their base forms will appear, with any other forms being ignored. Simple.

However, if you WANT these custom forms to appear in raids, but as separate entries, then you have to fiddle with adding those forms to the exceptions list. For example, if you want BOTH Ralts and Ralts_3 to appear in raids (and the Database), but not Ralts_2 (since it doesn't exist), you'd have to add something like this to the exceptions list:

Code:

next if i==PBSpecies::RALTS && f != 2

Play around with that, and let me know how it goes. I haven't explicitly tested any of these suggestions myself, I'm just outlining how it should work.

Lucidious89 · Feb 2, 2021

Minor Update:
Fixed an issue with raids where an error might occur when the Raid Pokemon tries to attack multiple times in certain situations. The Download link will be updated shortly. In the meantime, just replace your ZUD_04_Battle_Effects and ZUD_MaxRaid_01_Battle scripts with those found in the links provided.

DashBoy10 · Feb 2, 2021

Hey Lucidious89, it's DashBoy10. I don't know if its just me but there's are some errors that I don't know how to fix, I'll explain them.

1. The gimmicks works perfectly, but as I use a Z-Move or Dynamax move, the game says there's a problem with "Gorilla Tactics." I used a Pokemon that doesn't have the ability "Gorilla Tactics" and the game stops me from using the Z-Move or D-Max move. This also applies to Ultra Burst and Raid Battles. To Ultra Burst, it still allows Necrozma to attack, but not use its Z-Move.

In more simpler terms, here is where every error of mine occured.

The Gorilla Tactics one appears when the opponent attacks of inflicts a status on me or lower my stats.

The Obstruct one appears when I attack or just use a move in general.

The yamaskhp one appears when me or the opponents Pokemon faint

And the undefined arguments one appear when I send out a Pokemon after it fainted during its turn.

Am I missing something, or did I mess something up, it may be just me, but this is something I've encountered while using this script. If you're wondering, I'm using V18.1, I have Gen 8 Project, and I read all of the instructions and put them in the right place, can you help me out on this problem? Thanks!

Lucidious89 · Feb 2, 2021

DashBoy10 said:
Hey Lucidious89, it's DashBoy10. I don't know if its just me but there's are some errors that I don't know how to fix, I'll explain them.

1. The gimmicks works perfectly, but as I use a Z-Move or Dynamax move, the game says there's a problem with "Gorilla Tactics." I used a Pokemon that doesn't have the ability "Gorilla Tactics" and the game stops me from using the Z-Move or D-Max move. This also applies to Ultra Burst and Raid Battles. To Ultra Burst, it still allows Necrozma to attack, but not use its Z-Move.

In more simpler terms, here is where every error of mine occured.

The Gorilla Tactics one appears when the opponent attacks of inflicts a status on me or lower my stats.

The Obstruct one appears when I attack or just use a move in general.

The yamaskhp one appears when me or the opponents Pokemon faint

And the undefined arguments one appear when I send out a Pokemon after it fainted during its turn.

Am I missing something, or did I mess something up, it may be just me, but this is something I've encountered while using this script. If you're wondering, I'm using V18.1, I have Gen 8 Project, and I read all of the instructions and put them in the right place, can you help me out on this problem? Thanks!

I don't think you actually have the Gen 8 Project installed. It seems like you're missing those Gen 8 mechanics (Gorilla Tactics, Obstruct, etc.). You wouldn't be getting those errors otherwise. I think you installed this plugin in a regular copy of Essentials v18.1 (the error even says its v18.1).

EDIT: You're definitely using v18.1 and not the Gen 8 Project. Your error says pbRecallAndReplace should only have 3 arguments instead of 4. Version 18.1 only uses 3 arguments for that method, but the one in the Gen 8 Project uses 4. So you're using the wrong version of Essentials.

I guess we know that this plugin definitely doesn't work with v18.1 now, though lol

RTCanwind · Feb 2, 2021

Err...It seems it didnt work.(I filter with TYPE FIRE)
Did I get something wrong?

Lucidious89 · Feb 3, 2021

RTCanwind said:
Err...It seems it didnt work.(I filter with TYPE FIRE)
Did I get something wrong?

Yeah, the script just gets real weird when it comes to unregistered forms. I had this issue with Pikachu (its first 2 forms are unregistered), and I still can't get it to work exactly how I want. Try adding Charizard to the list of exceptions, too. If all you care about is having its base form in the database, that'll probably do the trick. However, if you want one or more of its other forms to appear too, that'll probably be tricky to somehow eliminate all the unregistered forms (otherwise you'll have 100 Charizard entries in the database).

The simplest long-term solution is to just not have unregistered forms when possible. Or if you do, make sure its for a species who has forms that you dont want in the database anyway.

RTCanwind · Feb 3, 2021

I will try to adapt that.
By the way,I have found the life orb bug in previous thread and it is fixed.Now I find a similar problem about Curse.
it seems curse damage should depend on dynamaxBoost.

ZUD plugin - Z-moves, Ultra-Burst, Dynamax, Dynamax adventures [v18]

More options

StCooler

Mayst thou thy peace discover.

StCooler

Mayst thou thy peace discover.

Lucidious89

Lucidious89

TheToxic7326

Lucidious89

TheToxic7326

RTCanwind

Lucidious89

Sir William

Chemist

Devil Monster

Rohit :The Charizard Trainer

RTCanwind

Lucidious89

Lucidious89

DashBoy10

Attachments

Lucidious89

RTCanwind

Lucidious89

RTCanwind