search

JustArchiNET / ArchiSteamFarm

C# application with primary purpose of farming Steam cards from multiple accounts simultaneously.
Apache License 2.0
11.14k stars 1.05k forks source link

Feature - !block Steam64id,Steam64id #515

Closed reeporter closed 7 years ago

reeporter commented 7 years ago

Hello,

i thought it would be nice if ASF had the possibilty to block a list of Steam64id's.

like

!block Steam64id,Steam64id

JustArchi commented 7 years ago

What is the purpose or reasoning of that? What is supposed to be blocked? Why?

reeporter commented 7 years ago

I have a big list of known scammers and other people who try to abuse bot mechanics for profit.

It would make it easy to share that list with others, import it into the bot accounts.

JustArchi commented 7 years ago

How you can "abuse ASF mechanics for profit"? ASF logic does not allow that.

reeporter commented 7 years ago

Trade bots that have match everything enabled...

Most people out there trade with common sense and respect for others. There are some people that only make profit with cards and have 10000+ cards.

JustArchi commented 7 years ago

Out of the scope but let's say that it can be added, since many people are asking for that feature and it's not that heavy to implement. Should also make Menels happy so he doesn't have to maintain his own custom build.

reeporter commented 7 years ago

I was talking to Menels about that too and also thought it might be not too complex. But i am not a coder thats your expertize. I realy appreciate your work!

Ne3tCode commented 7 years ago

Why don't just 'block all communication' with the 'scammer'?

JustArchi commented 7 years ago

@Ne3tCode Command > manual logging in and blocking, especially since you can use <Bots> syntax for adding to all bots.

Ne3tCode commented 7 years ago

You could do it in your commit. 1 http request to block, 1 request to unblock.

JustArchi commented 7 years ago

Yes, but I intentionally don't want to block people in ASF, but only to ignore trades from them.

Rudokhvist commented 7 years ago

If I remember it right - list of blocked users in steam is limited, so handling it in asf instead is not so bad idea. But why command and not a config property?

JustArchi commented 7 years ago

Because it should be possible to add/remove people during runtime, config properties are meant for more-or-less static things you change rarily. This is the one you can change often (for people that decide to use it of course).

MikeLund commented 7 years ago

@Ne3tCode The background for this is to help people who run 1:1 bots with MatchEverything,so their inventories doesn't end up looking like this: https://steamcommunity.com/profiles/76561198305483770/gamecards/568650 They want to offer diversity in cards for the community to craft sets with, not so other people can make a profit. They see obvious abuse, simple to blacklist them. If you block communication someone, they can't post on your profile to "appeal" the block either. So Archi's change works great for this.

reeporter commented 7 years ago

I think Archi approach here is better than just completly blocking those users. Sometimes I mistakenly block users. In that case they can still write on my profile and make an appeal.

And you can still block them manuly if they are that bad.

2017-03-30 9:10 GMT+02:00 MikeLund notifications@github.com:

@Ne3tCode https://github.com/Ne3tCode The background for this is to help people who run 1:1 bots with MatchEverything,so their inventories doesn't end up looking like this: https://steamcommunity.com/ profiles/76561198305483770/gamecards/568650 They want to offer diversity in cards for the community to craft sets with, not so other people can make a profit. They see obvious abuse, simple to blacklist them. If you block communication someone, they can't post on your profile to "appeal" the block either. So Archi's change works great for this.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/JustArchi/ArchiSteamFarm/issues/515#issuecomment-290322410, or mute the thread https://github.com/notifications/unsubscribe-auth/AA7G-Fohq5b7NPmqaKNWfUYqCONimJ12ks5rq1V5gaJpZM4Mr_Ll .