Updated Recipient Messages

[Samuelteal33]

Updated the below to allow for Recipients to receive message upon receipt of payment:

Updated Pay Command to send recipient a message when payment is completed so that they are informed of the payment.

Updated Deposit Command to send recipient a message when payment is completed by the server/admin such as in /eco give commands.

Updated TranslationHandler to allow for the parsing of these messages to the recipients.

Updated Translation.yml to allow for customization of the recipient messages under the commands Pay and Deposit.

[lokka30]

Awesome work - thanks so much. I'll review this as soon as I have some time off - hopefully this Sunday. If all goes well (by the sounds of your approach in the description, highly likely!) then I'll merge this in and make sure to make sure you're credited for your work.

I also had a thought that it would be worth making the 'money received by administrative /eco command' message type to be toggleable, something I'll work on after merging. I will need to check the default behaviour of Essentials economy and try mirror that, and have the option for users to enable/disable it.

[lokka30]

TODO - check DM'd code which has config and command toggle

[lokka30]

Thanks @Samuelteal33 - apologies for delay in reviewing this, have been very busy lately!

For some reason the file diffs that git wants to merge in are really whack - unclear what's caused this, maybe a difference in how our IDEs are formatting code if I were to guess.

Basically this will require manual fixes on my end to get the diff back in order otherwise it will be a messy commit

[Samuelteal33]

Sorry about that @lokka30. Yeah, I am not overly familiar with github, so may be some differences that I am not familiar with.

[lokka30]

No probs at all, I've myself caused mayhem with git in the past (and present!..). I've found it is indeed some whitespace or line ending related issue which I'll likely be able to fix by re-formatting master and this PR respectively via Prettier or something, then the diff should clean up and can move forward from there.

Thanks for doing some code cleanup too, always pays to have another set of eyes over the work 🙂

Life is still so busy, unfortunately - though at least you've got it working on your end - now it's just a matter of public access to the changes and attribution. I'll update once I can next work on this since I'm being the hold up.

Edit 29/09/2025: once able, I'll likely approach as so:

• interactive rebase
• use --whitespace=fix
• initial review
• include changes outside PR for configuration
• final review + test
• squash & merge
• release

[lokka30]

Hi @Samuelteal33, just wanted to update (a long while later) that unfortunately I don't have the capacity to continue working on this project, or at least for now. I'll keep this open in case this changes or if a new maintainer is able to work on this.