3.3.0-b1

Warning

BETA RELEASE - MAY HAVE BUGS - ONLY USE IF YOU ARE HAPPY TESTING PRE-RELEASE VERSIONS

v3.3.0-a1 to b1

New Features:

• Now log the details of any CMDR who kills you solo.

Bug Fixes:

• Don't log NPCs who kill you in a team, only CMDRs, and correctly look up the CMDR name (without the "Cmdr " prefix)

3.3.0-a1

Warning

ALPHA RELEASE - POTENTIALLY UNSTABLE - USE AT YOUR OWN RISK

3.3.0-a1

New Features:

• Targeting a player in a taxi will now log the player name and attempt lookup on Inara.
• Now log the details of any CMDR who interdicts you, sends a message in local chat, invites you to a team or kills you in a team.
• The CMDR listing window now has an extra 'Interaction' column which describes how you interacted with the other CMDR (scanned, interdicted by etc.).
• Thargoid War banshee kills are now tallied.

Changes:

• Faction name abbreviations are less obscure when the faction name contains a number or a dash.
• Thargoid vessel types are omitted if they are 0, both for kills and for missions. This creates shorter and clearer reports.
• No longer include Exobiology sales in discord reports.
• Plugin no longer terminates if it cannot fetch the tick from elitebgs.app on initial load. Not an ideal situation as we know nothing about the current tick, but at least BGS-Tally is still usable in this situation.

Bug Fixes:

• Fix (another) crash in code that detects drop from supercruise at megaships.

API Changes (v1.3):

• /events endpoint: All localised fields are now stripped before sending. i.e. fields who's name ends with _Localised.
• /activities endpoint: Added banshee to systems/[system]/twkills.
• /activities endpoint: Added scythe-glaive to systems/[system]/twkills.

3.2.0

New Features:

• In-game overlay now briefly displays a BGS summary for the current system when doing BGS work.
• Space Conflict Zones are now tracked automatically. As with Ground CZs, the game doesn't give us enough information to detect whether you've actually won the CZ, so if you drop in and log a kill within 5 minutes, this is tallied as a win. Manual controls are still available to adjust if you need.
• Thargoid War system progress is now displayed as a progress bar on the in-game overlay when in a TW active system.
• An activity indicator now briefly flashes green on the overlay when BGS-Tally logs BGS or TW activity.
• Thargoid War reactivation (settlement reboot) missions are now tracked: both for the station issuing the mission (🛠️ x n missions) and for the system where the settlement was reactivated (🛠️ x n settlements).
• Added a new setting to allow you to switch off reporting for new systems you visit. This is for CMDRs who regularly only want to report a subset of their work - it means you don't have to switch off a load of systems, you can just switch on the few you need.
• Forced ticks are now labelled clearly, including in Discord posts.
• Allow each overlay panel to be individually hidden or shown.
• Automatically attempt to track megaship scenarios. As with Ground CZs, the game doesn't give us enough information to detect whether you've actually won the scenario, so if you drop in and log a kill within 5 minutes, this is tallied as a win for the faction that's at war with the first ship you kill.
• Added quick-setup button for Comguard in API configuration window.

Changes:

• Pop-up legend window now contains a list of the Thargoid vessel type abbreviations.
• Show a hand cursor 👆 over help text to make it clearer you can click it to show the legend window.
• Pop-up legend window now includes 🛠️ for TW reactivation missions.
• Trade purchase is now reported in three brackets rather than two: 🅻 | 🅼 | 🅷
• Trade profit is now reported in four brackets rather than three: 🆉 | 🅻 | 🅼 | 🅷

Bug Fixes:

