Difference between revisions of "Extensions:Staff Rewards"

From Lorekeeper Wiki
Jump to navigation Jump to search
m (I don't know *what* I did, but it won't let me paste into this anymore-)
Tag: 2017 source edit
(Added missing command instruction update-staff-reward-actions)
Tag: 2017 source edit
 
(One intermediate revision by one other user not shown)
Line 6: Line 6:
 
| This extension has been merged into the v3.0.0 branch as [https://github.com/corowne/lorekeeper/pull/275 Staff Rewards].
 
| This extension has been merged into the v3.0.0 branch as [https://github.com/corowne/lorekeeper/pull/275 Staff Rewards].
 
|}
 
|}
<!-- Put a short summary of your extension here! -->
+
 
 +
Adds an optional (configurable/toggleable in config/lorekeeper/extensions.php) extension that can automatically reward a configurable amount of a chosen currency to a staff member on them performing an action for which rewards are enabled.
 
== Installation ==
 
== Installation ==
<!-- Describe installation. Include any requirements (such as packages), necessary commands, etc. -->
+
Must be turned on in config/lorekeeper/extensions.php in order to be used.
 +
 
 +
Run <code>update-staff-reward-actions</code> so that you can edit them in the admin panel.
 +
 
 
== Configuration ==
 
== Configuration ==
<!-- Is any configuration necessary? Describe it here! -->
+
Actions enabled for rewards are configured via different files in config/lorekeeper/staff-reward-actions, with each file corresponding to a different overall action (e.g. "process submission" for accepting/rejecting submissions and claims) for which staff should receive rewards. Rewards can only be dispensed for a specific action once and are broadly configured for only things that are one-time such as processing things through queues.
== Usage ==
+
 
<!-- Is there anything users should know about using your extension? -->
+
The amount of currency given to a staff member for performing each action can be configured via the staff rewards admin panel, accessible only to the admin rank; this also is populated via the config files via a command (php artisan update-staff-reward-actions) which can be run manually, but also runs daily via scheduler.
== Troubleshooting ==
 
<!-- Are there known issues or errors that require user action? Who should they contact, and where, for support? -->
 
 
== Images ==
 
== Images ==
 
<!-- Do you have any images to show what it looks like in action? -->
 
<!-- Do you have any images to show what it looks like in action? -->
 
== See Also ==
 
== See Also ==
<!-- Any relevant other pages. You may consider linking to related extensions, for instance. -->
+
* [[Updating:_to_3.0.0]]

Latest revision as of 09:27, 7 October 2024

Staff rewards
Description A short description
Author(s) itinerare
Status stable
LK Version 3.0
Is part of LK v3.0.0's release






THIS EXTENSION IS PART OF v3.0.0
This extension has been merged into the v3.0.0 branch as Staff Rewards.

Adds an optional (configurable/toggleable in config/lorekeeper/extensions.php) extension that can automatically reward a configurable amount of a chosen currency to a staff member on them performing an action for which rewards are enabled.

Installation

Must be turned on in config/lorekeeper/extensions.php in order to be used.

Run update-staff-reward-actions so that you can edit them in the admin panel.

Configuration

Actions enabled for rewards are configured via different files in config/lorekeeper/staff-reward-actions, with each file corresponding to a different overall action (e.g. "process submission" for accepting/rejecting submissions and claims) for which staff should receive rewards. Rewards can only be dispensed for a specific action once and are broadly configured for only things that are one-time such as processing things through queues.

The amount of currency given to a staff member for performing each action can be configured via the staff rewards admin panel, accessible only to the admin rank; this also is populated via the config files via a command (php artisan update-staff-reward-actions) which can be run manually, but also runs daily via scheduler.

Images

See Also