1) You might have already downloaded the required OXP in the same run. It can't tell if the dependencies are actually satisfied without doing a complete OXP reload, which can take a long time if you have a lot installed, so it only does that reload if anything's changed when you exit the manager.
2) The dependency might not be available through the manager at all, so you might want to set the download going while you go on the internet to look for it.
Incidentally: you can put manifest.plist files in OXPs. They won't do anything in 1.77.1, but if you have an OXP which other OXPs might either depend on or conflict with, add a manifest.plist the next time you update it, and when we get this into a release Oolite will pick it up as "manually installed". This will help stop people ending up with two copies - perhaps different versions - of the same OXP installed, though I imagine we'll still get a bit of that to start with.
There's been a public branch on Github for weeks, so it's more "secrecy through obscurity". It's just that now we can create branches easily, we don't have to have half-finished things cluttering up the nightly builds, so you tend to get the big stuff arriving in at least a mostly working state.Diziet Sma wrote:You guys really do keep the exciting stuff under your hats until almost ready to go
![[EliteWiki]](/images/elitewikismall.png){kind=small}
New Cargoes
