[DBTech] DragonByte Credits

[DBTech] DragonByte Credits 6.0.4

No permission to buy (€14.95)
Update highlights

This version fixes issues with various event triggers not respecting the "Frequency" event settings.


Complete Change Log

Fix:* The Daily, Interest, Taxation, Paycheck and Birthday events did not respect the "Frequency" related event settings
Update highlights

This version fixes various issues reported by the community.


Complete Change Log

Fix: The currency setting "Maximum Earned" did not work as intended
Fix: Internal change to fix a developer-only issue
Fix: Fix missing phrase in Approval Queue
  • Like
Reactions: Nirjonadda
Update highlights

This version implements the ability to disable the richest users' amounts in the overlay and widgets, as well as fixing a reported bug.


Complete Change Log

Feature: Per-currency option to disable richest users' amounts in overlay
Feature: Disable richest users' amounts in widget
Fix: Fix potential server error when merging posts
  • Like
Reactions: Nirjonadda
Update highlights

This version corrects an issue with the new cron job in Beta 1 where it would not correctly insert new transactions due to the nature of cron jobs running as guest user.


Complete Change Log

Fix: The Daily Activity event would not properly trigger while in a cron job
Update highlights

This version reworks the way daily credits operations are handled.

In previous versions, the following events would be handed the first time a user performed an activity on your forum that day:
  • Daily
  • Interest
  • Paycheck
  • Taxation
For the last 3, it would "catch up" if the user had not logged in for a significant amount of time.

This turned out to sporadically cause a problem wherein these events could be multiplied if users had multiple tabs open, and all of them performed some kind of action at the same time (such as refreshing a chat box every second). This only affected sites that had background operations that ran every second, otherwise collision protection would kick in. Still, the number of affected sites was greater than 0, and as such a solution was needed.

In v5.8, this code has now shifted to a cron-triggered rebuild job. What this means in practice is that those events will now be shifted to rewarding users for yesterday's activity at the end of the day, rather than giving them today's reward the first time they login. The upside to this is that there's no chance of collision, no matter how many tabs they open, because it's all handled by XenForo's cron job system.

This release is flagged as Beta because it's received limited amount of testing, but it should be functional enough for a production environment.


Complete Change Log

Change: Rework Daily Activity, Interest, Taxation and Paycheck to use cron jobs rather than login triggers
Fix: Prevent donating if either source is incapable of sending, OR target is incapable of receiving, donations
Update highlights

This version fixes an issue with the currency privacy setting, as well as a few PHP 8.1 related issues.


Complete Change Log

Fix: Fix an issue where the "Show to self and designated user groups" currency privacy setting did not apply correctly
Fix: Content type reference in the Transaction entity
Fix: Fix PHP 8.1 compatibility issue
Update highlights

This version updates the code for handling the Revival event, which may resolve certain issues with it.

Furthermore, a few other reported issues have been resolved.


Complete Change Log

Change: Attempt to resolve issues with Revival events
Fix: Fix server error when downloading a resource version
Fix: The Wallet widget would not save the correct values when choosing which currencies to display
  • Like
Reactions: jb9826 and Sunka
Update highlights

This version resolves an issue when loading options on certain pages other than the main AdminCP settings page.


Complete Change Log

Fix: When viewing options from pages other than the "Settings" page, a server error could be generated
  • Like
Reactions: jb9826 and Sunka
Update highlights

This update resolves an issue where the contents of [CHARGE] BBCodes could be revealed in the snippet shown to users when receiving "watched thread" emails, if the global XenForo setting to show post contents in watch emails was enabled.


Complete Change Log

Fix: Strip the [CHARGE] BBCode contents when rendering HTML in Email or API contexts
Update highlights

v5.7.3 introduced a bug where the post author was charged for others unlocking their content, this has now been resolved.


Complete Change Log

Fix: Fix regression in 5.7.3 with CHARGE tags
Back
Top Bottom