[DBTech] DragonByte Credits 6.0.10

Update highlights​

This version primarily fixes an issue with extremely large negative numbers in events such as Taxation. Furthermore, the Daily Credits cron job has an improved activity detection so it should no longer lag behind in certain circumstances.

Complete Change Log​

Fix: Use a better method for detecting latest activity for the Daily Credits cron job
Fix: Fix an issue where extremely large negative currency values could trigger server errors

Update highlights​

This version fixes an issue where an event would crash with a server error if the event's multiplier ended up at 0, such as leaving a rating with no stars.

Complete Change Log​

Fix: Fix server error with certain actions like leaving a rating with no stars

Update highlights​

This version updates the various widgets to make better use of cached data, eliminating one query per widget.

Complete Change Log​

Fix: Reduce the query count for widgets

Update highlights​

This version changes the way credit expiry works, to avoid a scenario where the user no longer has enough credits to deduct. If negative currency handling is set to "Disallow", expiring credits will now reduce the user's balance by 0 and skip any further expiration events.

Furthermore, a few reported bugs have been resolved.

Complete Change Log​

Change: Cap credit expiry to user's max credits when negative handling is set to "Disallow"
Fix: Fix issue when disabling navbar items from the Public Navigation page
Fix: Check whether the adjust event succeeded before printing success message
Fix: Check whether the transfer event succeeded before printing success message

Update highlights​

This version adds a couple of missing phrases.

Complete Change Log​

Fix: Add missing phrase
Fix: Refer to the correct XF phrase in transaction log

Update highlights​

This version makes a change to the "Richest Users" widget so it correctly respects currency privacy settings.

Furthermore, an issue with the "payment" event handler causing the transaction log to become unviewable due to a server error has been resolved.

Complete Change Log​

Change: "Richest Users" widget will now properly respect the currency privacy setting
Change: Clarify "Taxation" phrase with example of decimal form
Change: Change to XenForo native matching to verify table/columns
Fix: Fix "Content type payment must define an 'entity' value" server error
Fix: Fix missing phrase in alert opt-out preferences

Update highlights​

This version fixes a regression where events would not apply correctly due to the changes in v6.0.3.

Complete Change Log​

Fix: Fix events not applying correctly due to the changes in 6.0.3

Update highlights​

This version fixes an issue where various number fields in the database would be limited to a lower number than intended.

This also updates the database fields to use a different number-storing format. If you notice any unformatted displays (f.ex. 15.00000000 instead of 15.00 or however many decimals your currency is configured with), please let me know so I can fix it in a future version.

Complete Change Log​

Fix: Ensure we support numbers higher than 2147483647

Update highlights​

This version fixes an issue where the various number boxes used across this add-on would not accept decimals.

Complete Change Log​

Fix: Various number boxes would not accept decimals

Update highlights​

This version fixes an issue where removing an "Access Cost" event would still block people who did not purchase access from viewing the thread.

Complete Change Log​

Fix: Removing "Access Cost" events would not correctly allow users to view related threads