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...
Dismiss Notice
Have some great ideas for Wynncraft? Join the official CT (content team) and help us make quests, builds, cinematics and much more!

Guilds Simple Sniping Fix

Discussion in 'General Suggestions' started by Splintered, Aug 4, 2020.

?

Do you want this?

  1. Yes

    8 vote(s)
    28.6%
  2. No

    20 vote(s)
    71.4%
Thread Status:
Not open for further replies.
  1. Splintered

    Splintered dERN for ERN VIP

    Messages:
    158
    Likes Received:
    45
    Trophy Points:
    55
    Guild:
    Minecraft:
    I already posted this as a response to Novalescent's guild suggestion but I decided to make a separate thread for it, just to get it out in the wynn team's eyes. The entire suggestion is really just an easy and better way to do sniping. Instead of the old ping based system, guilds can instead attack a territory like 3 seconds or less than when it is actually ready to be attacked. This isn't really attacking per se, but it puts either all attackers, or all guilds attacking on a list, (the all attackers option being better for the guilds with a bigger war team) and will randomly pick from this list who successfully attacked. No ping, just random.

    Because of the bit of negative response this has seen so far I decided to explain this a bit more and why it is (IMO) the best option we have. Basically attacking a territory doesn't really have much to it and because of the way it works there is no way for sniping to be fair. By making it RNG it lets people, me for example, have a fighting chance. Take for example there being three guilds. Each has 3 people sniping. But the thing is, they ALL have the same ping. If they all attack at the same time which they should be doing, it's random anyways right? Maybe one person is a tiny bit quicker, but then again their ping being ever so slightly worse would also make that bit of skill completely irrelevant. So maybe it's the idea of it being RNG that gets a negative response, but in reality sniping will always have that RNG element. Making it actually RNG makes it fair. Unless you wanna like, pvp for whoever gets the flag you really can't change it. Why not just make it actually RNG so it's not just RNG for the few but RNG for the masses.
    ________________________________
    Oh btw I feel like being petty so... THE PEOPLE VOTING NO HAVE GOOD PING
     
    Last edited: Aug 4, 2020
    pogge5 and AjSimp_ like this.
  2. Novalescent

    Novalescent Retired Wynncraft Systematic Recreation Developer HERO

    Messages:
    569
    Likes Received:
    2,631
    Trophy Points:
    109
    Minecraft:
    It's an interesting idea, but at the same time it's RNG. I don't think people would feel right being cheated out of attacking a Territory because the dice didn't roll their way.
     
  3. Splintered

    Splintered dERN for ERN VIP

    Messages:
    158
    Likes Received:
    45
    Trophy Points:
    55
    Guild:
    Minecraft:
    But isn't that how it is to begin with? Except it's permenant rng basically if u have good ping u win
     
    Novalescent likes this.
  4. Novalescent

    Novalescent Retired Wynncraft Systematic Recreation Developer HERO

    Messages:
    569
    Likes Received:
    2,631
    Trophy Points:
    109
    Minecraft:
    Fair, but then would this change be better than the current state of things? Would it just be legitimizing the ping RNG to be more consistent?
     
  5. TheEpicCajun

    TheEpicCajun bee

    Messages:
    296
    Likes Received:
    1,622
    Trophy Points:
    76
    Guild:
    Minecraft:
    All I will say is that there is no simple fix for sniping, and this suggestion does not change that.
     
  6. Alex1

    Alex1 Alex HERO

    Messages:
    209
    Likes Received:
    510
    Trophy Points:
    67
    Guild:
    Minecraft:
    No. This is entirely unfair, and would make sniping even more broken, to the point actually where it would be impossible to reclaim from allies. Imagine an enemy alliance, off the map. All they have to do is get singular players in as many guilds as possible, and queue attacks on territories. It wouldn't matter if the main guild has 10 players online, since if 10 enemy players split into 10 guilds there's only a 10% chance of the actual owner winning the snipe.

    The only way I could see this work is if a guild could send in multiple "attacks", so if a guild has 10 players online all at a banner, VS 10 players in an enemy alliance split into enemy guilds, it's still 50/50.

    Either way however, RNG isn't the way to solve this problem. If you want to see our solution to it, here you go https://forums.wynncraft.com/threads/rural-player-discrimination-aka-how-to-fix-sniping.271347/
     
  7. Splintered

    Splintered dERN for ERN VIP

    Messages:
    158
    Likes Received:
    45
    Trophy Points:
    55
    Guild:
    Minecraft:
    How would it legitamize the ping RNG? It's getting rid of it.
    That just means that the player option that I mentioned would work better than the guild option
     
  8. MysticStrider

    MysticStrider Retired Emperor of Sindria HERO

    Messages:
    773
    Likes Received:
    159
    Trophy Points:
    62
    Guild:
    Minecraft:
    See, if the whole point of allied guilds defending 0 is so the guild that's being attacked can take the territory, making it completely random turns this process into a 1 in however many attacking guilds there are, giving the attacking force an overwhelming advantage. This doesn't make sniping fair-it serves to do is skewer the advantage of being attacker more so than it already is.
     
  9. Splintered

    Splintered dERN for ERN VIP

    Messages:
    158
    Likes Received:
    45
    Trophy Points:
    55
    Guild:
    Minecraft:
    But is that not how it already is and does it not already work fine? All this suggestion is doing, (if you look at the player one not the guild one turns out that was stupid) is making the system fair for everyone.
     
Thread Status:
Not open for further replies.