Unstoppable Polyobjects

[DnB-Freak]

Hi, I've tried all polyobject start/spawn spots (9301, 9302, 9303) while making moving walls that pushes players or monsters away or off cliffs.
Even on the (hurts on touch)-type, player runs against a polyobject moving/rotating towards him and yet a player manage to stop the polyobj's movement (yes, also receiving damage).
It causes it go out of sync with others, I've been trying fix it by activating and deactivating line bump specials on the very polyobj linedefs with LinedefAction 72: Thing Thrust,
but then it requires a very high amount of force to push a player running towards it, makes monsters pushed away too far
So I wonder if it's possible to add optional crushing polyobjects that are unstoppable and pushes anything standing in their way (if it doesn't require too much code or cpu usage, not sure )

[NeuralStunner]

I just tested this and noticed what you mean.

I put together a test map.

PolyPush.pk3

(1.15 KiB) Downloaded 56 times

In Map01 there are 2 polyobjects, the blue one is normal and the red has a crushing-type start spot. (This has no practical use in this case but anyhow.) They move in rhythm: Walk next to one and it'll slide you along. Push against one of them while it's coming toward you and you can desync the object, easily causing it to go through the wall.

There are a few things we could modify.

• Start Spots. There's a Crushing type, you could add an Unstoppable type (which would also imply crushing, I imagine).
• Movement specials. They'd need a new flag parameter with an "unstoppable" flag to begin with.
• Poly definition specials. You could add flags to them (same as above).

Unsure which would be best.

[DnB-Freak]

A unstoppable polyobject start spot DoomEdNum 9304 would be top-hole. Players running towards this would get knocked back.
Otherwise a flag for it at least it can be defined in decorate as child class.

[chopkinsca]

What happens if an unstoppable polyobject meets an unmovable thing?

[Gez]

Bad clipping.