• Our software update is now concluded. You will need to reset your password to log in. In order to do this, you will have to click "Log in" in the top right corner and then "Forgot your password?".
  • Staff applications for our PokéCommunity Daily and Social Media team are now open! Interested in joining staff? Then click here for more info!
  • Welcome to PokéCommunity! Register now and join one of the best fan communities on the 'net to talk Pokémon and more! We are not affiliated with The Pokémon Company or Nintendo.
    Register

Script: Z-Power [DBK Add-On] [v21.1]

Lucidious89

Lucidious89

    • 1,511
    Posts
    10
    Years
    • Seen today
    Z-Power for v21.1
    Fully implements Z-Move & Ultra Burst mechanics from Gen 7 into Essentials!
    [PokeCommunity.com] Z-Power [DBK Add-On] [v21.1]
    [PokeCommunity.com] Z-Power [DBK Add-On] [v21.1]

    Overview
    This plugin adds Z-Moves introduced in Pokemon Sun & Moon to your game, as well as the Ultra Burst mechanic from Pokemon Ultra Sun & Ultra Moon. Both mechanics have been replicated here, along with all of the Z-Crystals for each Z-Move, and the ability to power up status moves with Z-Powered effects. Ultra Burst has been generalizes so that it's possible to set up Ultra forms for other species beyond Necrozma. This plugin also fully utilizes the Deluxe Battle Kit's mid-battle scripting, allowing you to set up scripted scenarios related to Z-Moves and Ultra Burst.

    -DOWNLOAD LINK-

    Installation
    • First, please install the latest version of the Deluxe Battle Kit. This plugin functions as an add-on to that kit.
    • Next, download this plugin using the link provided and extract its contents to your root Essentials folder so that the Audio, Graphics, PBS and Plugins folders in the download merge with their equivalent folders in your project.
    • Note: If you are not using the Bag Screen w/ Interactable Party plugin, you can delete the Bag Screen with Party folder found in Graphics/UI. This is only provided for compatibility with that plugin, and serves no purpose otherwise.
    • Start your game in debug mode and make sure you recompile by holding down the CTRL key while the game is booting up. If the console says "Game data was not compiled", then you didn't hold down the key long enough, or don't have the game window in focus.
    • IMPORTANT: This plugin will adds graphics for a new bag slot, which this plugin assumes will be bag slot 9. If you already have a ninth bag slot, be careful not to replace your existing graphics while installing this plugin.
    • IMPORTANT: This plugin adds all eight of the capped Pikachu forms so that they may be present to use the exclusive Z-Move 10,000,000 Volt Thunderbolt. These forms are set to use form numbers 8-15 for Pikachu by default. If you already have these forms in your game, or use these form numbers for other things, then edit or remove the PBS file pokemon_forms_pikachu_caps.txt that is added by this plugin.

    Changelog (v1.1)
    Spoiler:




    Plugin Tutorial
    Please refer to the add-on page for this plugin in the Deluxe Battle Kit Tutorial.​
    Click to expand...
     
    Last edited:
    Minor Update (v1.0.1)
    • Fixed a major oversight that would ignore all damage calculation modifiers. Damage should now calculate normally.
    • Added new settings that allow you to manually assign the pocket used for Z-Crystals, and also rename it.
    • Made the Z-Crystal pocket inherently compatible with the (broken link removed) plugin. Z-Crystals will now also display party members who can use them when viewed in this plugin UI.
     
    Minor Update (v1.0.2)
    • Made some slight adjustments for compatibility with the (broken link removed) plugin. Button graphics are not provided, however.
    • Fixed an error that would occur when a Pokemon hit itself in confusion.
    • Fixed the Z-Booster item so that it only displays fail messages when appropriate.
    • Made it so the Z-Move Guardian of Alola may be assigned different animations based on which Tapu uses the move.
    • Made various tweaks in preparation for the release of the Dynamax add-on.
     
    Minor Update (v1.0.3)
    • Fixed an issue that would prevent battlers from updating their ability after Ultra Burst.
    • Fixed a crash that could occur when a Shadow Pokemon leaves the battlefield.
     
    Report: In a battle Necrozma used Ultra Burst and after that its ability is still Neuroforce.
     
    kome1j1514 said:
    Report: In a battle Necrozma used Ultra Burst and after that its ability is still Neuroforce.
    Click to expand...
    Do you have the latest versions installed?
     
    Minor Update (v1.0.4)
    • Z-Power mechanics will now show up in battle logs when battle logging is enabled.
    • Made some minor adjustments in preparation for the release of the Wonder Launcher add-on.
     
    Minor Update (v1.0.5)
    • Fixed a bug that would cause a crash when the AI has the move Copycat.
    • Made some minor adjustments in preparation for the release of the Animated Pokemon System add-on.
     
    Minor Update (v1.0.6)
    • Spinda will now properly display its spots during Z-Move/Ultra Burst animations.
    • Fixed a compatibility issue with the Animated Pokemon System add-on that would cause some sprites to display the incorrect Super Shiny hue during Z-Move/Ultra Burst animations.
     
    Last edited:
    I'm trying to add an Ultra Burst form for a Pokemon, but for some reason, the Z-Move goes through but the Ultra Burst form does not. I have it registered in pokemon_forms.txt and the following code in FormHandlers. The Pokemon in question has been covered by PKMN to avoid spoilers.

    Code: 
    MultipleForms.register(:PKMN, {
  "getUltraForm" => proc { |pkmn|
    next 4
  },
  "getUnUltraForm" => proc { |pkmn|
    next 3
  },
  "getUltraItem" => proc { |pkmn|
    next :ULTRAPOKENIUM if pkmn.form == 3
  },
  "getDataPageInfo" => proc { |pkmn|
    next [pkmn.form, 3, :ULTRAPOKENIUM] if pkmn.form == 4
  }
})

    What am doing wrong with this?
     
    JacktheLightningRipper said:
    I'm trying to add an Ultra Burst form for a Pokemon, but for some reason, the Z-Move goes through but the Ultra Burst form does not. I have it registered in pokemon_forms.txt and the following code in FormHandlers. The Pokemon in question has been covered by PKMN to avoid spoilers.

    Code: 
    MultipleForms.register(:PKMN, {
  "getUltraForm" => proc { |pkmn|
    next 4
  },
  "getUnUltraForm" => proc { |pkmn|
    next 3
  },
  "getUltraItem" => proc { |pkmn|
    next :ULTRAPOKENIUM if pkmn.form == 3
  },
  "getDataPageInfo" => proc { |pkmn|
    next [pkmn.form, 3, :ULTRAPOKENIUM] if pkmn.form == 4
  }
})

    What am doing wrong with this?
    Click to expand...
    Looks fine to me at a glance. Gonna need more details on your setup and the actual species and forms. I don't see how "spoilers" could possibly matter here.
     
    Lucidious89 said:
    Looks fine to me at a glance. Gonna need more details on your setup and the actual species and forms. I don't see how "spoilers" could possibly matter here.
    Click to expand...
    Sorry. I only tried to avoid spoilers since this Ultra Burst form is only obtained at one of my fangame's final battles. The Pokemon in question is Pikachu and the Ultra Burst form is Form 4.

    Form 0 is supposed to be your everyday, normal Pikachu, Form 1 is meant to be the Partner form (like Partner Pikachu in Let's Go), Form 2 is the Bonding Form (a form where Pikachu bonds with its trainer and it gains a little patch of fur on its head and its eyes change to a dark shade of blue), Form 3 is the Bonded form (a form where the patch of fur looks more like the hair on the main trainer's head and its eyes become the same shade of blue), Forms 8-16 are the Cap forms, and Forms 17-22 are for Cosplay Pikachu. The Cap and Cosplay forms I do not intend to use right now.

    The item in question is called the Ultrapikanium Z.
     
    JacktheLightningRipper said:
    Sorry. I only tried to avoid spoilers since this Ultra Burst form is only obtained at one of my fangame's final battles. The Pokemon in question is Pikachu and the Ultra Burst form is Form 4.

    Form 0 is supposed to be your everyday, normal Pikachu, Form 1 is meant to be the Partner form (like Partner Pikachu in Let's Go), Form 2 is the Bonding Form (a form where Pikachu bonds with its trainer and it gains a little patch of fur on its head and its eyes change to a dark shade of blue), Form 3 is the Bonded form (a form where the patch of fur looks more like the hair on the main trainer's head and its eyes become the same shade of blue), Forms 8-16 are the Cap forms, and Forms 17-22 are for Cosplay Pikachu. The Cap and Cosplay forms I do not intend to use right now.

    The item in question is called the Ultrapikanium Z.
    Click to expand...
    Then it probably has something to do with the fact that Pikachu already has a form handler, and form 1 of Pikachu is already reserved for evolving into Alolan Raichu.
     
    Lucidious89 said:
    Then it probably has something to do with the fact that Pikachu already has a form handler, and form 1 of Pikachu is already reserved for evolving into Alolan Raichu.
    Click to expand...
    I don't have the Partner form set to evolve into Alolan Raichu. All of these forms are set to have no evolution method. So how do you propose working around this? I want to have the Ultra Burst Form be a power-up and not a form to permenantly be in like the Bonding and Bonded forms.
     
    JacktheLightningRipper said:
    I don't have the Partner form set to evolve into Alolan Raichu. All of these forms are set to have no evolution method. So how do you propose working around this? I want to have the Ultra Burst Form be a power-up and not a form to permenantly be in like the Bonding and Bonded forms.
    Click to expand...
    No, I'm saying Essentials already has form 1 of Pikachu reserved for Alolan Raichu by default. You're overwriting that with Partner Pikachu. Form 1 of Pikachu should always be left blank because of this. Your forms should start from form 2 onwards.

    Pikachu already *has* a form handler in Essentials to force it into form 1 for evolving it into Alolan Raichu. So the form handler you made for an Ultra Burst form is either overwriting that handler, or the base handler is overwriting yours (depending on where you put your Ultra Burst script). My guess is that's why there's a conflict. You have to combine both handlers into a single script if you want to retain both and not have them overlap each other.
     
    How difficult would it be to add a "Partner Move" option for Pika Papow, VeeVee Volley or the stat boosts if the active Pokemon is not Partner Pikachu/Eevee?
     
    You must log in or register to reply here.
    Back
    Top