Whenever I generate the list of artifacts (see also http://wiki.alioth.net/index.php/Index_of_artefacts), I can see that we have 687 OXPs registered on the expansion manager. Yet, when using the expansion manager I see the message that 690 expansions are available for download.
So I tried to find the discrepancy, and indeed there is a reason for this:
Whenever I generate the list of artifacts (see also http://wiki.alioth.net/index.php/Index_of_artefacts), I can see that we have 687 OXPs registered on the expansion manager. Yet, when using the expansion manager I see the message that 690 expansions are available for download.
So I tried to find the discrepancy, and indeed there is a reason for this:
This way it is questionable which OXP the user actually gets when trying to install by the name or id. How do we want to treat this situation?
BGS might well be my fault. The two versions have quite different effects for the witchspace jump - and I bugged people for the earlier effect (much more conducive to my aesthetic sensibilities). This might be solvable by either introducing a BGS override with the older effect or having a choice within BGS (accessible via OXP Config or some such). But this is work, and it is easier just to leave the choice on the Expansions Manager List.
I could add a maximum Oolite version to version 1.10.9 of BGS, so that it won't conflict with version 2.5.1. Would that help?
But with v1.10.8 and 1.10.9 of BGS, the min/max Oolite versions would keep them separate.
With Market Observer, v2.3.2 has a max Oolite version of 1.80, while version 3.7 has a min Oolite version of 1.82, so theoretically there is no conflict with this one either.
Actually, if players want to install both BGS versions in the current Oolite install, to grab the components out of each one, adding a max Oolite version would make that difficult.
Actually, if players want to install both BGS versions in the current Oolite install, to grab the components out of each one, adding a max Oolite version would make that difficult.
I guess since both OXPs have the same ID that Oolite would not be able to distinguish one from the other. So if you want to have two different OXPs make the IDs unique and off you go!
