This plugin allows server administrators to receive PayPal donations without additional
servers or a website. A built in webserver hosts a small website where people login
with steam, donate and receive a group ingame. The webserver handles
the response from PayPal and triggers the promotion. The donations are logged to be further
processed in later features to come. Additionally the plugin comes with a notification
service that allows people to type /donate in the game, be added by a bot on steam, and get
the hyperlink that directly points to your donation page.
- Fullly implemented PayPal donation workflow
- Built in webserver to host the donation page
- Notification service that contacts players over steam and explains the steps to donate
- The webserver can also host the permissions to use the WebPermissions on other servers
- Master / Slave mode to use the plugin on multiple servers
Permissions: donate - Allow access to the /donate command Configuration: UDonationsCoreConfiguration: Title: The name of your server / network Receiver: The business id or e-mail address of your PayPal account Local: The local the PayPal page will be in (Check https://developer.paypal.com/docs/classic/api/locale_codes/ for more) Currency: The currency you will be receiving donations in (Check https://developer.paypal.com/docs/classic/api/currency_codes/ for more) License: The license key you received when buying this plugin Items: (List of UDonationsItem) UDonationsItem: ItemNumber: Unique item id ItemName: Item name Price: Price or 0 to not have a fixed price set Commands: (List of string) Command: Command that will be executed when a user buys this UDonationsItem WaitForConnectBeforeExecute: Wait for the buyer to join before the command will be executed Description: Description of this item Category: Category (Tab) the item will be displayed on the website WebserverConfiguration: Enabled: If set to false - no webserver will be started, useful to use on a second server to not have its own page but link to an existing LocalIP: Change to listen on a specific network device PublicIP: Has to be set! Can either be the domain name or an ip that the webserver is publicly accessible with Port: The port used by the webserver (Make sure its TCP forwarded) PermissionsPassword: The password required to see the WebPermissions WebPermissions: The built in webserver is able to host WebPermissions on http://<PublicIP>:<Port>/permissions/<PermissionsPassword>. To setup, simply modify the WebPermissions entry in Rocket.config.xml accordingly on all other servers. Make sure to not use WebPermissions on the server you have the webserver running, also keep in mind that the permissions will be read-only on all other servers.