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

Rules to level up #25

Closed
matt-dray opened this issue Sep 21, 2022 · 1 comment · Fixed by #36
Closed

Rules to level up #25

matt-dray opened this issue Sep 21, 2022 · 1 comment · Fixed by #36
Labels
backend 🍑 Things not shown to the user, supports the stuff they can interact with frontend 👀 Things that are shown to the user, that they can interact with question ❔ Putting it out there for discussion/ideas

Comments

@matt-dray
Copy link
Owner

Let's keep this simple. Levelling up should be related to XP accumulation (#24).

What should the XP thresholds be? Might depend on how long we expect people to interact with the pet. Over multiple days, weeks, etc? Probably want the thresholds to be met relatively quickly to maintain some interest.

How many thresholds should there be and how should they scale? Might be more engaging if its non-linear. You can level up the first time relatively easily, then it takes a bit more effort, then a lot more effort.

Levelling up results in the pet taking a new form (#10) and more power in battle (#8)?

(Don't think about this too hard; no-one is actually going to play with this package.)

@matt-dray matt-dray added question ❔ Putting it out there for discussion/ideas frontend 👀 Things that are shown to the user, that they can interact with backend 🍑 Things not shown to the user, supports the stuff they can interact with thinking 🧠 labels Sep 21, 2022
@matt-dray matt-dray mentioned this issue Sep 21, 2022
@matt-dray
Copy link
Owner Author

matt-dray commented Oct 4, 2022

.update_blueprint() has current defaults of:

  • xp_threshold_1 = 100L (i.e. need 100 XP to get from level 0 to level 1)
  • xp_threshold_2 = 200L
  • xp_threshold_3 = 500L

This feels okay in basic testing. You aren't likely to interact with the pet all the time and so it may take a few days to break the thresholds. It would probably be boring if it took months and it would reduce the reward of 'caring' for the pet if it broke the thresholds too quickly.

Aside: should probably provide an arbitrary number of thresholds in a list or vector rather than specifically-named variables. But three thresholds feels right.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend 🍑 Things not shown to the user, supports the stuff they can interact with frontend 👀 Things that are shown to the user, that they can interact with question ❔ Putting it out there for discussion/ideas
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant