Meaning of MOVETYPE_s and SOLID_s

[daemonicky]

I think that MOVETYPE_ affects several parameters : whether collides with world, whether collides with monsters (and players), whether gravity is simulated and whether bouncing is simulated. SOLID_ affects whether blocked() or touched() is called. Is it correct?

There are several MOVETYPE_ and SOLID_. What is each kind used for and when to use it?

I wanted to make some simple rope physics and i am not sure which to choose.

Thanks for help.

[Spike]

movetype affects how it moves and what stops it
solid affects what it stops

note that an ent which is not solid will generally not touch things that are not, so there's an overlap there.

most of the movetypes are basically the same. there's no difference between noclip/step/fly/toss/bounce until its affected by gravity or actually hit something.

if you want simple rope physics, use movetype_fly and solid_slidebox or whatever it is.
do the gravity and velocity changes in a think function and aproximate the swing, ignore the actual origin until you hit an object, otherwise use it only to propell the entity to the 'target' position that it should be at a fraction of a second's time.
if it touches something, bounce it off.
alternatively, use movetype_none and do all the moves yourself with tracebox. This will allow 'stepping' while swinging, if you care about that.

none of the builtin movetypes will give appropriate physics. movetype_fly will at least do collisions and impacts without gravity, but won't step (movetype_step won't step either).

[daemonicky]

[daemonicky]

[behind_you]