Strange Morph issue

  • Please make sure you are posting in the correct place. Server ads go here and modpack bugs go here
  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Shevron

Well-Known Member
Aug 12, 2013
838
302
78
Playing DW20 1.0.24

Morph has been working fine for months for all players.

This morning I brought the server down, and updated AM2 to the latest version (we needed to clear some known bugs in 1.1.2).

Since I brought the server back up, Morph has gone weird.

If you hit the ceiling in bat form, you get damage.
Any 1-block morph, bat, chicken etc, takes damage when going through a 1x1 hole, being hole or ceiling.

What the heck is going on? I didn't touch anything on the server except AM2.

HALP
 
I actually think this is a Morph-side bug, AM2 doesn't seem to come into this issue at all really, making it seem like it has no part in this.
Do you know if this didn't happen before you installed AM2 for definite?
 
  • Like
Reactions: Elec332
I updated my DW20 server to 1.0.25 recently and all my players morphs were erased.. No player data files were messed with, all the Thaumcraft and AM2 research was still there, but all morphs gone.

I've also noticed that when in bat form your field of vision changes, and the edges of the screen go darker.. maybe something new? /shrug
I've not noticed taking any damage when morphing or trying to fly/crawl through 1x1 spaces. Try updating to 1.0.25?
 
I actually think this is a Morph-side bug, AM2 doesn't seem to come into this issue at all really, making it seem like it has no part in this.
Do you know if this didn't happen before you installed AM2 for definite?
Yes I am 200% sure that it didn't happen before the update.

I know AM2 (probably) has nothing to do with it, but it was the only change that I did. Installed AM2 together with its API and animation library, and fixed a couple of ID conflicts in the AM2 cfg.
 
Updating Morph to 0.7.2 up from the default-included 0.6.0.

Will see what happens and report back.

======================================

Update: Problem persists.
 
Well that would be nice. Is there a way to contact him?

I don't like bugging mod devs with issues, as I can imagine how bombarded they are with the pettiest of problems.
 
Did some testing. It actually IS AM2's fault in some way.

Rolled back to AM2 version 1.1.2, no damage and everything works fine. Reupgraded to 1.2.0, and problem is there again.
 
  • Like
Reactions: RealSketch