Cannot Summon Fireball/WitherSkull With/Without Direction (Unable To Summon Object)

Also WitherSkulls which were summoned before (in the snapshots) are now gone. Error in the Console for EACH witherSkull which disappeared:

java.lang.NoSuchMethodException: ahu.<init>(aqs)
	at java.lang.Class.getConstructor0(Class.java:2971)
	at java.lang.Class.getConstructor(Class.java:1812)
	at xb.a(SourceFile:175)
	at bfw.a(SourceFile:330)
	at bfw.a(SourceFile:95)
	at bfw.a(SourceFile:83)
	at qs.e(SourceFile:129)
	at qs.c(SourceFile:81)
	at net.minecraft.server.MinecraftServer.k(SourceFile:315)
	at cyf.a(SourceFile:111)
	at cyf.i(SourceFile:127)
	at net.minecraft.server.MinecraftServer.run(SourceFile:417)
	at java.lang.Thread.run(Thread.java:745)
[21:24:50] [Server thread/WARN]: Skipping Entity with id WitherSkull

I had the same problem with the WitherSkulls disappearing in this version

Looks like the constructor with just one World parameter was removed in the latest release for both the WitherSkull and Fireball classes.

This massively effects MANY custom maps. We really need a fix!

Time for 1.8 pre-2 this has to be fixed.

Heres Attachment of the fireball WITH direction:

[22:14:24 INFO]: Client> java.lang.NoSuchMethodException: ahl.<init>(aqs)
[22:14:24 INFO]: Client> 	at java.lang.Class.getConstructor0(Unknown Source)
[22:14:24 INFO]: Client> 	at java.lang.Class.getConstructor(Unknown Source)
[22:14:24 INFO]: Client> 	at xb.a(SourceFile:175)
[22:14:24 INFO]: Client> 	at cv.a(SourceFile:87)
[22:14:24 INFO]: Client> 	at ab.a(SourceFile:80)
[22:14:24 INFO]: Client> 	at ab.a(SourceFile:63)
[22:14:24 INFO]: Client> 	at rj.d(SourceFile:635)
[22:14:24 INFO]: Client> 	at rj.a(SourceFile:622)
[22:14:24 INFO]: Client> 	at lu.a(SourceFile:37)
[22:14:24 INFO]: Client> 	at lu.a(SourceFile:9)
[22:14:24 INFO]: Client> 	at ih.run(SourceFile:13)
[22:14:24 INFO]: Client> 	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
[22:14:24 INFO]: Client> 	at java.util.concurrent.FutureTask.run(Unknown Source)
[22:14:24 INFO]: Client> 	at net.minecraft.server.MinecraftServer.z(SourceFile:576)
[22:14:24 INFO]: Client> 	at net.minecraft.server.MinecraftServer.y(SourceFile:531)
[22:14:24 INFO]: Client> 	at cyf.y(SourceFile:155)
[22:14:24 INFO]: Client> 	at net.minecraft.server.MinecraftServer.run(SourceFile:447)
[22:14:24 INFO]: Client> 	at java.lang.Thread.run(Unknown Source)
[22:14:24 INFO]: Client> [22:14:24] [Server thread/WARN]: Skipping Entity with id Fireball
[22:14:24 INFO]: Client> [22:14:24] [Client thread/INFO]: [CHAT] Unable to summon object

PS. And Heres one from the snapshots:

[22:27:29 INFO]: Client> [22:27:29] [Server thread/WARN]: Fetching addPacket for removed entity
[22:27:29 INFO]: Client> [22:27:29] [Server thread/INFO]: [Sufi: Object successfully summoned]
[22:27:29 INFO]: Client> [22:27:29] [Client thread/INFO]: [CHAT] Object successfully summoned

This has GOT to be Fixed, so many things will be broken!

I believe that doesn't work because you're supposed to put a "d" after each number... But Searge 'fixed' it anyway. Not sure how...? But to quote Minecraft Wiki's Chunk Format page:

> direction: List of 3 doubles. Should be identical to Motion.

The command would be:

/summon Fireball ~ ~ ~ {direction:[0.0d,0.0d,0.0d]}

Louis, that does not work on affected versions.

The d's have never been required. I know this from personal experience using fireball "spells" as my go-to combat code on singleplayer. Remembering that it's direction not Motion (and that direction isn't capitalized) is the tricky part. Well that and having to make a math face anytime you want to change the direction you're firing.

From what I remember the one time that info is required is in a testfor code. Correct me if I'm wrong about that being the only instance.

Is it required for NBT data in scoreboards as well?

So, Searge changed the Fix versions to: Future Version 1.8. What means this? i need to wait for release 1.8 OR snapshot 1.8-pre2?

It could be either or.

Good news, heres a tweet from @SeargeDP : The witherskulls/fireballs bug is one of the reasons for pre2. We'll fix issues that are crashes or can break world saves. Nothing else!

(me) PS. So this means fireball/witherskull cannot be summoned until 1.8-pre2...

Even though we "fixed" wither skulls in pre2, map makers should NOT use them as position markers anymore, they will not work in the future.

– https://twitter.com/SeargeDP/status/503927350199738368

FYI - I found this same exception can happen with enderpearls too. The single-argument constructor for it was also removed. I had it happen on my server when someone was porting to the Nether, although not sure exact repro steps.

It would be clear though if a Mojang developer looked at the thrown enderpearl class. It would be the exact same fix for fireball and wither skull (adding a constructor that accepts only World parameter).

finally fixed days ago 🙂

Still occurs in 1.8 if summoned without direction. I think that this is intended, but in that case the title should be changed to Cannot Summon Fireball/WitherSkull With Direction (Unable To Summon Object) (get rid of the "without" in order to avoid confusion).

Also Ender Pearls are still unable to be summoned (didn't find it with the search, so I thought it might be related).

Sonicwave@ i think the fireball WITHOUT direction will not APPEAR. it should say : Object summoned successfully| but only the fireball/wither skull will dissapear.
ill try testing at 1.8 to see what happens. wait for an PS

PS. Tested. it works. so i shouldn't change the title. Even i cannot because is shared to https://mojang.com/2014/08/minecraft-1-8-pre-release-the-bountiful-update/ and if i change it mojang will need to edit the page, etc... O.O

I would say "without" works as intended and I have just tried summoning a ThrownEnderpearl with no luck. Not sure if it should be tagged along with this or as a new bug report. I am leaning towards making it a new report

This article is closed. Nobody needs to edit it anymore, since we already solved that. In case, we have that new 1.9 bugs which are very disturbing. Hope 1.9 looks nicer than 1.8. I dont say that 1.8 is awful, i love it, but i love more 1.9 😛