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
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.