I hope this email finds you well.
I am currently using your Lottery for WooCommerce plugin for my website, and I truly appreciate the functionality and ease it offers for setting up lottery systems. However, I have a specific requirement for my project that I believe could be a valuable addition to your plugin’s features.
Feature Request: Support for Multiple Number Selection Per Ticket
In my use case, I need participants to select 5 numbers per ticket (instead of the default single number selection). The winning condition would be that all 5 selected numbers must match the predefined winning numbers for the participant to win. If one or more numbers do not match, the ticket would be marked as a loss.
This feature would add flexibility to the plugin and make it suitable for more complex lottery systems. Below are a few specifics about the feature I am suggesting:
Multiple Number Fields: Allow participants to choose 5 numbers per ticket at the time of purchase.
Validation Rules: Ensure the selected numbers are within a predefined range (e.g., 1–50).
Winning Condition: Compare the selected numbers against a set of predefined winning numbers to determine winners.
Frontend Ticket Checker: Enable participants to check their results by entering their ticket/order number to see if they’ve won.
Why This Feature Is Valuable
Adding support for multiple number selections will significantly expand the plugin’s use cases, making it suitable for users who want to offer lottery games that are more engaging and customized. It could attract new users who currently rely on custom solutions or alternative plugins.
Conclusion
I believe this enhancement would make the Lottery for WooCommerce plugin even more versatile and popular among users. If this feature aligns with your development roadmap or if there’s an existing add-on that already supports this, kindly let me know.
Thank you for your time and for considering my suggestion. I look forward to hearing your thoughts!
Best regards,
Open
Last updated: January 22, 2025
0 comments
Log in to comment on this feature request.