Clan Participation ("Catch All" Type of Input for the Point Ranking System) #71
Closed
opened 2024-07-24 13:58:32 -04:00 by dakiny
·
2 comments
71-catch-all-clan-participation
main
renovate/python-3.x
renovate/ghcr.io-astral-sh-uv-0.x
renovate/pytz-2026.x
renovate/pandas-3.x
renovate/setuptools-84.x
renovate/dataclass-wizard-1.x
renovate/actions-checkout-7.x
renovate/docker-login-action-4.x
renovate/aiofiles-25.x
81-sqlmodel
autoban-channel
test-some-util-functions
add-logging
update-python
82-uv
76-clan-points
no-election-bug-fix
78-config-for-skipping-election-cycle
77-verification-for-splits
21-edit-configs-from-discord
65-database-changes
74-Double-period-in-record-point-command
60-view-event-points-when-no-non-discord-members
71-catch-all-clan-participation
68-time-command
63-bad-sorting
52-update-packages
fix-ruff-lint-smells
64-Limit-weekly-event-points
49-view-votes-cant-see-HC-elections
61-Create-virtual-environment-and-update-python-version
54-Only-edit-changed-channels
55-Use-dakiny-messages-repo-for-message-templates
56-announce-clan-council
53-Not-recording-High-Council-results-in-CouncilMembers-database
6-add-clan-rules
51-event-participation-recording
44-sort-candidates
47-incorrect-election-cycle
42-q1-elections-wrong-name
40-remove-presence
39-view-presences
v1.1.0
36-bot-presence
35-remove-nomination-views
18-highcouncil-election
33-fixes-from-mock-election
30-threads
34-use-correct-sql-statement
mock-election
32-view-votes-command
28-add-election-reminder
11-council-member-vote-automation
29-update-name-of-channel
27-supporting-first-live-action
26-the-annoy-command
25-cakeday
22-daily-loop-not-starting-election
19-birthday-tracking
10-name-change-request
20-finish-daily-loop
15-term-start-action
14-high-council-election-action
13-voting-end-action
12-voting-start-action
3-sqlite-database
2-election-cycle-class
4-configuration-options
election-class-test
5-create-pipeline
1-daily-loop
v2.1.2
v2.1.1
v2.1.0
v2.0.5
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v2.0.0
v1.7.3
v1.7.2
v1.7.1
v1.7.0
v1.6.9
v1.6.8
v1.6.7
v1.6.6
v1.6.5
v1.6.4
v1.6.3
v1.6.2
v1.6.1
v1.6.0
v1.5.1
v1.5.0
v1.4.5
v1.4.4
v1.4.3
v1.4.2
v1.4.1
v1.4.0
v1.3.0
v1.2.4
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.1.1
v1.0.1
v1.0.0
v0.2.1
v0.2.0
v0.1.1
v0.1.0
v0.0.6
v0.0.5
v0.0.4
v0.0.3
v0.0.2
v0.0.1
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: imcompiling/dakiny-bot#71
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This feature allows the bot to award 1 point for various activities that are not official clan events. These points, combined with points from events, will have a maximum of 10 points per week. For this feature, the bots needs to record who added the points, similar to the highscores submission.
Structure:
(drop-down with the following list:)Recipient
(same feature as "participants" in the events participation feature)Non-Discord Recipient
(same feature as "Non-Discord participants" in the events participation feature).Justification
*For recruiting counts: Active search, posting, bumping or commenting on other's threads (RS official discord or RS subreddits)
(~Kandy)
Shouldn't be that hard to implement. I won't track the justification, but I can have the command log the participation to the channel with the given justification.
Should this also be locked only behind the event host role or behind clan admin?
At this moment, we think lock behind @clan_member and maybe add some sort of summary of the input saying that a point was added by @dakeample to @dakother in category XXXX (similar to the "highscores submission" messages that are logged in the #highscores-submit after the submission is approved).
Ideally, we want clan members to "recommend" and give out points to fellow clan members. At this moment, the points do nothing to ranking and this feature is another test to see if we can use it to implement a point-base clan system for ranking and open to clan members.
With the weekly limit, even if someone abuses the system, we shouldn't have a big issue as we would be able to have a log of "baddakexample" adding a bunch of points to his friend with unsubstantiated justifications. The pro side is that people that we usually don't see being active can get points from other clan members, that would help with promoting people that play other times than council does.
(~Kandy)