This is a tracking issue related to the Event API refactor which will break compatibility for the 5.0 release. Historically it was assumed that the returned values from the Ruby Event hash-like int...