Settings and Modifiers by insouciance

[halcyon marsh]

Welcome @vital prairie! Any feedback from the community will show up here.
Please note that this thread discussion may be shared with SMG, but its primary purpose is for the RISK community to discuss ideas and provide constructive feedback.
If you would like to submit feedback to SMG directly, use this link.

[mild tulip]

Neutral vote because auto removing players from block list may not be preferred behaviour

[cold leaf]

I would say you should never report anyone who you would not want blocked or are not completely sure they deserved to be reported in the first place. This will take the consequence out of falsely reporting people.

[vital prairie]

It's not auto removing. But rather look at the report given by risk, and then make your decision.

[mild tulip]

Ah, so like a notification on their avatar in block list?

1. Friend icon has notifications -> click
2. Blocked list has notifications -> click
3. Blocked players with notification are at top of list(?) -> click an avatar
4. Remove Block | Report Update (notification icon again) -> click Report Update
5. you reported on DATE: report status: INFO account status: INFO
   so report status: accepted by admin / rejected by admin / accepted by system / rejected by system
   account status: I guess ban duration or "permanently banned"?

You'd then be able to remove players from blocklist that are permanently banned too - since you won't see them again anyway

[vital prairie]

Yes, so that we can see the history of it before making an informed decision. As of now, once the original risk report gets closed, we can never see what happened to it again

Yes, the workflow you presented will work. Important is to be able to retrieve those information

[mild tulip]

edited message above with more info*
definitely an idea, upvoting as it's not automatically changing blocked status

Not sure it's as simple to implement though,
blocked lists -> per user basis
reports -> separate
report statuses -> within individual reports

and report reason may have been "bad name" - so a collab suspension (or no suspension) wouldn't necessarily be relevant
you'd need to store the reason reported, ideally the reason suspended (whether or not they match would be relevant context)

[vital prairie]

Yes, understand that it may not be that simple as it is querying from different database. But can be done if resources are put into developing this. Whether it's worth it or not is a separate thing. I think for a first step is to get some kind of information on the block list. Can be only report reasons or report results.