Grief Report / Rollback Request

Discussion in 'Historically Archived Grief Report & Rollback Req' started by Reincarnated_, Feb 21, 2016.

Thread Status:
Not open for further replies.
Thread Tools

Thread Tools

  1. Reincarnated_

    Reincarnated_ Builder
    Builder ⛰️ Ex-Tycoon ⚜️⚜️⚜️

    Joined:
    May 31, 2015
    Messages:
    619
    Trophy Points:
    28,840
    Gender:
    Male
    Ratings:
    +1,333
    Minecraft Username: Exportation

    Affiliation: Mayor

    Town Name: Shanghi

    Town World: Rising

    Is the Grief located in the Wild? If so, is there a pending Mayor application for this defined region? No. it is not in the wild.

    Co-ordinates of Grief: X: 8792 Z: 4425

    Brief Description: Houses built, trees grown and random blocks placed everywhere.

    Which users own the griefed area, or are allowed to edit blocks in the area Griefer was caught.

    Screenshots to assist Staff identify the grief: http://prntscr.com/a6b5hg http://prntscr.com/a6b5ms http://prntscr.com/a6b5wo

    Rollback: Yes
     
    #1 Reincarnated_, Feb 21, 2016
  2. miniCLH

    miniCLH President
    President ⛰️⛰️ Ex-EcoLegend ⚜️⚜️⚜️⚜️ Prestige ⭐ II ⭐ Premium Upgrade

    Joined:
    Apr 14, 2013
    Messages:
    1,729
    Trophy Points:
    70,010
    Gender:
    Male
    Ratings:
    +397
    For this http://prntscr.com/a6b5hg I found that SayianSamYT was the person that did this, however they have already been banned for this reason.

    For this http://prntscr.com/a6b5ms I was unable to find anything, this could be due to the logs being reset or the build being old.

    For this http://prntscr.com/a6b5wo I found that the user water1hp destroyed the following:
    141 Potatoes

    I also found the user fbi54 destroyed the following:
    28 Potatoes

    water1hp has been tempbanned for 24 hours for Minor Crop Grief In Shanghi
    fbi54 has been tempbanned for 24 hours for Minor Crop Grief In Shanghi
    Rollback Denied, Block damage does not meet the rollback requirements.
     
    #2 miniCLH, Feb 21, 2016
Thread Status:
Not open for further replies.