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

Battle #8

Open
matt-dray opened this issue Sep 16, 2022 · 4 comments
Open

Battle #8

matt-dray opened this issue Sep 16, 2022 · 4 comments
Labels
backend 🍑 Things not shown to the user, supports the stuff they can interact with feature ✨ New feature or request frontend 👀 Things that are shown to the user, that they can interact with

Comments

@matt-dray
Copy link
Owner

Idea via @adrianadepalma. Provide a pet (gist) ID, or choose one randomly (search gists for 'tamRgo.yaml' or whatever?). They (auto?)battle. Results are recorded in the pet blueprint. Wins increase happiness, increase XP/levelling up.

@matt-dray matt-dray added the feature ✨ New feature or request label Sep 18, 2022
@matt-dray matt-dray added 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 labels Sep 18, 2022
@mattkerlogue
Copy link

Oh perhaps my comment in #29 is better considered here.

@matt-dray
Copy link
Owner Author

matt-dray commented Oct 9, 2022

@mattkerlogue Acknowledged, good shout.

Regardless, I think there's a strong case for local battling in the first instance. So you get assigned a randomised on-machine 'opponent' that is within your pet's level, but with an XP value that's maybe normally distributed around your pet's XP (I think XP may be tied strongly to attach strength, among other things).

Later could extend this allow players to input a gist ID to fight a given pet (though if yours is level 1 and there's is level 3, you are going to get smacked). Could scan for gists that have 'tamRgo' in the name, but will be prohibitively time-expensive to search, I'm sure.

There's also an argument that happiness/play() don't need to exist if there's a battle mechanic. Battling can reward XP for a win, for example, and maybe increase happiness.

@mattkerlogue
Copy link

Maybe you can curate a central gist with links to available pets. Would then be easy to write a function that calls that gist and allows the user to select a specific pet and/or get one assigned (either completely at random or a smart matching like you suggest).

@matt-dray
Copy link
Owner Author

But won't it be difficult to maintain a gist that's millions of lines long? 🙃

(But ooh yes, I hadn't thought if doing it like that.)

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 feature ✨ New feature or request frontend 👀 Things that are shown to the user, that they can interact with
Projects
None yet
Development

No branches or pull requests

2 participants