EventedObject 3.0 clears up a lot of confusion. Event objects and evented objects are too similar, so event objects have been renamed to event fire objects because they are specific to the ->fire_event(). no_fire_obj replaces no_obj as the option to omit the event fire object. However, it behaves differently in that the evented object can still be passed with the new with_evented_object option. eo_obj has been replaced by this. no_obj, eo_obj, and with_obj are now deprecated but will remain functional until at least version 4.0.