Revision Titles - Getting site wide notifications for Revision votes

[MertTolo]

Since I was the person who asked how the process in voting for revisioning games work, I felt that it would be more than appropiate for me to write this as an idea.

Currently, Revisions are not widely communicated and there are countless ways on how to improve it. One essential thing is - getting the opinion from current and former players - as the "outrage" with Grand Theft Auto: Vice City Stories showed.

Now, there are multiple ways on how to "weigh" these votes, but here are how I would communicate them, to start off with that:

1A: Communicate via the Notifications bell - as in, there is a new vote, with the option of disabling it on certain games.
Kinda like: IF=GameNotificationTrue THEN=SendNotificationVote ELSE=Ignore
1B: Via Private Messages - also in the same principle as 1A
1C: As a new section on the lower page, beneath "Latest Sets in Progress"

No matter how one goes about this though, there should be a option to disable these notifications from the getgo - 1C might be something that can stay either way

Now, regarding the weight of votes:

2A: Mastered Player 2 Votes - Current Players 3 Votes - Others 1 Vote - Devs 5-10 Votes (depending on the size of the revision)
-> that's the most balanced one in my opinion, however - I want to present alternatives.
2B: All Players 2 Votes - Others No Vote - Devs 10 Votes
-> Could lead to potential abuse of people just starting up the game so they can vote though.
2C: All Players 3 Votes - Others 1 Vote - Devs 10-15 Votes (depending on the size of revision)
-> my second favorite way on how to go about it.

Either way, I'd keep the vote for a week for smaller revisions, 2 weeks for bigger ones -> the vote itself is visible on the the lower main page, beneath "Latest Sets in Progress" and the game page itself.

(I know that this idea is not the most elaborate one, but I'm more than welcome to hear other peoples ideas)

[wescopeland]

My perception is this is a discussion for two distinct changes:

1. Adding a notification type.
2. Giving non-devs voting power for revisions.

Agreed that notifications need a lot of help, and I'm going to be doing some work on this imminently.

Giving non-devs voting power for revisions is more of a policy change than a technical one. I'm doing my best not to put words in anyones mouth, but my perception is this will have a lukewarm reception among the site staff. I believe in the site's early history we had something similar and allowed the entire community to vote on revisions. The way things shaked out was current players of a game would strongly prefer that there is no revision to any achievement set ever. That is understandable, but also conflicts with the project's goals.

Additionally, I'm not sure any formulaic weighting can work around the problem. Players significantly outnumber devs. In 30 minutes, enough new accounts are created to outnumber the entire dev team.

The idea that I wanted to propose was to create a new game_achievement_set_plans table in the database which would allow any user (dev or non-dev alike) to draft a revision plan and propose the revision. These plans would support rescoring achievements, demoting achievements, transferring achievements to/from subsets, and proposing new achievement designs (with titles, descriptions, points values, etc).

A new team ("set design team"?) could review these plans and offer feedback or a counterproposal. The community could publicly give feedback on these plans as well (they'd be commentable).

Once a plan is ready, a dev could sponsor it, and the voting process would move off Discord and on site.

[MertTolo]

I agree with you wholeheartedly on 2 and the creation of new accounts + the outnumbering problem, that was an oversight in my original post - I feel like comments are the best middle ground for that (as at least there is some discussion for that then) and everything you wrote is solid, as far as I understand and read it.