xF2 Add-on [DBTech] DragonByte Credits 5.9.0

Update highlights

This version introduces a few major features.

Where possible, a transaction will link back to the content it originated from. For thread / post events, no titles are displayed as that could potentially cause privacy issues, but clicking on the link will do all the normal permission checks.

The "Maximum applications" event limitation can now be applied per-user rather than globally. This resolves an issue where certain events make more sense to limit per-user and certain events globally.

A few reported bugs were also resolved, the most important of which being a case where the Payment event could fail. To resolve this, old Payment alerts have been removed (even if they were unread), as the data stored alongside these alerts has changed.


Complete Change Log

Feature: Link back to the content related to a transaction
Feature: The "Maximum applications" event limitation can now be applied per-user rather than globally
Change: Reworked the installer to make it more manageable going forward
Change: Points columns are now stored with a hard cap of 8 decimals
Change: When Smart Negation is enabled, Negation events will not occur if a matching Apply event is not found
Change: Remove prefix and suffix from currency alert template
Fix: Certain broken threads could produce a server error on rebuild
Fix: XF Media Gallery Comment class extension would eat comments
Fix: Paying with credits could cause a server error in certain circumstances
Fix: Alert opt out phrase for the Payment event was missing
Fix: If no previous transaction existed, ensure we set a sensible default when negating a transaction
Fix: Do not block charged events the user cannot afford if the currency allows negative amounts
Fix: Broken "Payment" event alerts have been deleted

Update highlights

This version adds one of the most frequently requested features: The ability to add DragonByte Credits as a payment profile!

You can apply this payment profile to things like user upgrades, DragonByte eCommerce products, and more! This feature will work with any 1st party or 3rd party system that uses XenForo's built-in payment profile system to handle payments.

When configuring the payment profile, you will have the option to pick which Credits currency is applied, and also the "Exchange rate". This helps translate your Credits currency to real-world currency. For instance, if you plan to apply this profile to a User Upgrade that costs $4.99, and set the exchange rate to 100, users will need 499 points to buy this upgrade.

This minor update fixes a couple reported bugs discovered since Beta 1.


Complete Change Log

Fix: Fix an issue where negating a skipped event would incorrectly apply - the negation should also be skipped
Fix: Fix an issue where the "Frequency" setting would not work as intended

Update highlights

This version adds one of the most frequently requested features: The ability to add DragonByte Credits as a payment profile!

You can apply this payment profile to things like user upgrades, DragonByte eCommerce products, and more! This feature will work with any 1st party or 3rd party system that uses XenForo's built-in payment profile system to handle payments.

When configuring the payment profile, you will have the option to pick which Credits currency is applied, and also the "Exchange rate". This helps translate your Credits currency to real-world currency. For instance, if you plan to apply this profile to a User Upgrade that costs $4.99, and set the exchange rate to 100, users will need 499 points to buy this upgrade.


Complete Change Log

Feature: Credits as a Payment Profile

Update highlights

This version fixes a few minor issues discovered in the previous version, based on reports from our community.


Complete Change Log

Fix: The Purchase event description now supports BBCode as intended
Fix: Ensure certain actions can only occur via submitting a form

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

Fix error

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

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