Pixelmon Mod - Bug tracker

[8.2] Spectating a battle causes client to crash if either fighter uses Mega-Rayquaza fix completed

Ticket description:
When spectating a battle, if either of the two battling trainers uses Mega Rayquaza, the client crashes with a null pointer exception. This does not occur when I am participating in the battle, only when spectating it.

If participating, nothing bad happens regardless if I, my opponent, or both use Mega-Rayquaza.

java.lang.NullPointerException: Ticking screen
at com.pixelmonmod.pixelmon.client.gui.battles.battleScreens.BattleLogElement.acknowledge(BattleLogElement.java:103)
at com.pixelmonmod.pixelmon.client.gui.battles.battleScreens.BattleLogElement.func_73660_a(BattleLogElement.java:78)
at com.pixelmonmod.pixelmon.client.gui.battles.battleScreens.screens.WaitingScreen.func_73876_c(WaitingScreen.java:65)
at com.pixelmonmod.pixelmon.client.gui.battles.GuiBattle.func_73876_c(GuiBattle.java:451)
at net.minecraft.client.Minecraft.func_71407_l(Minecraft.java:1779)
at net.minecraft.client.Minecraft.func_71411_J(Minecraft.java:1098)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:398)
at net.minecraft.client.main.Main.main(SourceFile:123)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)

Full crash report for running at 2GB at: https://pastebin.com/3CQeV9CK
Full crash report for running at 4GB at: https://pastebin.com/GciyTcBE


#23060 Posted by Ordalca » 12 Aug 2021 15:39

This does not occur with other mega Pokemon that I've tried, such as Mega Alakazam, or alternate forms such as Primal Groudon/Kyogre.

#23076 Posted by NotKili » 21 Aug 2021 13:57

Hey Ordalca,

thanks for reporting this bug!

I can confirm that this does happen on the latest version of Pixelmon. Any other mega's, such as Mega-Tyranitar work just fine!

Marked as "Awaiting move to internal".

Sincerely, NotKili

#23754 Posted by Ordalca » 22 Nov 2021 22:30

Not 100% certain, but I believe this is fixed in the latest version

#23910 Posted by VanironCZ » 14 Dec 2021 06:59

Still bugged in 8.3.4.

#24667 Posted by Sophie847 » 21 Mar 2022 08:21


Just cleaning out some old tickets and came across this - I can confirm this issue was resolved in version 8.3.5.

Ticket details

  • Ticket ID: 16275
  • Project: Pixelmon Mod
  • Status: Fix completed
  • Component: Crash
  • Project version: 1.12.2-8.x.x
  • Priority: Normal
  • Severity: Normal
  • Forge/Sponge: Forge
  • What else would be useful to know?: See crash report for full list, attached
  • Assigned to: Sophie847
  • Reported by: Ordalca (Send PM)
  • Reporter's tickets: (List all tickets)
  • Reported on: 12 Aug 2021 15:26
  • Ticket last visited by: Sophie847 on 15 Jul 2022 00:17