Dismiss Notice
Wynncraft, the Minecraft MMORPG. Play it now on your Minecraft client at (IP): play.wynncraft.com. No mods required! Click here for more info...

Can I Get This Glitch Fixed?

Discussion in 'Wynncraft' started by Joshua White, Dec 7, 2015.

Thread Status:
Not open for further replies.
  1. Joshua White

    Joshua White Travelled Adventurer

    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    12
    I attacked a guild and instead of tping me to the guild fight, i was tped to nothingness. I typed /kill to get out of the nothingness, and when i tried to /guild attack again it said "your guild is already in battle". Any time any members of the guild or myself try to attack a guild now it will always say "your guild is already in battle" Is there any way to fix this glitch myself, or for an admin to fix it? *the first image isnt of the exact moment, its just a picture i took of a previous time in which i experienced this "nothingness" for referencing purposes* Screen Shot 2015-11-07 at 12.02.30 AM.png Screen Shot 2015-12-06 at 7.35.30 PM.png
     
  2. Thunder

    Thunder Chief Thunder HERO

    Messages:
    3,818
    Likes Received:
    6,409
    Trophy Points:
    217
    Guild:
    Minecraft:
    Didn't I see this exact same thread before.......
    Oh yeah. Kinda. https://forums.wynncraft.com/threads/admin-help-pls.95973/
     
  3. Joshua White

    Joshua White Travelled Adventurer

    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    12
  4. CheesePrince13

    CheesePrince13 Eternally Inactive HERO

    Messages:
    377
    Likes Received:
    434
    Trophy Points:
    85
    Guild:
    Minecraft:
    It's already known that guilds are completely busted. All we can do is wait until it gets fixed. It's supposed to be done soon after gavel's release. However this is the Wynncraft definition of "soon" so who knows when it will happen.

    I'm not sure which is worse, making a new thread after seeing the old one, or necroposting the old one ;-;

    No actually I'm pretty sure it's that first option :l
     
Thread Status:
Not open for further replies.