1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Reputation Thread READ ME!

Discussion in 'Reputation Threads' started by n0name, Sep 28, 2014.

Thread Status:
Not open for further replies.
  1. n0name

    n0name Founder

    Joined:
    Aug 27, 2012
    Messages:
    6,239
    Likes Received:
    1,207
    Steam:
    Steam SteamRep SourceBans gameMe
    Unlike SOP, we do not want to burden you with a lot of rules, so we will try to keep this nice and simple.

    1. Rep should only be left on risky transactions (PayPal, Brokering, etc.), it is pointless to +rep someone only because they are nice or you have made a 1:1 item trade. We will not punish you for that, but if it reaches a certain non-tolerable amount, we will close your thread.

    2. ABSOLUTELY NO FAKE REP. If we notice that you were given fake rep (either by a friend or some random stranger/alt), your thread will be deleted and you permanently banned from this site. In case it's also related to a scam, a BANNED BY tag will be applied on SteamRep.

    3. We do allow external rep, but please keep records of everything. If we find one or many of your rep entries bogus, we will ask you for said proof. Failure to do so will result in a permanent forum ban + thread deletion.

    4. Your rep thread MUST contain a SteamRep block, like shown below:

    | steamname: [FoG] n0:name S>Buds17k
    | steam3ID: [U:1:53504668]
    | steamID32: STEAM_0:0:26752334
    | steamID64: http://steamcommunity.com/profiles/76561198013770396
    | customURL: http://steamcommunity.com/id/awi95
    | steamrep: http://steamrep.com/profiles/76561198013770396

    5. All alt accounts should be listed (SteamID64 + name is sufficient)

    6. Players tagged with BANNED BY tags on SteamRep are not allowed to make rep threads, all threads made by such users will be deleted

    Please report any instances of FAKE REP or SR TAGGED PLAYERS by using the "Report" button below the post!
     
    Last edited by a moderator: Jan 15, 2016
Thread Status:
Not open for further replies.