Oolite Bulletins

I desperately want an Explorers' Club OXP to automate that process. One could gradually rise through the ranks and - only by visiting all 2048 planets - become president of the Explorers' Club.

Explorers’ Club OXP v1.3.3 (30/06/12)
Inspired by Wildeblood, code by capt murphy - 2011,2012
Licence: CC BY-NC-SA 3.0 : Please visit http://creativecommons.org/licenses/by-nc-sa/3.0/ for more info.
Requires Oolite 1.76.1

Overview:

Once installed this OXP keeps track of unique systems visited and reports on the manifest screen (F5) the total systems visited in the current galaxy out of 256 and the total systems visited out of 2048 in the whole Ooniverse. It also displays an Explorer ‘rank’. You need to visit all 2048 systems to be ranked an Elite Explorer.

In addition this OXP adds some functionality to the Long Range Chart (F6/F6) in that it can be set to different modes. To access the options screen press F2, then F6 when docked. The available options are:

1) Default - standard long range chart behaviour.
2) Long range chart shows animation of systems visited to date, in order of first visit.
3) Long range chart marks unvisited systems.
4) Player can manually mark systems on long range chart as a destination (highlight a system with the cursor and press F7)
5) Player can manually unmark systems on long range chart as a destination (highlight a system with the cursor and press F7)

Players should exercise caution when using the 2nd and 3rd options as it will clear any currently marked systems (e.g mission or contract destinations), although the 4th option can be used to manually reinstate them.

The options screen also allows you to choose when a system is recorded as visited. The options are.

1) Default – when docked at the main station.
2) On arrival from witch-space.

Options are persistent between sessions with the same save game.

The options screen also gives access to two further sets of mission screens.

1) Displays a list of the system names that have been visited so far in the current Galaxy, followed by a list of the system names that are yet to be visited in the current galaxy.
2) Displays a list of mile-stones that the player has completed / not completed so far. Defined mile-stones are:

· Visited all of the ‘Old Worlds’ in galaxy 1.
· Visited all of the ‘Famous Planets’ in galaxy 1 (as per OXP of same name).
· Visited all of the ‘Famous Planets’ in galaxy 2 (as per OXP of same name).
· Visited the ‘Prodigal Suns’ in galaxy 3.
· Visited the ‘Lost Worlds’ in galaxy 6.
· Visited the systems beyond the ‘Great Rift’ in galaxy 7.
· Visited Oresrati in galaxy 8.
· Visited all 8 galaxies at least once.

The options screen also allows you to enable/disable an experimental feature to keep a photographic record of systems visited. This is disabled by default.

If enabled the behaviour will depend on which option is set for recording a visit. If a visit is recorded on arrival from witch-space a screenshot will be automatically saved on exiting witch-space. If a visit is recorded on docking with the main station, at the next launch the player will be briefly ‘teleported’ to a good vantage point and a screenshot will be automatically saved before the player is teleported back to the launch point.

Change Log:

Version 1.0: 23/11/11 - Initial release.

Version 1.1: 24/11/11 – Fixed dodgy condition checks for the ‘rank’ string. Incorporated a number of code tweaks for efficiency suggested by Svengali.

Version 1.2.1: 1/12/11

Added functionality to view long range chart with unvisited systems marked, to view list of system names visited and unvisited in current galaxy, and to view list of mile-stones.
All missionScreens now managed via missionScreenOpportunity.
Long range chart mark visited systems animation will now complete in a maximum of 32 seconds (if all 256 systems have been visited).
Script now uses strict mode.
Added code to disable OXP entirely if player is in a galaxy outside of the range 1 to 8.
Added code to disable mile-stones feature if player is using a non-standard galaxy_seed.

Version 1.3.1: 21/01/12

Made compatible with Save Anywhere OXP.
Amended start-up behaviour for 1.76.
Removed use of forEach method for array iteration.
Message appended to system description on F7 screen to indicate whether system has been visited or not.
Added background image to missionScreens,
Added experimental photographic record of visited systems feature (thanks to Wildeblood for the snapshot HUD and some script suggestions, and thanks to the Honourable Guild of Test-Pilots for their valuable testing services).

Version 1.3.2 and 1.3.2oxpC: 5/03/12

Fixed minor bug in oxpC version that caused setting not to be saved in some circumstances.
Changed timing of record visit on witch space exit from this.shipWillExitWitchSpace to this.shipExitedWitchSpace - for compatibility with as yet unreleased long range jump OXPs.
Fixed mechanism of failsafe which prevents freeze should a JS timeout occur.

Version 1.3.3 and 1.3.3oxpC: 30/06/12

Fixed timer clean up mechanism to avoid unrooted timer errors when flicking rapidly to and from the long range chart,

Explorers’ Club OXP v1.3.3oxpC (30/06/12)
Inspired by Wildeblood, code by capt murphy - 2011,2012
Licence: CC BY-NC-SA 3.0 : Please visit http://creativecommons.org/licenses/by-nc-sa/3.0/ for more info.

Requires Oolite 1.76.1
Requires oxpConfig v.2.05
Requires Cabal_Common_Library v 1.5

Overview:

Once installed this OXP keeps track of unique systems visited and reports on the manifest screen (F5) the total systems visited in the current galaxy out of 256 and the total systems visited out of 2048 in the whole Ooniverse. It also displays an Explorer ‘rank’. You need to visit all 2048 systems to be ranked an Elite Explorer. From the manifest screen you can also press F6 to access more information about your explorations including lists of systems you have visited and systems you have not visited so far in the current galaxy and a list of other exploration mile-stones that you have completed or are yet to complete.

The current mile-stones are

