> So dropping warp3d support was the side effect of dropping rave3d?

Exactly.

> thats basically the same...

I don't think so. One was the intended effect, the other was the unintended side effect.

> MorphOS Team decided against Warp3D compatibility for R300 and beyond.

They decided against Rave3D compatibility for R300 and beyond.

> There is no side effect of anything.

I don't think so.

> They just straight ignored to implement it into the rave3d lib.

They "ignored" to implement support for R300 and beyond into Rave3D, for good reasons. MorphOS 3.13 still has Warp3D support for R200 wrapped to Rave3D via Goa.