• Some Orthrus kills were not being tallied because the bond value logged was 40m instead of the previous 25m. We can only detect the type of Thargoid via the bond value logged by the game, so BGS-Tally will now tally an Orthrus for both kill values.
• Trade purchase, sale and profit was not being logged if you previously disembarked from your ship on foot, took a taxi or dropship somewhere, returned to your ship and then traded.
• Forcing a tick (via the settings panel), though still not recommended unless automatic tick detection has definitely missed a tick, should now be much more reliable:
  • It would cause your previously logged activity for the current tick to be lost and replaced by activity after the forced tick. Now, a 'proper' new tick is created so your earlier activity should be kept and available in the previous ticks dropdown menu.
  • If an automatic tick arrived with an earlier tick time than your forced tick, this could cause BGS-Tally to get confused. We now ignore any incoming ticks that have an older tick time than your forced tick.
  • Forced ticks are now handled more elegantly when sending data via the BGS-Tally API, as we generate a fake tickid for the forced tick.
• Due to a game bug, some illegal massacre and assassination missions were not tallying negative INF correctly against the target faction. Implemented a workaround for this.
• Due to a game bug, some ship murders were not being tallied against the target ship faction. Implemented a workaround for this.
• BGS-Tally now handles cargo ejection for Thargoid S&R operations. Previously, it could mis-tally to the wrong system because it hadn't realised the cargo scooped in that system had been destroyed by ejection.
• If you quit EDMC, jumped to a new system, then relaunched EDMC, any activity would be tallied to the last system you visited before quitting EDMC. BGS-Tally now realises that you are in a new system. Please note however, although it now knows you're in a new system, it can't get hold of faction or conflict information in this situation, so if you plan to work in the new system and haven't visited it before in this tick, you should jump to another system and back, or re-log to the main menu, either of which will properly load up the factions and conflicts.
• /events/ API wasn't augmenting StationFaction correctly for MissionFailed and MissionAbandoned events (per API spec v1.1).
• Thargoid S&R operations cargo tracking now cleared down properly when your cargo hold is empty. Previously, it could mis-tally to the wrong system.
• Don't clear Thargoid S&R delivery tally if you are killed.
• Fix crash in code that detects drop from supercruise at megaships.

API Changes (v1.2):

• /activities endpoint: Thargoid War reactivation missions now included in systems/[system]/factions/[faction]/stations/[station]/twreactivate
• /activities endpoint: Thargoid War number of settlements reactivated now included in systems/[system]/twreactivate
• /activities endpoint: Activity now has a ticktime timestamp in addition to tickid.
• /activities endpoint: When the user forces a tick, a new tickid is generated by BGS-Tally that conforms to the 24-character elitebgs.app tickid standard but starts with six zeroes '000000' to distinguish it as a forced tick.
• /events endpoint: Event now has a ticktime timestamp in addition to tickid.
• /events endpoint: When the user forces a tick, a new tickid is generated by BGS-Tally that conforms to the 24-character elitebgs.app tickid standard but starts with six zeroes '000000' to distinguish it as a forced tick.
• /events endpoint: Ensure StationFaction is not overwritten if it is already present from the journal event.
• /events endpoint breaking change: StationFaction is now always an object with a single Name property, and is never a simple string.

3.2.0-b3

Warning

BETA RELEASE - MAY HAVE BUGS - ONLY USE IF YOU ARE HAPPY TESTING PRE-RELEASE VERSIONS

v3.2.0-b2 to b3

Bug Fixes:

• /events/ API wasn't augmenting StationFaction correctly for MissionFailed and MissionAbandoned events (per API spec v1.1).
• Thargoid S&R operations cargo tracking now cleared down properly when your cargo hold is empty. Previously, it could mis-tally to the wrong system.
• Don't clear Thargoid S&R delivery tally if you are killed.
• Fix crash in code that detects drop from supercruise at megaships.

API Changes (v1.2):

• /events endpoint breaking change: StationFaction is now always an object with a single Name property, and is never a simple string.

3.2.0-b2

Warning

BETA RELEASE - MAY HAVE BUGS - ONLY USE IF YOU ARE HAPPY TESTING PRE-RELEASE VERSIONS

v3.2.0-b1 to b2

New Features:

• Added quick-setup button for Comguard in API configuration window.
• Trade profit is now reported in four brackets rather than three: 🆉 | 🅻 | 🅼 | 🅷

Bug Fixes:

