Resource [Obsolete] wrigty12's much less exciting and less robust Terastal Phenomenon 1.4.3

[PokémonHeroine90]

I got this an error at the start

"[Pokémon Essentials version 20.1]
[v20.1 Hotfixes 1.0.7]

Exception: SystemStackError
Message: stack level too deep

Backtrace:
[ScarletVioletGimmick_TDW] 001_ScarletVioletGimmick.rb:77:in `initialize'
[ScarletVioletGimmick_TDW] 001_ScarletVioletGimmick.rb:77:in `initialize'
[ScarletVioletGimmick_TDW] 001_ScarletVioletGimmick.rb:77:in `initialize'
[ScarletVioletGimmick_TDW] 001_ScarletVioletGimmick.rb:77:in `initialize'
[ScarletVioletGimmick_TDW] 001_ScarletVioletGimmick.rb:77:in `initialize'
[ScarletVioletGimmick_TDW] 001_ScarletVioletGimmick.rb:77:in `initialize'
[ScarletVioletGimmick_TDW] 001_ScarletVioletGimmick.rb:77:in `initialize'
[ScarletVioletGimmick_TDW] 001_ScarletVioletGimmick.rb:77:in `initialize'
[ScarletVioletGimmick_TDW] 001_ScarletVioletGimmick.rb:77:in `initialize'
[ScarletVioletGimmick_TDW] 001_ScarletVioletGimmick.rb:77:in `initialize'"

Too deep!

Oh I forgot. Let me check

 

[raizen138]

I can't seem to replicate your issue, my Pokemon keep the previously set tera type when evolving. What Pokemon's evolution was switching tera type?

I am testing it with a chimchar evolving into monferno. The first time it happened it changed from fire to ice. Some tests keeps the fire tera, but now i've done another test and it has gone from fire to fighting.
My settings are:
UNDEFINED_MEANS_RANDOM = true
WEIGHT_RANDOM_TO_ORIGINAL = true
WEIGHT_PERCENT = 50

Don't know if it has something to do but I'm also using the script to evolve mid battle. And don't know if it helps but probably when the pokemon is evolving it is calling the generateTeraType function so it is making a new tera type for the "new" evolved pokemon? Just my guess.

 

[wrigty12]

Got it, I probably just had really good luck all the times I evolved something xD

I'll play around with it again tonight or tomorrow

 

[ardicoozer]

I got this error' after recall pokemon and get hit by dragon tail move

Spoiler

[2023-01-14 21:44:34 +0700]
[Pokémon Essentials version 20.1]
[v20.1 Hotfixes 1.0.7]

Exception: NoMethodError
Message: undefined method `pattern=' for #<Battle::Scene::BattlerSprite>

Backtrace:
[ScarletVioletGimmick_TDW] 006_ColorEffects.rb:212:in `unTera'
[ScarletVioletGimmick_TDW] 001_ScarletVioletGimmick.rb:506:in `pbRecall'
151:Battle_ActionSwitching:220:in `pbRecallAndReplace'
[ZUD Mechanics] Battle_Overrides.rb:290:in `pbRecallAndReplace'
[ZUD Mechanics] Override_Moves.rb:500:in `block in pbSwitchOutTargetEffect'
[ZUD Mechanics] Override_Moves.rb:494:in `each'
[ZUD Mechanics] Override_Moves.rb:494:in `pbSwitchOutTargetEffect'
[Generation 9 Pack] Battler.rb:767:in `pbEffectsAfterMove'
[ZUD Mechanics] Raid_Battle_Overrides.rb:29:in `pbEffectsAfterMove'
[PLA Battle Styles] [001] Battle.rb:264:in `pbEffectsAfterMove'

 

[wrigty12]

I got this error' after recall pokemon and get hit by dragon tail move

Spoiler

[2023-01-14 21:44:34 +0700]
[Pokémon Essentials version 20.1]
[v20.1 Hotfixes 1.0.7]

Exception: NoMethodError
Message: undefined method `pattern=' for #<Battle::Scene::BattlerSprite>

Backtrace:
[ScarletVioletGimmick_TDW] 006_ColorEffects.rb:212:in `unTera'
[ScarletVioletGimmick_TDW] 001_ScarletVioletGimmick.rb:506:in `pbRecall'
151:Battle_ActionSwitching:220:in `pbRecallAndReplace'
[ZUD Mechanics] Battle_Overrides.rb:290:in `pbRecallAndReplace'
[ZUD Mechanics] Override_Moves.rb:500:in `block in pbSwitchOutTargetEffect'
[ZUD Mechanics] Override_Moves.rb:494:in `each'
[ZUD Mechanics] Override_Moves.rb:494:in `pbSwitchOutTargetEffect'
[Generation 9 Pack] Battler.rb:767:in `pbEffectsAfterMove'
[ZUD Mechanics] Raid_Battle_Overrides.rb:29:in `pbEffectsAfterMove'
[PLA Battle Styles] [001] Battle.rb:264:in `pbEffectsAfterMove'

I'm unable to reproduce this. I tried many different combinations of having both wild pokemon and trainers using Dragon Tail against both terastilized and non-terastilized pokemon, both before and after switching them out manually and I never see this crash.

If you can reproduce it, can you give me exact steps (Trainer vs wild battle? was the pokemon you switched terastilized or not? etc.)

 

[wrigty12]

wrigty12 updated [Beta] Terastal Phenomenon with a new update entry:

Update 1.4.3

Fixed an issue where if a non-active party pokemon was terrasilized when the battle ended, it stayed terrastilized.

Read the rest of this update entry...

 

[Eften]

Though I used the command to force the pokemon trainer to the specified tera type, it didn't work. I did it successfully in the previous version but in this version, it is not working.

 

[wrigty12]

Though I used the command to force the pokemon trainer to the specified tera type, it didn't work. I did it successfully in the previous version but in this version, it is not working.

Can you give me more information? What is the exact command you used to force tera and create the trainer? Are you saying you updated my plugin from 1.4.2 to 1.4.3 when it stopped working? What other plugins do you have installed and did you update any of them at the same time?

 

[OkunoShio]

Is there a possibility to set the Tera Type for a wild Deluxe Battle similar how you can force the type of a trainer's Pokémon?

 

[Lucidious89]

Is there a possibility to set the Tera Type for a wild Deluxe Battle similar how you can force the type of a trainer's Pokémon?

There's an update in the works for total integration into Essentials Deluxe for features like this.

 

[OkunoShio]

Awesome to hear! Looking forward to it!

 

[wrigty12]

wrigty12 updated [Obsolete] Terastal Phenomenon with a new update entry:

A much better version takes its place

With the release of Lucidious89's Terastal Phenomenon plugin (URL to be added once post is approved), my version of this plugin is now obsolete. While you may still use this plugin if you wish, I highly recommend Lucidious89's fantastic and much more robust version, instead.

Unless someone really wants to use this version and a severe bug is found, I will not be making any more updates to this.

Thanks all!

Read the rest of this update entry...