Tried it in a mineshaft and every time I used headbutt as an external move it said "Nothing happened." when, in fact, something did happen. Tried it around five times and each time it repeated the message when it dropped an item

Thank you for your time and work!

Hey,

I was unable to replicate this, every time I used "External Move Headbutt" with my Charizard, an "A (pokemon) fell from the tree!" within a mineshaft. As that is a separate issue, I'll be investigating that further within another ticket.

-Swifty

I tested it again with a fresh install using 9.0.4 and it still happens. Got an Energy Root and White Herb and for both instances it still showed "Nothing happened" This was with a level 100 Gengar that I gave headbutt. To make sure I also tried with a level 100 Charizard that was given headbutt and I got two feathers to drop while the message still displayed.

I've been able to reproduce it every single time so I'm honestly confused why it didn't happen for you. Hope some further testing can be done, thank you for your time and effort!

Hi there, I was able to reproduce this myself, using the curseforge 9.0.4 modpack in singleplayer.

I gave a gengar the external move headbutt (if relevant, mine was level 38) and used the external move on a tree several times until an item dropped. I encountered several wild pokemon before I had this occur, which correctly displayed the message Swifty reported, but when the result of headbutt was an item, the somewhat errenuous message "Nothing happened." is displayed. From my testing, I received a power herb, white herb, big root, luminous moss, stick, 2 mental herbs and 5 feathers.

I found this easiest to reproduce with mushroom trees and savanna biome trees, presumably as the pool of pokemon spawns is smaller relative to the pool of loot spawns (hence, less uses of headbutt before an item and hence this issue occur). But I tested all vanilla tree types as well as a few modded ones (byg and pixelmon), and the issue is present for all of them.

Moving this issue to internal now, thank you for the report!

Hi there, I can confirm that this bug is resolved from version 9.0.6 onwards - thanks for the report!