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

Change method .love command uses to derive score #1204

Open
1 of 2 tasks
jonathan-d-zhang opened this issue Feb 2, 2023 · 1 comment
Open
1 of 2 tasks

Change method .love command uses to derive score #1204

jonathan-d-zhang opened this issue Feb 2, 2023 · 1 comment
Labels
status: planning Discussing details type: feature Relating to the functionality of the application.

Comments

@jonathan-d-zhang
Copy link
Contributor

Description

Rather than using the usernames, the command should first try nicknames, then fall back to usernames if necessary. Alternatively, according to Nicky, "Love is deep. Love is about the true you". The .love command will use the id of the user rather than the nickname.

Reasoning

This would allow users to change their nicknames in order to get a score of 100% compatibility.

Proposed Implementation

Change https://github.com/python-discord/sir-lancebot/blob/main/bot/exts/holidays/valentines/lovecalculator.py#L62 to be

return clean_content(escape_markdown=True).convert(ctx, arg.nickname or str(arg))

or in the second case

return clean_content(escape_markdown=True).convert(ctx, arg.id)

Would you like to implement this yourself?

  • I'd like to implement this feature myself
  • Anyone can implement this feature
@jonathan-d-zhang jonathan-d-zhang added status: planning Discussing details type: feature Relating to the functionality of the application. labels Feb 2, 2023
@wookie184
Copy link
Contributor

I don't really mind, maybe the current behaviour of using usernames is the best balance between letting/not letting people influence the results

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: planning Discussing details type: feature Relating to the functionality of the application.
Projects
None yet
Development

No branches or pull requests

2 participants