Resource Raid Battles [DBK Add-On] [v21.1] v1.0

[Lucidious89]

Lucidious89 submitted a new resource:

Raid Battles [DBK Add-On] [v21.1] - Implements Raid battle mechanics to set up challenging wild encounters.

Raid Battles for v21.1
Implements Raid battle mechanics to set up challenging wild encounters.

Overview
This plugin builds upon the Deluxe Battle Kit to add various new battle modes to allow for challenging boss fights against wild Pokemon. Raid battles have their own special mechanics that draw...

Read more about this resource...

 

[komeiji514]

The last piece of DBK is here!

 

[Albion Kawakami Kuki]

This plugin, like the rest of the DBK, looks absolutely goated. For the rest of the plugin family, I already know how awesome they are.

For me, however, this plugin seems to cause an error with several instances of the pbStorePokemon command and its variants used in the 21.1 Hotfix plugin, the base Deluxe Battle Kit, this Raid Battles plugin, and even base 21.1 Essentials. No idea if this is just me, but it appeared after I installed this plugin. I tried looking into the commands, but I really have no clue what happens here. There are also a couple pbEndOfBattle additions in there, for some reason. Maybe they loop around and fail to actually store the Pokemon?

I did try setting up non-raid encounters, wild Mega, Dynamax, Gigantamax, and Tera events, but they all failed once I plugged this plugin back into the folder, though only after I caught the mon and it tried storing the Pokemon. Registering it didn't seem to cause any issues. I tried that without the Raid Battle plugin installed.

Finally, I just erased the offending line from the Raid Battles plugin (because violence against offending lines of code solves things sometimes, surprisingly), but not this time. The Pokemon just fails to get stored at all... Well, I should have figured things aren't that simple. I'm just baffled what happened here.

In hopes of getting things resolved, I included screenshots of the errors I got after catching a Pokemon set up through the wildMegaEvolution command from the Deluxe Battle Kit, a Pokemon I caught while it was in its mega-form (through setting an encounter with the mega-form directly through the encounters.txt PBS), and a plain old non-mega Pokemon I caught normally.

The error report for the wildMegaEvolution event:

The other two look the same, but the first one is the wild mega, the second is the regular wild Pokemon:

[PS: Noticed it after the fact, but the "regular wild Pokemon" was actually an overworld event using visible overworld encounters. Not that it changes anything, as I added a new screenshot below with a truly regular wild Land encounter.]

 

[Willøw]

- Reply -

First, we are aware of the Bugs this Plugin has, Lucidious dind't have time to polish every single Bug and released on this stage. however, we are waiting some time for more bugs to be found before releasing an Update to fix them, Lucidious in on a break, so we won't have updates from him for a while

In the meantime, go to the '[DBK] Battle - Raid Properties' inside '[002] Battle' folder within the plugin, found the raid_pbStorePokemon at the very end of the file and add (pkmn) next to it to fix the storing problem, also, yor images won't work because we need perms to view them, i recommend using Imgur when sharing images

 

[Albion Kawakami Kuki]

First, we are aware of the Bugs this Plugin has, Lucidious dind't have time to polish every single Bug and released on this stage. however, we are waiting some time for more bugs to be found before releasing an Update to fix them, Lucidious in on a break, so we won't have updates from him for a while

In the meantime, go to the '[DBK] Battle - Raid Properties' inside '[002] Battle' folder within the plugin, found the raid_pbStorePokemon at the very end of the file and add (pkmn) next to it to fix the storing problem, also, yor images won't work because we need perms to view them, i recommend using Imgur when sharing images

I had some trouble with Imgur at the time, and the Drive images showed up for me, so... Yeah, dummy be dummy. I fixed it now, but your addition already fixed that particular issue. Very happy with this plugin, thank you very much for the help!