- ServUO Version
- Publish 57
- Ultima Expansion
- None
I'm trying to understand the differences in the movement implementations between RunUO and ServUO. One thing I have noticed, is that ServUO replaced the Mobile object which was passed to CheckMovement() by a IPoint3D. It is then checked in a lot of places whether this can be casted back to Mobile.
My current assessment is that the only place where this change is actually needed, is in the VvVTrap class. There a path algorithm is used to draw a MovementPath when setting a trip wire, and in this instance there is no corresponding mobile (only the location is used).
Is this correct?
My current assessment is that the only place where this change is actually needed, is in the VvVTrap class. There a path algorithm is used to draw a MovementPath when setting a trip wire, and in this instance there is no corresponding mobile (only the location is used).
Is this correct?