Update highlights
This version fixes a few minor issues discovered in the previous version, based on reports from our community.
Complete Change Log
Fix: Birthday event phrases used the wrong phrase key
Fix: Purchase event alert phrases did not work as intended
Fix: Worked around a race condition where the points column was deleted
Fix: Fixed clean installation not having the correct columns
Update highlights
This version features a major change to the way Thread and Post events work. The most frequent piece of feedback for DB Credits has always been "why do people lose credits when editing posts?" and the answer has always been "because of the 'amount per character' feature".
With this version, I aim to eliminate that confusion. The system will now look at the "Amount per character" / "Amount per word" setting for the Thread and Post events, and not apply any such events if those features are unused.
The end result is that editing a post will no longer add or remove credits unnecessarily.
Furthermore, credits are no longer awarded for automated threads or posts.
In other news, a new feature has been added where users can see their unlocked content (via the "Content" event and the[CHARGE]
tags in posts). This new page can be found via the navbar.
Complete Change Log
Feature: Page where users can view their unlocked content
Change: Rework Thread / Post editing to only trigger negation when it's absolutely necessary
Update highlights
This version fixes a performance problem with MySQL 5.6 and MariaDB 10.4, as well as introducing a few new minor features.
The description of a currency as set in the AdminCP is now displayed in the currency pop-up, above the tabs.
Lastly, it is now possible to link directly to a tab in the currency pop-up with a link such as/dbtech-credits/credits.1/?tab=purchase
(if you have a Purchase event set up for that currency).
Complete Change Log
Feature: Currency description now shows up above the tabs in the currency pop-up
Feature: Support "tab=" query string parameter to pre-select a tab
Fix: Work around a bug in MySQL 5.6+ / MariaDB 10.4 causing slow performance on transactions page
Fix: Purchasable type is now removed on uninstall
Update highlights
"Bug fixes and stability improvements"
Now that I've sufficiently triggered everyone who reads their phone app change logs...
This version makes a change that will help prevent a database error where leaving the "Points Column" field blank when adding a new currency could produce a database error.
Furthermore, the CLI command to rebuild currencies was not actually working because the class name and the file name didn't match. Whoops.
Lastly, a few minor other issues reported by our customers have been resolved.
Complete Change Log
Change: The "Column" field when adding a new currency is now marked as required in the form, preventing database errors in certain scenarios
Fix: Transaction alerts were not correctly listed as depending on this add-on
Fix: Fixed a missing phrase when adding a new currency
Fix: Fixed issues with Richest Users widgets
Fix: Fixed incorrect CLI class name preventing the CLI command from running
Update highlights
After a long beta / RC process, we're proud to present the Gold version of DragonByte Credits v6.1.0This means that this version is now considered stable enough to use on all forums.
Thank you to everyone who reported bugs and provided feedback during the Beta process, the mod wouldn't be as stable without your help and support.
This version makes a minor change to associate alerts with the add-on, meaning no ghost notifications should you ever disable the add-on while alerts are active.
Complete Change Log
Fix: Ensure alerts are tied to addon ID
Update highlights
This version updates the Approval Queue template for transactions to match the new XF 2.1 style. Furthermore, it fixes an issue where it was possible for a charge purchase (buying access to hidden content) to produce a server error.
Complete Change Log
Change: Updated Approval Queue template for Transactions
Fix: Prevent duplicate key exception when inserting a charge purchase
Update highlights
This version features mostly behind-the-scenes changes aimed at improving performance and reliability when deleting events and currencies.
Previously, transactions would be deleted right away, which did not work if you had tens of thousands of transactions (or more!) for any given event / currency. Transactions are now deleted using a background task, which vastly improves reliability.
Out of the bug fixes, the most important fix is that the Daily, Paycheck, Interest and Taxation events would not trigger correctly if multiple currencies were defined. Instead, they would only trigger for the first currency in the list.
Complete Change Log
Change: Transactions are now deleted in the background when an event is deleted
Change: Transactions are now deleted in the background when a currency is deleted
Fix: The Purchase event trigger would not correctly log the real-world cost of the purchase in its helper log table
Fix: Fix a missing landing page after purchasing credits
Fix: Daily, Paycheck, Interest and Taxation events would not trigger correctly if multiple currencies were defined
Update highlights
This version contains a number of bug fixes reported during the beta period, as well as a few major features and changes.
There are two major features in this update: Smart event negation and Event transaction moderation.
Smart event negation: In previous versions, you had to configure both the "Amount" and "Negation amount" settings for each events. If you did not do this, users could gain infinite credits by simply editing their posts over and over again. While the negation amount worked for the majority of users, it did not work if you made use of the "Random addition" feature.
In this version, you can optionally enable "Smart event negation" which will delete the previous transaction rather than inserting a new transaction when negating an event (such as deleting a post). This means your members will lose the exact amount of credits they earned (including random additions), and will no longer see multiple alerts when editing their posts. The transaction log will also no longer be cluttered with strike-through events.
This feature is still experimental, as I can't be sure if it works in every scenario. Furthermore, in order to take advantage of this feature, you have to set the "Negation amount" settings in your events back to 0 (so as to not disable a feature where negating an event would take away a different amount of credits).
The feature also doesn't work with all event triggers. A complete list is not available at this time.
Event transaction moderation: You can now optionally moderate each and every transaction for any given event. This is particularly useful if you have, for instance, a Redeem event that's supposed to be secret but you suspect the code has been shared. Events will appear in the Approval Queue where moderators with the appropriate permission will be able to approve or reject it.
Other changes and fixes can be found in the change log.
Complete Change Log
Feature: Smart event negation (beta)
Feature: Event transaction moderation
Feature: AdminCP transaction list / transaction view now displays the transaction state
Change: Editing posts will no longer produce an alert
Change: Rework the way Interest, Paycheck and Taxation events are applied in an attempt to reduce race conditions where events would apply into the future
Change: AdminCP transaction list now hides "Skipped" and "Skipped (maximum applications)" by default
Change: Renamed the Credits alert content types for consistency
Change: Number boxes in the AdminCP now use the XF spinbox style
Fix: It was not possible to select "both users" for the Taxation setting for certain events
Fix: The taxation feature did not function as described in the explanation text
Fix: Transaction messages would not respect the forum's censoring
Fix: Resolved a server error when limiting the Trophy event
Fix: Ensure thread owners won't trigger their own Reply events
Update highlights
This version refines the navbar integration by adding FontAwesome icons for menu entries when positioned in the right-side menu, as well as adding the ability to disable the text. Lastly, the HTML has been updated to better blend in with other right-side navbar items.
This has been tested on a limited number of custom skins. If you encounter any problems with the right-side menu after installing this update, please report it to the developer of your custom skin and ask them to get in touch with us to notify us of any changes we need to make.
Complete Change Log
Feature: Added FontAwesome icons for right-side menu entries
Feature: Added ability to disable the navbar text for right-side menu entries
Change: Updated the style of right-side menu entries to better fit into the surrounding entries
Update highlights
This update contains a few bug fixes for race conditions that could occur.
Most importantly, it fixes issues pertaining to the extra logging found when someone purchases credits for real money.
This update also fixes an issue where it was possible to crash the front-end by integrating the navbar tab with DragonByte Shop but the viewing user did not have permission to see the Shop tab.
Complete Change Log
Change: Switch various "delete" actions to use XF 2.1's deletion plugin
Fix: Fix issue where transaction log search in the AdminCP would always return no results
Fix: The "Filter" drop-down will no longer produce a server error if no valid events were found
Fix: Fix an issue with the Purchase Transaction table that could lead to server errors
Fix: Prevent server error when integrating with Shop but the Shop navigation is missing
We use essential cookies to make this site work, and optional cookies to enhance your experience.