• Just a reminder that providing specifics on, sharing links to, or naming websites where ROMs can be accessed is against the rules. If your post has any of this information it will be removed.
  • Ever thought it'd be cool to have your art, writing, or challenge runs featured on PokéCommunity? Click here for info - we'd love to spotlight your work!
  • PokéCommunity's Easter Egg Hunt is now on! If you're interested in looking for some eggs and earning badges, click here!
  • Our weekly protagonist poll is now up! Vote for your favorite Conquest protagonist in the poll by clicking here.
  • 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

[Scripting Question] Ultra Necrozma & Greninja-Ash

Gemini_air

    • 51
    Posts
    10
    Years
    • Seen Jan 8, 2023
    Hello Guys!
    I have two questions for you. Actually i'm using the 17.2 version and i have some problem with "Mega Evolution" Script. I would like to add Ultra-Necrozma and Greninja Ash but i have these problems:
    Greninja-Ash.
    First i add in Compiler this line
    Spoiler:

    Then i wrote in MegaEvolution
    Spoiler:

    The problem is that the Mega Evolution not start. (I wrote in pokemonsform.txt)

    Ultra Necrozma
    in Mega Evolution i wrote this:
    Spoiler:

    The problem is when the battle ends, returns in the form 0 and not in 1/2 form. Can you help me?
     
    I'll adress Greninja, for the moment, because Ultra-Necrozma is not at my disposal yet.
    So, delete everything you have about Greninja in the scripts. Copy only what I've written with red. Let's go:

    In PokeBattle_Battler:
    Spoiler:


    In PokeBattle_MoveEffects:
    Spoiler:

    In Pokemon_Forms, under def def initialize(*args):
    Spoiler:

    In PokeBattle_Battle, in def pbThrowPokeBall:
    Spoiler:

    In PField_Battles, in def pbAfterBattle:
    Spoiler:

    Edit: Now I saw that Poq and WolfPP solved this before me, although we arrived independently to this conclusion.
    Edit2: With this code, a Greninja with Battle Bond can activate its ability again in the same battle if it dies, revives and faints an opponent again, which Bulbapedia says it shouldn't happen.
     
    Last edited:
    mybusiness said:
    With this code, a Greninja with Battle Bond can activate its ability again in the same battle if it dies, revives and faints an opponent again, which Bulbapedia says it shouldn't happen.
    Click to expand...

    I've got solution for this! It's not exactly elegant, but it should work - and the good news is that it involves only a slight modification to mybusiness's code. What we need to do is give Greninja a dummy ability that looks just like Battle Bond, but doesn't do anything. I'll explain:

    First things first, in abilities.txt, copy the line for Battle Bond at the bottom. Change the ability number to something unused, and change the internal name (the one in all caps) to something distinct but memorable, like XBATTLEBONDX. Leave the display name as is.

    Next, in pokemon.txt, assign this ability to Greninja as a second hidden ability.

    Now we're ready to get into the code. First, we'll go to PokeBattle_Battler and the code for pbFaint:
    Spoiler:

    That will give Greninja it's dummy ability when it faints, but only if it has changed form. So in Greninja's summary, it will still look like it has the usual Battle Bond ability, but if the player revives the Greninja, the dummy ability will not trigger any of the other code to activate Battle Bond.

    Next, we need to make it so that the REAL Battle Bond gets reset after battle. Back in PField_Battles, in def pbAfterBattle:
    Spoiler:

    This should ensure that Greninja with Battle Bond can only change forms once per battle. I'm sure there is a more coherent way of accomplishing it, but this is what I came up with.
     
    Last edited:
    Poq's script for PokeBattle_Battler seems to be missing an end statement, causing a syntax error.

    Here's a fixed version:
    Spoiler:


    Basically, just add an end statement under @pokemon.setability(3) and it should work.
     
    You must log in or register to reply here.
    Back
    Top