• If you quit EDMC, jumped to a new system, then relaunched EDMC, any activity would be tallied to the last system you visited before quitting EDMC. BGS-Tally now realises that you are in a new system. Please note however, although it now knows you're in a new system, it can't get hold of faction or conflict information in this situation, so if you plan to work in the new system and haven't visited it before in this tick, you should jump to another system and back, or re-log to the main menu, either of which will properly load up the factions and conflicts.

API Changes (v1.2):

• /events endpoint: Ensure StationFaction is not overwritten if it is already present from the journal event. Note that this means StationFaction can now be either a string or an object.

3.2.0-b1

Warning

BETA RELEASE - MAY HAVE BUGS - ONLY USE IF YOU ARE HAPPY TESTING PRE-RELEASE VERSIONS

v3.2.0-a2 to b1

New Features:

• Allow each overlay panel to be individually hidden or shown.
• Trade purchase is now reported in three brackets rather than two: 🅻 | 🅼 | 🅷
• Automatically attempt to track megaship scenarios. As with Ground CZs, the game doesn't give us enough information to detect whether you've actually won the scenario, so if you drop in and log a kill within 5 minutes, this is tallied as a win for the faction that's at war with the first ship you kill.

Bug Fixes:

• Now handles cargo ejection for Thargoid S&R operations. Previously, it could mis-tally to the wrong system because it hadn't realised the cargo scooped in that system had been destroyed by ejection.

3.2.0-a2

Warning

ALPHA RELEASE - POTENTIALLY UNSTABLE - USE AT YOUR OWN RISK

v3.2.0-a1 to a2

Changes:

• Pop-up legend window now includes 🛠️ for TW reactivation missions.

Bug Fixes:

• The new TW reactivation mission tracking wasn't working quite right - it was tallying the missions as cargo instead of reac.

3.2.0-a1

Warning

ALPHA RELEASE - POTENTIALLY UNSTABLE - USE AT YOUR OWN RISK

3.2.0-a1

New Features:

• In-game overlay now briefly displays a BGS summary for the current system when doing BGS work.
• Space Conflict Zones are now tracked automatically. As with Ground CZs, the game doesn't give us enough information to detect whether you've actually won the CZ, so if you drop in and log a kill within 5 minutes, this is tallied as a win. Manual controls are still available to adjust if you need.
• Thargoid War system progress is now displayed as a progress bar on the in-game overlay when in a TW active system.
• An activity indicator now briefly flashes green on the overlay when BGS-Tally logs BGS or TW activity.
• Thargoid War reactivation (settlement reboot) missions are now tracked: 🛠️ (missions), both for the station issuing the mission and for the system where the settlement was reactivated.
• Added a new setting to allow you to switch off reporting for new systems you visit. This is for CMDRs who regularly only want to report a subset of their work - it means you don't have to switch off a load of systems, you can just switch on the few you need.
• Forced ticks are now labelled clearly, including in Discord posts.

Changes:

• Pop-up legend window now contains a list of the Thargoid vessel type abbreviations.
• Show a hand cursor 👆 over help text to make it clearer you can click it to show the legend window.

Bug Fixes:

• Some Orthrus kills were not being tallied because the bond value logged was 40m instead of the previous 25m. We can only detect the type of Thargoid via the bond value logged by the game, so BGS-Tally will now tally an Orthrus for both kill values.
• Trade purchase, sale and profit was not being logged if you previously disembarked from your ship on foot, took a taxi or dropship somewhere, returned to your ship and then traded.
• Forcing a tick (via the settings panel), though still not recommended unless automatic tick detection has definitely missed a tick, should now be much more reliable:
  • It would cause your previously logged activity for the current tick to be lost and replaced by activity after the forced tick. Now, a 'proper' new tick is created so your earlier activity should be kept and available in the previous ticks dropdown menu.
  • If an automatic tick arrived with an earlier tick time than your forced tick, this could cause BGS-Tally to get confused. We now ignore any incoming ticks that have an older tick time than your forced tick.
  • Forced ticks are now handled more elegantly when sending data via the BGS-Tally API, as we generate a fake tickid for the forced tick.
