Entity_GetAbsOrigin uses m_vecOrigin rather than m_vecAbsOrigin for some reason. We've only recently discovered that when used on a func_door_rotating, it returns the world origin (0, 0, 0). Are there any historical reasons for this function using m_vecOrigin rather than m_vecAbsOrigin? From the SDK, CBaseEntity::GetAbsOrigin uses m_vecAbsOrigin instead.
UPDATE: (If it wasn't obvious, the latter prop solves this case, causing to return the correct origin)
Entity_GetAbsOriginusesm_vecOriginrather thanm_vecAbsOriginfor some reason. We've only recently discovered that when used on afunc_door_rotating, it returns the world origin(0, 0, 0). Are there any historical reasons for this function usingm_vecOriginrather thanm_vecAbsOrigin? From the SDK,CBaseEntity::GetAbsOriginusesm_vecAbsOrigininstead.UPDATE: (If it wasn't obvious, the latter prop solves this case, causing to return the correct origin)