[DBTech] DragonByte Credits 5.9.0

Update highlights

This version builds on the work done in the previous version by extending support for [CHARGE] BBCode to the following areas:

• XFRM Resource Descriptions
• XFRM Resource Updates
• XFMG Albums
• XFMG Comments
• XFMG Media Items

Furthermore, a few issues reported by the community have been resolved.


Complete Change Log

Feature: Add CHARGE BBCode support for XFRM Resource Descriptions, XFRM Resource Updates, XFMG Albums, XFMG Comments, and XFMG Media Items
Change: Posts with CHARGE tags that have a cost of 0 will now be rendered normally
Fix: Fix an issue with deleting transactions after a currency has been deleted

Update highlights

This version fixes a bug with the XFMG, that only affected users whose media items required moderator approval.


Complete Change Log

Fix: If XFMG media required approval, credits would be awarded twice

Update highlights

This version implements a workaround for ThemeHouse's UI.X themes that use Material icons rather than FontAwesome icons.

Furthermore, it fixes a few issues reported by the community.


Complete Change Log

Change: Changed the display style of currency values for Ajust and Donate alert / push phrases
Fix: Support ThemeHouse UI.X themes when the navbar is configured to appear on the right hand side of the navbar
Fix: The currency overlay would not display correctly for mobile users if enough actionable events were enabled
Fix: Fixed an issue with the XFMG Media Create event when certain other add-ons are installed

Update highlights

This version makes internal improvements to the [CHARGE] BBCode parser in order to prepare it for upcoming functionality where it can be used to charge for other content types other than posts.

This version also resolves a few other edge case issues reported by the community.


Complete Change Log

Change: Make the Charge BBCode parser a bit more dynamic to prepare for other content types
Fix: If the event or currency pertaining to a particular transaction has been deleted, don't try to check permissions
Fix: Fix issue with the Credits payment profile

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

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