• Due to a game bug, some illegal massacre and assassination missions were not tallying negative INF correctly against the target faction. Implemented a workaround for this.
• Due to a game bug, some ship murders were not being tallied against the target ship faction. Implemented a workaround for this.

API Changes (v1.2):

• /activities endpoint: Thargoid War reactivation missions now included in systems/[system]/factions/[faction]/stations/[station]/twreactivate
• /activities endpoint: Thargoid War number of settlements reactivated now included in systems/[system]/twreactivate
• /activities endpoint: Activity now has a ticktime timestamp in addition to tickid.
• /activities endpoint: When the user forces a tick, a new tickid is generated by BGS-Tally that conforms to the 24-character elitebgs.app tickid standard but starts with six zeroes '000000' to distinguish it as a forced tick.
• /events endpoint: Event now has a ticktime timestamp in addition to tickid.
• /events endpoint: When the user forces a tick, a new tickid is generated by BGS-Tally that conforms to the 24-character elitebgs.app tickid standard but starts with six zeroes '000000' to distinguish it as a forced tick.

3.1.1

Bug Fixes:

• Fixed the Fleet Carrier screen, which was showing empty buy and sell order panels if your carrier had either no buy or sell orders.

3.1.0

New Features:

• Thargoid War kills are now tracked for each vessel type: 💀 (kills). But please be aware: BGS-Tally will only count a kill if it is logged in your game journal. This reliably happens if you solo kill a Thargoid, and usually happens (since game update 16) when you kill in a Team or with others.
• Thargoid War Search and Rescue collection and hand-in tracking. BGS-Tally now tracks where you pick up occupied and damaged escape pods ⚰️, black boxes ⬛ and tissue samples 🌱. You can hand them in anywhere, but they are tallied in the system they were collected.
• You can now delete CMDRs from the CMDR target list history.
• Targets older than 90 days are automatically removed from the CMDR target list history.
• When a friend request is received from another player, their details are looked up on Inara and they are added to the target log. Note that the squadron ID and legal status will be shown as '----' as that information is not available for friend requests.
• Carrier jump reporting implemented, automatically reporting your carrier jumps (and cancelled jumps) to a Discord channel of your choice.
• Thargoid War Revenant kills are now tracked (R in report).
• Thargoid War Scythe and Glaive kills are now tracked (S/G in report).
• Track the new TW evacuation mission released in Update 16.

Changes:

• Thargoid War massacre missions are now labelled slightly differently - 💀 (missions) - in line with the labelling for kills - 💀 (kills).
• Posting information on Discord now goes to a separate 'CMDR Information' channel, if you configure one. It will fall back to using the BGS channel.
• Exploration data tallying now takes into account not just the TotalEarnings logged but also the BaseValue and Bonus. The larger value is used if these differ. Note this is now the same logic that EDDiscovery uses.
• If there is a new version of BGS-Tally available, it is downloaded and installed during launch of the plugin instead of shutdown. This should mean that if there is a critical plugin bug that stops a clean shutdown, we should be able to fix it with an auto-update.

Bug Fixes:

• BGS-Tally was crashing on load when running on Linux. This is now fixed.
• Fix failure of networking thread, and therefore all subsequent networking calls, if an API discovery request detects new API features during startup.
• TW kills were not being logged to the correct system if it was a zero-population system. This was because historically BGST only dealt with BGS logging, so ignored zero-pop systems. We now create tracking entries for these systems.
• Harden all file loading and JSON parsing to protect against corrupted data on disk.
• Potential fix for mis-tallying of ground CZs when other commanders are fighting.
• Check for main UI frame before attempting to update the status text. Protects against rare errors where the status bar was updated before the main window has fully initialised.

API Changes (v1.1):

• /activities endpoint: Thargoid war kills now included in systems/[system]/twkills
• /activities endpoint: Thargoid search and rescue counts now included in systems/[system]/twsandr
• /events endpoint: StationFaction is now an empty string "" when undocked.