ZMovement 3.2.1

[thedeathrunner123]

ok thanks, didnt read that bro.

[Ivory Duke]

It's all good man, you asked me politely so I was not bothered by your request

[mamaluigisbagel]

I don't know if this was because I was playing D4T Crucible: Slayer Edition instead of normal D4T, but after grabbing a demon rune and turning into a Spectre, I noticed using Alt Fire/Charging acted...odd. It was like I was hitting the "Move Forward" key repeatedly. Not sure if the "reset values" button will fix this as I didn't try it. It only happened when in Spectre form and charging. Normal Player and Spectre's normal movement were fine.

I also had some crashes ledge grabbing, but I just assume that's because D4T Crucible: Slayer Edition adds ledge grabbing and the two are conflicting.

EDIT: Had another crash, and figured I'd post a screenshot of the error in case

[Ivory Duke]

I am gonna be honest and say right away that I do not intend to spend time on compatibility with Crucibile.
As for the crash I checked the code and it doesn't make sense that it would crash at those lines, gonna look into it a little more later but I see no problem on my end.

[mamaluigisbagel]

well I wasn't asking for compatibility for it. I was just saying I didn't know if that bug had to do with it or not.

I actually went back and played regular D4T, and had the same bug and crash anyway.

[TheOldKingCole]

So I tried to make a custom patch for beautiful Doom, but it didn't work. I followed the instructions, but I think I will need some help.

[Ivory Duke]

Is it the same crash you posted a picture of above?
It is helpful to know the exact circumstances in which it happened.
EDIT: please forgive me if I sounded rude in my previous comment, I have arrived home after an exausting flight to find out I have to fix my computer

[mamaluigisbagel]

I'm pretty sure it was the same crash as the picture, but I'll play regular D4T again and try to get the crash again just to be sure. Usually happens over time as I play.

And after going through that, I'd probably be a bit irritated too

[Ivory Duke]

Ok I figured out what was wrong and added a safety check.
I have updated the D4T patch, there is no hurry to update the main mod since it is a morph player exclusive issue.
Let me know if you run into the same issue again

[TheOldKingCole]

I realized I didn't past my error log for my Beautiful Doom problem, so here it is

"Script warning, "Beautiful-Doom-master.pk3:z_bdoom/w_ssg.zc" line 159:
Truncation of floating point constant -2.300000
Script warning, "Beautiful-Doom-master.pk3:z_bdoom/w_ssg.zc" line 333:
Truncation of floating point constant -2.300000
script parsing took 205.45 ms

Execution could not continue.

Fatal: unknown event handler class DashHandler"

[Ivory Duke]

I realized I didn't past my error log for my Beautiful Doom problem, so here it is

"Script warning, "Beautiful-Doom-master.pk3:z_bdoom/w_ssg.zc" line 159:
Truncation of floating point constant -2.300000
Script warning, "Beautiful-Doom-master.pk3:z_bdoom/w_ssg.zc" line 333:
Truncation of floating point constant -2.300000
script parsing took 205.45 ms

Execution could not continue.

Fatal: unknown event handler class DashHandler"

If you can link me in any way your patch I'll fix it up for you
EDIT: or if you tell me which Beautiful Doom you are using I can do it for you, but keep in mind it will up to you to keep it updated with any future releases

[TheOldKingCole]

I realized I didn't past my error log for my Beautiful Doom problem, so here it is

"Script warning, "Beautiful-Doom-master.pk3:z_bdoom/w_ssg.zc" line 159:
Truncation of floating point constant -2.300000
Script warning, "Beautiful-Doom-master.pk3:z_bdoom/w_ssg.zc" line 333:
Truncation of floating point constant -2.300000
script parsing took 205.45 ms

Execution could not continue.

Fatal: unknown event handler class DashHandler"

If you can link me in any way your patch I'll fix it up for you
EDIT: or if you tell me which Beautiful Doom you are using I can do it for you, but keep in mind it will up to you to keep it updated with any future releases

I'm using the most recent github master build. If you could make it for me that would be great.

[TheOldKingCole]

I realized I didn't past my error log for my Beautiful Doom problem, so here it is

"Script warning, "Beautiful-Doom-master.pk3:z_bdoom/w_ssg.zc" line 159:
Truncation of floating point constant -2.300000
Script warning, "Beautiful-Doom-master.pk3:z_bdoom/w_ssg.zc" line 333:
Truncation of floating point constant -2.300000
script parsing took 205.45 ms

Execution could not continue.

Fatal: unknown event handler class DashHandler"

If you can link me in any way your patch I'll fix it up for you
EDIT: or if you tell me which Beautiful Doom you are using I can do it for you, but keep in mind it will up to you to keep it updated with any future releases

I'm using the most recent github master build. If you could make it for me that would be great.

Since for whatever reason I cannot send a private reply i'd like to thank ivory duke for his help.

[Ivory Duke]

I checked my messages settings and they are enabled.
Whatever I guess, I am glad it worked out.

[mamaluigisbagel]

got another crash, but this time it was after using the "personal teleporter" equipment item in regular D4T. Will say I don't know if this crash is related to ZMovement or not, though. It looks like a D4T crash, but figured I'd post in case.