Ban Request against Rilist

Discussion in 'Denied' started by Bender, Jun 25, 2017.

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

    Bender Forum Bot

    Joined:
    Jan 3, 2015
    Messages:
    1,952
    Likes Received:
    88
    Ban Request Against Rilist

    Target Name:
    Rilist
    Target SteamID:
    STEAM_0:1:164682416
    Target Forum Profile URL:


    Requester Name:
    furry
    Requester Forum Profile URL:


    Event Date and Time:
    13:57 (na)
    Server:
    Devinity Flood EU #2
    What rules the target broke:
    10: Do not exploit and/or encourage the use of any glitches, hacks, or bugs.
    Briefly explain what happened:
    They were flying above the water (they were stuck in each other and were abusing of it)

    Screenshot evidence:
    http://steamcommunity.com/sharedfiles/filedetails/?id=955400337
    (U can find more here) http://steamcommunity.com/id/FRAKZ/screenshots/

    Video evidence:

    Other evidence:
     
    #1
  2. Bender

    Bender Forum Bot

    Joined:
    Jan 3, 2015
    Messages:
    1,952
    Likes Received:
    88
    Ban Request Against VimeR

    Target Name:
    VimeR
    Target SteamID:
    STEAM_0:1:92597573
    Target Forum Profile URL:


    Requester Name:
    furry
    Requester Forum Profile URL:


    Event Date and Time:
    13:57 (na)
    Server:
    Devinity Flood EU #2
    What rules the target broke:
    10: Do not exploit and/or encourage the use of any glitches, hacks, or bugs.
    Briefly explain what happened:
    They were flying above the water (they were stuck in each other and were abusing of it)

    Screenshot evidence:
    http://steamcommunity.com/sharedfiles/filedetails/?id=955400337
    (U can find more here) http://steamcommunity.com/id/FRAKZ/screenshots/

    Video evidence:

    Other evidence:
     
    #2
  3. counter

    counter Moderator Staff Member Server Moderator Platinum VIP

    Joined:
    Feb 21, 2015
    Messages:
    3,131
    Likes Received:
    850
    Server:
    Flood
    Discord:
    co#2858
    This was most likely done unintentionally. I'm going to deny this request--case noted

    I'm going to see if @Donkie can fix this issue
     
    #3
Thread Status:
Not open for further replies.