-
Notifications
You must be signed in to change notification settings - Fork 8
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
Levels #91
Comments
I think points is probably a better measure for leveling up; maybe level up starting at 100,000 points and have the threshold increase with your level? |
Possible level names and point value, based on cloaks, but you don't have to stick to this. I'm thinking of around 20 different levels, then you would prestige (start over again). elite – over 4 million points required It may be best for there to be a min. point and a min. question requirement for each level. |
Hm, that's a possibility. Not sure if that's completely necessary though, I think one or the other is probably sufficient. |
The only reason for the minimum question count is due to points gained from:
It could be technically possible for a user who has answered less questions to level up faster than someone who hasn't although it wouldn't be as likely. Now that I list it all out, I agree with @csssuf. I think it makes more sense to level up based upon questions answered only for now. That would work out better. |
How will KAOS questions be counted towards leveling up? One KAOS answer is one question, or getting at least one answer on a KAOS question is one question? I think the latter is probably better. |
Currently KAOS don't count into your total questions answered. I think either that or your idea with just one per KAOS would be fine. Assigned to csssuf |
@csssuf how's the progress going on this? |
Been busy with school; I can't take a look at this tonight, but I will get started tomorrow. |
That's fine, there's no rush - just wanted to see what your plan was. |
Basically I have two thoughts as how to do this:
Thoughts on which would be better? It's basically a tradeoff of disk vs. CPU. |
I think the first idea would turn out better, as it would be instant. |
@csssuf Do you think you'll be able to complete this project by the end of the month? I know you probably have finals coming up but do you plan on working on it during winter break? |
I have to see how my workload takes shape over the next couple of weeks, but I should be able to get this done by the end of the month. |
Any updates to this? :P |
Here's what I'm thinking: This uses lifetime questions. I'm not sure how this is stored in the database currently. Original proposal on how to do this: Two functions: checkLevel(username): changeLevel(username): |
- Updated table definition for trivialevel - Added methods for DB interaction with trivialevel table
Next feature to implement: levels.
Move up a level after a certain number of points have been reached, or after a certain number of questions have been answered? Also consider: increase streak multiplier as you level up? How many points/% should a player be awarded?
The text was updated successfully, but these errors were encountered: