(OITC) Glitch

Discussion in 'Report Bugs' started by John3nv, May 17, 2014.

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

    John3nv

    Messages:
    797
    Likes Received:
    459
    Your username: John3nv

    In which minigame/server does the bug occur:
    This happened in OITC

    Detailed description of bug:
    Well I joined a match and I spawned over the void and here are some screen shots.[​IMG]
    [​IMG]
     
  2. kinghakaka

    kinghakaka Bowsweat- Trickshotter #Veracity- 1500 Subs

    Messages:
    4,094
    Likes Received:
    2,178
    Minecraft:
    Hakaka & Feyenoord
    this is on terminal @ItsHarry says it is fixed but now i see youre screenshots it isnt fixed
     
  3. John3nv

    John3nv

    Messages:
    797
    Likes Received:
    459
    Yes, and I spawned there again twice.
     
  4. Olovi2008

    Olovi2008

    Messages:
    72
    Likes Received:
    88
    This happens to me a lot :/
     
  5. ItsHarry

    ItsHarry Owner Staff Member Owner

    Messages:
    9,372
    Likes Received:
    23,362
    Minecraft:
    ItsHarry
    Could you take another screenshot but this time with F3 open?
     
    John3nv and ZZTheNinja like this.
  6. AACM

    AACM

    Messages:
    1,522
    Likes Received:
    938
    How is that needed actually?

    EDIT: Oh, to find the spawn >.<
     
  7. ZZTheNinja

    ZZTheNinja Yass Donator

    Messages:
    884
    Likes Received:
    468
    Minecraft:
    ZZTheNinja
    But the glitch doesn't happen every Match. Or does it? Last time I played this map it was fine.corrupted chunk('s)? Or is it just were you spawn and the map was totally fine?
     
  8. ItsHarry

    ItsHarry Owner Staff Member Owner

    Messages:
    9,372
    Likes Received:
    23,362
    Minecraft:
    ItsHarry
    I posted the following on friday at 9:13 PM.
    I believe this thread was made before the server restarted. The server restarted on Saturday at 11:00 AM.
    This bug should already be fixed.
     
    John3nv, kinghakaka and ZZTheNinja like this.
Thread Status:
Not open for further replies.