Check for behavior misspellings, states, mobs n such. Also its CaSe-SeNsItIvE. Or delete the abyss behavior topkek
Originally Posted by MikeRaarupBirk Check for behavior misspellings, states, mobs n such. Also its CaSe-SeNsItIvE. Or delete the abyss behavior topkek But wouldn't visual studio pick it up if something was wrong with a behaviour? - - - Updated - - - Also, I just tried deleting abyss behaviour. Still same error.
Originally Posted by 9Gold But wouldn't visual studio pick it up if something was wrong with a behaviour? Maybe you made a mob called "watafck" and you write "watafck" in the XML but you write "watack" in the behavior. It wouldn't pop up as an error.
Originally Posted by 9Gold Oh okay. But how can I fix my problem I have? - - - Updated - - - So any ideas to fix it? If it was working before, just reverse whatever you added in or paste the code here so someone can find the error