[Suggestion] @Heintzer, Morello, and Ironstylus: More ideas regarding RIot-Player communication
#The problems:
#1) The same posts keep coming up over and over again
This is a problem because players feel like Riot isn't listening, while Rioters have to choose between actually doing work and addressing the same issues over and over again.
Examples:
- Read by a Rioter was discussed here
- The topic of Karma's Rework was [apparently ](http://(http://boards.na.leagueoflegends.com/en/c/champions-gameplay/xl2REgqA-please-acknowledge-karma?comment=00030000)beaten to death back in the day.
- Reduced consequences when your team has an afk has SO many threads.
#The solution: R^3, the Rioter Response Repository
How does it work?
- The Repository functions as a kind of FAQ, with a list of commonly posted topics and links to the threads where Rioters have responded to those topics.
- When Rioters post, they have an opportunity to add that thread to the Repository.
- They are not required to do so.
- When I create a new thread, there's a comparison between my thread title and threads in the repository, and a "Check out these threads before you post" message
#2)
Originally posted by: Daen It's a feedback loop, essentially. This is a trend I have noticed over my four years participating in League's community:
Community wants information Riot gives information Community gets mad at Riot Riot becomes more reluctant to give information Community wants information etc.
This is obviously oversimplified, as it doesn't happen for everything (or even most things).
It seems like, no matter what Riot does here, they can't win. But let's take a closer look...
#Scenario 1: Riot doesn't give information.
Possible outcomes:
- Community wants information, gets mad at riot for no transparency.
- Community understands that Riot just wants to avoid setting expectations and isn't mad.
- Yeah, right.
- Even if this happened, the community would still feel resentful that Riot isn't able to give info.
tl;dr, this is a bad solution.
#Scenario 2: Riot does give information
Possible outcomes:
- Community gets false expectations, then is disappointed and mad when they inevitably aren't met
- Messaging is done in such a way that the community doesn't get false expectations.
Of course, there's a chance of community backlash if messaging is done wrong. But the important thing to note here is that, in scenario 1, there is no realistic success story.
#If messaging is done, rather than avoided, there is at least a chance of success.
So then, the question becomes, What is required for successful messaging?
#I think the answer is more transparency.
-
Riot needs to have more high-level discussion with players.
- There are no promises to be made of expectations to be set or broken here.
It's just a discussion of philosophy.
- You can commit to fixing [the jungle] while simultaneously being honest that you may not get it right the first time.
- Morello does a great job of this here.
- There are no promises to be made of expectations to be set or broken here.
It's just a discussion of philosophy.
-
Riot needs to be clear about both what their priorities are AND how likely those priorities are to change. Example: Champion Updates.
- The Champion Update Schedule is a great start.
- The problem is, the list seems fixed, but it's not. Fiora used to be on that list, but has since fallen off.
- I suggest a system like this:
#Champion Update Schedule
|Up Next|Priorities|On the List|Not On the List| |- |We're committed to releasing these champion updates next. We Promise.|These champion updates are high on our priorities list right now, and we're playtesting potential changes, but we might end up dropping them if our priorities change. NO PROMISES|These champions need work, but they're not our top priority. We're thinking about them, but probably not playtesting changes.|We think these champs are in a good spot right now, and we're not looking to make any kit changes (balance/number changes are still on the table). |Soraka|Viktor|Diana|Lucian| |Sion|Fiora|Morgana|Leona| |||Leblanc|Thresh| |||Talon|Nidalee|
- This system has increased clarity.
- It only promises that which you actually have in line to deliver.
- It provides a framework around which to have discussion.
- "Thresh isn't on the list, but I think he should be because his kit is overloaded" is a much more constructive thread than "Thresh has been a top pick all season and still no nerfs"
One final thing to address:
Why is this post in Boards Feedback?
I put it here because I think the closer the people creating content are working with the people delivering that content, the more the form of delivery makes sense, and the better the delivery is.
######Thoughts?