Based on your response, I went ahead and disabled the
Add-on Update Notifier add-on and they were able to be installed. I assume that means no other client you've had is using it so far, but this is an add-on that is being used by a lot of people in the XF community. That add-on is so popular it's supposedly going to be a default feature of XF 2.4.
That may well explain why you were the only person running into this.
At the moment, there are no plans to build Eggy add-ons around the behaviour of third-party add-ons. They will continue to be built and tested against XenForo itself unless this becomes something a larger portion of the customer base is actually affected by.
I’ve also checked the Add-on Update Notifier resource you mentioned, and it is currently marked as
Unmaintained on XenForo.com, with its last update dating back to December 2024. Because of that, I’m not going to make compatibility changes to Eggy products specifically around that add-on.
As things stand, you are still the only customer who has reported this particular issue. Given that disabling Add-on Update Notifier allowed both the Expansion Hub and AI Opponent to install normally, that strongly indicates the issue is being caused by an interaction with that third-party add-on rather than Eggy Pool itself.
It would also explain why I have been able to upgrade Eggy Pool through 1.0.7 to 1.0.8 with all extensions upgrading successfully, and why no other customers have reported the same dependency problem.
If XenForo 2.4 eventually includes similar functionality natively, that would be handled as part of supporting XenForo 2.4 itself. That is separate from supporting the behaviour of an unmaintained third-party add-on today.
Since you have now been able to install the Expansion Hub and AI Opponent successfully by briefly disabling that add-on, there is no need for me to send over any modified files.
Glad you’ve got it sorted now.