ZDoom

No big deal, i didn't catch it either. It was an inconvenience for the ZZDoom release, i could have moved the tag but being myself i had to do a hard reset. xD

Apologies for the inconvenience.
I should have caught the whole thing in the OP but didn't notice it until later.

Thanks again.

Another PR: https://github.com/coelckers/gzdoom/pull/1524

I fixed what you reported and the test wad works.

Thank you kindly!
Although the fix is incomplete.

Other flags that are being changed is bNoGravity [url=https://github.com/coelckers/gzdoom/blob/395b5695adf10c843b4bc6a574ee505a4da0f193/wadsrc/static/zscript/actors/shared/movingcamera.zs#L491]here[/url]
And bInvulnerable and bDormant [url=https://github.com/coelckers/gzdoom/blob/395b5695adf10c843b4bc6a574ee505a4da0f193/wadsrc/static/zscript/actors/shared/movingcamera.zs#L502]here[/url]

The whole issue seems to be contained in the Activate() override which is pretty short.
Just to compare (again), [url=https://github.com/rheit/zdoom/blob/master/src/g_shared/a_movingcamera.cpp#L534]here's ZDoom's version of ActorMover's Activate()[/url]

Made a PR: https://github.com/coelckers/gzdoom/pull/1523

Not sure if this is relevant, but yes, apparently ZDoom's version did actually change the tracer's flags. So it's definitely broken.
https://github.com/rheit/zdoom/blob/master/src/g_shared/a_movingcamera.cpp#L542

According to this here [wiki]Classes:ActorMover[/wiki]
[quote]128: If the thing being moved is normally solid, make it nonsolid so that it can't be blocked.[/quote]

However I have found out that's actually not the case.
According to this it seems the ActorMover is changing its own flags instead of its tracer's flags. Seems like a typo?
https://github.com/coelckers/gzdoom/blob/9fac6058b766be33886e2028d88e1e298bb01d24/wadsrc/static/zscript/actors/shared/movingcamera.zs#L492

[attachment=0]actormover-nonsolidtest.wad[/attachment]
Have a test map, the moving green pillar is supposed to be non-solid, but you can stand in its way and it'll be blocked.
The ActorMover is using the 128 bit.

EDIT: Actually, any flag changes it's supposed to do are done on itself and not the tracer, regardless if 128 is used or not.
This seems wrong?