1ce63c40fc
The first time you click "Start monitor" (assuming you haven't read-all), we read the last 2 log files to find the journal entries for the last system jumped into (if we can find the FSDJump entry) in order to re-populate the information in all interested plugins. Its much faster than reading all to restore current system context. - For Botanist plugin, this will display what plants/planets you've already sampled and avoids placeholder planet entries with incorrect bio counts. - For Explorer, it re-lists interesting items, in case you weren't done exploring the system. See https://github.com/Xjph/ObservatoryCore/issues/5
Elite Observatory Core
Tool for reading/monitoring Elite Dangerous journals for interesting objects. Successor to the original Elite Observatory, rewritten from scratch using .NET 5.0 and AvaloniaUI.
IMPORTANT
Observatory Core and it's associated plugins are currently in an alpha state and are neither feature-complete nor using a finalised UI. Over the coming weeks I will outline in detail what functionality is missing but still planned, and begin work on getting it to feature parity with the original Elite Observatory.
Omissions to current functionality include:
- Voice notification
- Checks based on surface materials (yes, there are checkboxes for them in the Explorer settings, they do not do anything)
- Having an application icon
- Integration with Frontier's Companion API
- Integration with Telegram
- Data submission to IGAU
- More that I'm just not thinking of right now
How To Use
Observatory Core differs from the original Elite Observatory in that it is a fully generic reader for the Elite Dangerous journal files, passing those events along to plugins to do the actual work.
Observatory will attempt to locate your Elite Dangerous journal location in its default location, though other locations can be specified from the settings in the "Core" application tab. Due to the variety of possible system configurations this automatic detection does not function under Linux, so all Linux users will need to browse for the correct location.
The "Read All" button will read all journal files in the specified folder, handing their contents over to all loaded worker plugins. "Start Monitor" will begin watching files in the journal folder for changes, and pass new journal lines as they are created, as well as all changes to the status.json file, over to the worker plugins.
In addition to updating the content of their respective UI tabs, some workers can also send notifications, which will be distributed to all notifier plugins, as well as be passed to Observatory Core's native notification popup.
For specifics on what each plugin does, please refer to their respective repositories:
For information on how to create a plugin, refer to the repository for ObservatoryFramework.
Prerequisites for use
.NET 5, and by extension one of its supported OSes.
Prerequisites for building
C# 9.0, .NET 5.0, AvaloniaUI 0.10.3, and of course ObservatoryFramework.