Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Raffle Draw #1

Open
sc-idevops opened this issue Apr 1, 2019 · 5 comments
Open

Feature: Raffle Draw #1

sc-idevops opened this issue Apr 1, 2019 · 5 comments

Comments

@sc-idevops
Copy link

It wouldn't be too hard to modify this program to also be able to pick one of the entries at random for when people do raffles! :3

@tonytins tonytins added the enhancement New feature or request label Apr 1, 2019
@tonytins
Copy link
Owner

tonytins commented Apr 1, 2019

This is definitely doable but would have to be saved for when I move to a database.

@tonytins
Copy link
Owner

tonytins commented Apr 2, 2019

Okay, I've been thinking this over and it is possible to create a raffle system with the current architecture. It'll be accessed via a subcommand since it differs from normal routine. artm raffle --slots 5 --tickets 20 --ych "Night Sky". The slots and tickets are max that are allowed and will generate a number based on those limitations. So the ouput would be:

{
  "slot": "2",
  "ticket": "15",
  "ych": "Night Sky"
}

Of course, this is very basic and a lot of room for error but it's a start. It's based on this YCH raffle.

@sc-idevops
Copy link
Author

ah I see how this raffle is set up. Users are self assigned a number on the order they are commented in. I was originally thinking about a twitter raffle where you can plug in someone's name and data in and then select one of those, but I think this implementation is a lot easier and requires less input. (all it is really is, is a RNG)

@tonytins
Copy link
Owner

tonytins commented Apr 2, 2019

Yes. I do like both the idea of a raffle and your Twitter-based approach. It's just the current architecture doesn't really allow for it, at the moment. I figured this would be the best compromise in the meantime.

tonytins added a commit that referenced this issue Jul 30, 2019
The database will allow for better flexibility and extensibility in maintaining varies types of art that are requested. This features a basic implementation of adding new orders to it but you can't yet search or delete. In the future, you will also be able to export these orders as Json files for use as a receipt or import into someone else's implementation of artm.

Other features include automated category selection and hashing based on former to determine the appropriate to add. The hashing is meant to not only verify information but also allow for accurate searching and pave the way for the raffling system, see issue #1.
@tonytins
Copy link
Owner

tonytins commented Oct 8, 2020

The architecture was completely rewritten starting with 0.4. I think this feature may finally become more of a reality.

@tonytins tonytins added this to To do in Raffle system Oct 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

2 participants