v1.4.2

Changes

• The application will now ensure that prices attained through the fallback method (autobot cache of prices.tf) are priced above 0. The autobot cache can sometimes contain items priced at 0, thus effectively pricing the item as free, making this new measure necessary.

Repository

v1.4.1

Changes

• Words will now be split on each space within a listing description before we check for blacklisted terms.

This patch ensures listings are not incorrectly excluded due to false positives.

Repository

1.4.0

Changes

• Added a new option "fallbackOntoPricesTf" to config.json that defaults to false.

When set to 'true' any items that are failed to be priced will instead be by prices.tf

Repository

v1.3.0

Changes

• Introduced a new configurable setting, 'alwaysQuerySnapshotAPI', which determines whether the pricer should consistently call the snapshot API for each item during the pricing process. When set to false has the potential to greatly speed up the pricing process for large item lists.
• Updated README.md with a new section discussing this new option.

Repository

v1.2.0

Changes

• New filtering logic added that excludes listings from pricing calculations that contain attributes indicating an item is painted. Painted items normally stray far from the average price due to their higher perceived value.

New Contributors

• @purplebarber made their first contribution in #5

Repository

v1.1.5

Changes

• Added more Steam IDs to the default blacklist. These IDs are associated with a recent scam.

Repository

v1.1.4

Changes

• Fixed issue where key object was left undefined on start-up, causing the first calculateAndEmitPrices() call to throw errors for the first few items.
• Refactored code, moved declarations of intervals into place.

Thank you @MartinL457 for reviewing the effects of the changes.

Repository

v1.1.3

Changes

• Fixed an issue where the metal values of the key were not always rounded to the nearest 0.11, to the nearest scrap.

Repository

v1.1.2

Changes

• Fixed an issue where we accessed undefined listing objects when calculating a mean after filtering out outliers.

This bug fix ensures that we only attempt to calculate the mean from the listings if there are 3 of them left after filtering out the outliers. If there aren't 3 listings, an error message is thrown.

Repository

v1.1.1

Changes

• Fixed bug that resulted in listings with only a metal value field being ignored.

This bug fix ensures that listings containing only a metal value are now properly processed and included.

Repository