TypeError "Cannot read property 'height' of undefined

[BaigletheKid]

Clear the troop and add it again... tell me if it worx

This worked, I have been sailing smooth using this method. You have to delete the enemy and input it manually. For some reason in mv if you paste a new enemy over an old one it trips it out.

 

[Shaz]

Can you please try and reproduce this issue in a brand new project, with NO plugins? I would like to know if this is an MV bug.


If you are able to reproduce it, please give me the exact steps, including screenshots if necessary, so I can also reproduce it?

 

[BrytonJSwan]

Hey I just thought I'd comment here and let y'all know that I had a essentially the exact same issue where a troop wouldn't work because of "TypeError: Cannot Read Property Height." This caused me extreme frustration until is was eventually solved. What I ended up discovering is that I had accidentally added in another enemy to the troop: an enemy for which I hadn't added a sprite. What I assume happened is that the game check to find both enemies heights for their sprites to know how to set up the battle and crashed because it was unable to find one of them (which seems like a huge oversight to be honest. You probably shouldn't be able to add enemies without sprites to a battle if it's just going to make it crash.) Hope that helps!

 

[dhofari9]

it happen to me also when i change the enemy position ( bat pic ) far behind


before it was working .. but, when i put some yanfly plugin its creach

 

[Zaen]

I am now having this exact same problem

 

[Shaz]

You need to provide more detail (preferably in your own thread, as this one is ooooold).


Screenshots of the console, details of what version of MV you're using, whether you're playing a saved game or started a new game, whether you've upgraded your MV since creating this project and if you manually updated all of the default scripts and checked/updated all of your plugins as part of the upgrade process, what plugins you're using.

 

[Andar]

I am now having this exact same problem

Np, you have the same error message but most probably not the same problem - because that error message is a message that can have dozens of different causes, which is why we need your specific screenshots.


And since it is another problem, you have to make your own topic about it instead of hijacking this topic.


Zaen, please refrain from necro-posting in a thread. Necro-posting is posting in a thread that has not had posting activity in over 30 days. You can review our forum rules here. Thank you.



Closing this