· Visited all of the ‘Old Worlds’ in galaxy 1.
· Visited all of the ‘Famous Planets’ in galaxy 1 (as per OXP of same name).
· Visited all of the ‘Famous Planets’ in galaxy 2 (as per OXP of same name).
· Visited the ‘Prodigal Suns’ in galaxy 3.
· Visited the ‘Lost Worlds’ in galaxy 6.
· Visited the systems beyond the ‘Great Rift’ in galaxy 7.
· Visited Oresrati in galaxy 8.
· Visited all 8 galaxies at least once.

In addition this OXP adds some functionality to the Long Range Chart (F6/F6) in that it can be set to different modes. This version uses oxpConfig to access the options. oxpConfig can be accessed by pressing F2, then clicking on options. After a short delay oxpConfig will invite you to press F7 to access its screens.

Chart options are set via an oxpConfig slider.

1) Default - standard long range chart behaviour.
2) Long range chart shows animation of systems visited to date, in order of first visit.
3) Long range chart marks unvisited systems.
4) Player can manually mark systems on long range chart as a destination (highlight a system with the cursor and press F7)
5) Player can manually unmark systems on long range chart as a destination (highlight a system with the cursor and press F7)

Players should exercise caution when using the 2nd and 3rd options as it will clear any currently marked systems (e.g mission or contract destinations), although the 4th option can be used to manually reinstate them.

You can also set when a system is recorded as visited via oxpConfig. The options are.

1) Default – when docked at the main station.
2) On arrival from witch-space.

You can also enable/disable an experimental feature that keeps a photographic record of systems visited via oxpConfig. This is disabled by default.

If enabled the behaviour will depend on which option is set for recording a visit. If a visit is recorded on arrival from witch-space a screenshot will be automatically saved on exiting witch-space. If a visit is recorded on docking with the main station, at the next launch the player will be briefly ‘teleported’ to a good vantage point and a screenshot will be automatically saved before the player is teleported back to the launch point.

If you are changing to the oxpConfig dependant version of Explorers' Club from a previous standalone version your saved settings will be loaded into oxpConfig the first time you load a save game. However you will need to enter oxpConfig and manually store the settings for them to be maintained when you next save.

Change Log:

Version 1.0: 23/11/11 - Initial release.

Version 1.1: 24/11/11 – Fixed dodgy condition checks for the ‘rank’ string. Incorporated a number of code tweaks for efficiency suggested by Svengali.

Version 1.2.1: 1/12/11

Added functionality to view long range chart with unvisited systems marked, to view list of system names visited and unvisited in current galaxy, and to view list of mile-stones.
All missionScreens now managed via missionScreenOpportunity.
Long range chart mark visited systems animation will now complete in a maximum of 32 seconds (if all 256 systems have been visited).
Script now uses strict mode.
Added code to disable OXP entirely if player is in a galaxy outside of the range 1 to 8.
Added code to disable mile-stones feature if player is using a non-standard galaxy_seed.

Version 1.3.1: 21/1/12

Made compatible with Save Anywhere OXP.
Amended start-up behaviour for 1.76.
Removed use of forEach method for array iteration.
Message appended to system description on F7 screen to indicate whether system has been visited or not.
Added background image to missionScreens.
Added experimental photographic record of visited systems feature (thanks to Wildeblood for the snapshot HUD and some script suggestions, and thanks to the Honourable Guild of Test-Pilots for their valuable testing services).

Version 1.3.1oxpC: 21/1/12

Same features as 1.3.1 but options are set via oxpConfig.

Version 1.3.2 and 1.3.2oxpC: 5/03/12

Fixed minor bug in oxpC version that caused setting not to be saved in some circumstances.
Changed timing of record visit on witch space exit from this.shipWillExitWitchSpace to this.shipExitedWitchSpace - for compatibility with as yet unreleased long range jump OXPs.
Fixed mechanism of failsafe which prevents freeze should a JS timeout occur.

Version 1.3.3 and 1.3.3oxpC: 30/06/12

Fixed timer clean up mechanism to avoid unrooted timer errors when flicking rapidly to and from the long range chart,

Galactic Hyperdrive OXP

A free upgrade for the Galactic Hyperdrive, adding a destination programmer with 32 specific destinations, four in each galactic sector. Featured destinations include all the less commonly visited "Lost Worlds", allowing the operator to complete the Explorers' Club challenge.

Capt. Murphy wrote:

Inspired by discussion in this thread ( https://bb.oolite.space/viewtopic.php?f=4&t=11212), and Wildeblood's plea -

I desperately want an Explorers' Club OXP to automate that process. One could gradually rise through the ranks and - only by visiting all 2048 planets - become president of the Explorers' Club.

Capt. Murphy wrote:

Wildeblood spotted a problem with the condition checking for the ranking

Change Log:

Version 1.1: 24/11/11 – Fixed dodgy condition checks for the ‘rank’ string. Incorporated a number of code tweaks for efficiency suggested by Svengali.

To Do:

Look to code a display of (if systems visited in current galaxy <= 128, systems visited) or (if systems visited > 128, systems left to visit).
Make options configurable via OXPconfig rather than in-house screen.

pagroove wrote:

Nice OXP.
Could be nice to add certain achievements like: Vistited all of The Old Worlds, Tianve Tourist, Vetitice shipyards visitor etc

or put all the regions from the maps in it.

pagroove wrote:

Nice OXP.
Could be nice to add certain achievements like: Vistited all of The Old Worlds, Tianve Tourist, Vetitice shipyards visitor etc or put all the regions from the maps in it.

Capt. Murphy wrote:

Unfortunately the minimum interval for a timer is 0.25s so it's not a straightforward tweak. Might be able to do something with a frame callback, I'll have a think.

Edit to add - I could do something with TAF, but then that maybe wouldn't work with MNSR, depending on what build type is used for distribution.