Announcement

Collapse
No announcement yet.

Stop the fake 5* battle results with #checksum

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Stop the fake 5* battle results with #checksum

    The battle result says they 5* your base, but the replay shows an impossible victory after a few seconds of combat by a handful of weak troops. This is annoying in MP but completely overturns the outcome of wars. This is not healthy for the game. Enough already!

    Nexon could easily prevent this cheat by adding a digital fingerprint (a checksum hash) to the battle result. It is a small calculated value unique to the two players and the actual battle result that cannot be faked when properly implemented. I don’t understand why they don’t just do it.

    #checksum

  • #2
    This is the first time I'm hearing of this but it does sound like the right thing to do.
    *************************************************

    Lord Stark leader of Dragonstone 1.0

    Comment


    • #3
      But is it really a type of cheat or just a wrong replay? Cause i've seen a lot of replays COMPLETLY wrong even in my own attacks.

      Comment


      • Cannibals
        Cannibals commented
        Editing a comment
        Joe, adding security to battle results won’t harm anything even if it is just a bad replay. But it is hard to imagine that 5 Iron Age infantry actually defeated a space age base and the replay is just amiss. And that it has happened agains hundreds of players.

        #checksum
        Last edited by Cannibals; 08-24-2019, 02:11 PM.

    • #4
      Yes, i face the same problem too, heres some proof.
      Attached Files

      Comment


      • #5
        Agreed that something has to be done. If the checksum approach is such a simple fix, why wasn't this used initially? Is this standard in other games?

        In addition, I was hit twice by the same cheater in a few days which to me means he has some way of saving a player's base to attack it again repeatedly. How is this possible?

        proof

        Comment


        • Persia
          Persia commented
          Editing a comment
          It’s likely your medal range. Get high enough, and there are only a few bases to hit. Nobody can “save” a base to later hit them unless you get attacked by them, but I don’t think that’s the case here, since he had already attacked you.

      • #6
        Very common at high levels. I’m assuming this is still the result of the matrix glitch that hasn’t been fully patched. I’ve been getting attacked by them constantly. It’s not a replay glitch. They drop infantry only and log says they 5 starred my max defense base. Not possible.
        Dominion Legion is accepting new members. You can also consider joining Dominion Elite, Dominion Jedis, Dominion Empire, DominionRaiders, or Dominion Stars.

        Visit our thread: Dominion Family of Alliances

        All of our alliances are connected via the Line chat app. Add my ID SirVipe on the LINE app and message me to join our alliance chat groups.

        Comment


        • Cannibals
          Cannibals commented
          Editing a comment
          This isn’t matrix. It’s unscrupulous players running an unsophisticated app that intercepts the battle result message and simply updates where it says 0* to instead say 5*. They wouldn’t be able to do it if there was a digital fingerprint on the message that would indicate when it had been tampered with.

          #checksum

      • #7
        this will not solve people using 200 demolition tactics or 20 troop cards or 30 planes to get a 5 star

        Comment


        • Cannibals
          Cannibals commented
          Editing a comment
          That’s a different problem. In that case, they did actually get a 5* victory albeit through invalid means and the battle report matches the outcome. This fix would stop the cases were the outcome is tampered with before it gets reported to Nexon servers.

          #checksum

      • #8
        If it really is as simple as an app intercepting and changing the number of stars then a checksum will be a good counter measure. Until the developer works out how the checksum is calculated and builds it into the app. We also need an AI auditor of all battles to spot impossible results (like 6 infantry clearing a base the same age or higher) and dealing with the cheater. The punishment is probably a subject for a new topic though.
        Bad Rabbits. We hop, you drop. Adults 25+

        Comment


        • Cannibals
          Cannibals commented
          Editing a comment
          AI auditor is a great idea, and it will work better if it audits battle results that have not been tampered with. There are readily-available hashes like SHA-1 that can be used as a checksum for unbreakable security of battle results so that hackers won’t be able to duplicate it. #checksum

      • #9
        It’s a pretty goo idea

        Comment


        • #10
          Sigh ... another loss to a handful of weak troops in just 6s. This is the biggest issue with the game today imo. #checksum

          Comment


          • #11
            Selling P2W crap like artifacts for $200 no problem, getting rid of cheaters no go...I would be ashamed if I was Nexon

            Comment


            • #12
              Bump. Bump. Bump.
              *************************************************

              Lord Stark leader of Dragonstone 1.0

              Comment


              • #13
                I know it sounds silly to ask, from me.. 😅😆 but how does this checksum work?
                Does it only work on developer server, or does it apply to our game and devices as well?
                Improvise. Adapt. Overcome.
                ​​​​​​

                Comment


                • Cannibals
                  Cannibals commented
                  Editing a comment
                  The result of the battle would be run through a one-way algorithm on your device to calculate a unique number matching that result. The number would then be sent to Nexon along with the battle result. If the battle result is tampered with along the way, it won’t match against the unique number when it arrives at Nexon’s server. #checksum
              Working...
              X